Back-To-Back PRI - Am I Missing something??
pitviper
Member Posts: 1,376 ■■■■■■■□□□
Hi! Anyone know if a Back to Back PRI lab configuration is possible with the following hardware:
Router1 - c1760, PVDM-256K-16, VWIC-2MFT-T1, CME
T1 X-Over cable (tested)
Router2 - c1760, PVDM-256K-16, VWIC-2MFT-T1, CME
I see layer-1 connectivity between the PRI, but have been unable to call across.
Router1:
tdm clock T1 1/0 both import onboard internal
isdn switch-type primary-ni
controller T1 1/0
framing esf
linecode b8zs
pri-group timeslots 1-12,24
interface Serial1/0:23
no ip address
encapsulation hdlc
no logging event link-status
isdn switch-type primary-ni
isdn protocol-emulate network
isdn incoming-voice voice
no cdp enable
Router2:
tdm clock T1 1/0 both export line
isdn switch-type primary-ni
controller T1 1/0
framing esf
linecode b8zs
pri-group timeslots 1-12,24
interface Serial1/0:23
no ip address
encapsulation hdlc
no logging event link-status
isdn switch-type primary-ni
isdn incoming-voice voice
no cdp enable
Thoughts???
Router1 - c1760, PVDM-256K-16, VWIC-2MFT-T1, CME
T1 X-Over cable (tested)
Router2 - c1760, PVDM-256K-16, VWIC-2MFT-T1, CME
I see layer-1 connectivity between the PRI, but have been unable to call across.
Router1:
tdm clock T1 1/0 both import onboard internal
isdn switch-type primary-ni
controller T1 1/0
framing esf
linecode b8zs
pri-group timeslots 1-12,24
interface Serial1/0:23
no ip address
encapsulation hdlc
no logging event link-status
isdn switch-type primary-ni
isdn protocol-emulate network
isdn incoming-voice voice
no cdp enable
Router2:
tdm clock T1 1/0 both export line
isdn switch-type primary-ni
controller T1 1/0
framing esf
linecode b8zs
pri-group timeslots 1-12,24
interface Serial1/0:23
no ip address
encapsulation hdlc
no logging event link-status
isdn switch-type primary-ni
isdn incoming-voice voice
no cdp enable
Thoughts???
CCNP:Collaboration, CCNP:R&S, CCNA:S, CCNA:V, CCNA, CCENT
Comments
-
pitviper Member Posts: 1,376 ■■■■■■■□□□I'm all set now - above config works like a charm when I put the crossover cable between the CORRECT T1 ports (had them connected via 1 and not ports 0!!!). Good example of why lab experience with real gear is so beneficial. I looked over the config like 20 times before I located the physical error!!!!CCNP:Collaboration, CCNP:R&S, CCNA:S, CCNA:V, CCNA, CCENT
-
Luckycharms Member Posts: 267HAHAHA >>> I laugh because I have done that before with FXSs ports... If you ever mess with High Density FXS/DID cards make sure you test them before assuming they work..
But good for you on finding the problem...The quality of a book is never equated to the number of words it contains. -- And neither should be a man by the number of certifications or degree's he has earned. -
pitviper Member Posts: 1,376 ■■■■■■■□□□mikej412 wrote:pitviper wrote:I see layer-1 connectivity
Nah, hardware level, green light on the VWICs
I'll just have to train myself to think right to left I guess!CCNP:Collaboration, CCNP:R&S, CCNA:S, CCNA:V, CCNA, CCENT -
mikej412 Member Posts: 10,086 ■■■■■■■■■■pitviper wrote:isdn protocol-emulate network
Somewhere in the distant past I guess I must have plugged into the wrong T1 port -- I always use a loopback plug to test -- and see which port comes up:mike: Cisco Certifications -- Collect the Entire Set!