PRI link not working with router

lorenz84gDD · ‎12-19-2010

Hello all,

I have an issue with a 2911 router with a VWIC2-1MFT-T1/E1 module set as E1 card. The release is 15.0(1)M3, universalk9.

When I connect the router to the telecom's DCE I get an error message stating LOF detected and after some minutes the link from the telco switch gets down, then I have to contact my provider to switch that back on. I mean the link between the two DCEs.

The E1 link works fine when connected to the old PABX.

I'm sure about the CRC4 line mode. I don't know the available numer of time-slots.

I've noticed, but i'm not sure, some runts and input errors on the serial interface.

I made this link work in the past (two week ago) but now, with the same configuration, router position and so on it's not working. The only difference is the snow all around the city :)

This is the configuration:

network-clock-participate wic 0

network-clock-select 1 E1 0/0/0

isdn switch-type primary-net5

controller E1 0/0/0
pri-group timeslots 1-31

interface Serial0/0/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn overlap-receiving
isdn incoming-voice voice
isdn send-alerting
no cdp enable

Any idea is really appreciated

many thanks

Lorenz

------- have a look to my blog lgrconsulting.com

Daniele Giordano · ‎12-19-2010

What's the output of "show controller e1"?

Refer this for troubleshooting: http://docwiki.cisco.com/wiki/Cisco_IOS_Voice_Troubleshooting_and_Monitoring_--_T1_or_E1_Interface_Troubleshooting#Controller_Has_Loss_of_Frame

This is my config:

network-clock-participate E1 1/0
network-clock-select 1 E1 1/0

controller E1 1/0
clock source line
pri-group timeslots 1-31

interface Serial1/0:15
no ip address
encapsulation hdlc
no logging event link-status
no snmp trap link-status
isdn switch-type primary-net5
isdn overlap-receiving T302 3000
isdn incoming-voice voice
isdn map address transparent
isdn send-alerting
isdn negotiate-bchan
isdn sending-complete
no isdn outgoing display-ie
no cdp enable

Regards.

lorenz84gDD · ‎12-19-2010

hello,

thanks for you reply.

I don't have the precise output but i can remember the controller remains down, hdb line encoding is on and CRC4 is enabled.

------- have a look to my blog lgrconsulting.com

paolo bevilacqua · ‎12-19-2010

You must post the output to enable others to help you.

dennis916 · ‎12-19-2010

Hi Lorenz,

Your setup works when you connect it to the PBX because you already sync the correct configuration to that E1 parameter. Now, it is very much differs to the connection with your E1 Pri local provider, usually before you start with your configuration you must get or coordinate with your local provider regarding the parameters they setup to that E1, you can get this information with them, like line coding, framing, channels open, etc... or of the E1 Pri is still on a loopback setup in there end.

Regards,

Dennis

lorenz84gDD · ‎12-20-2010

This is what I get when I connect the Router to the PRI link

E1 0/0/0 is down.
Applique type is Channelized E1 - balanced
Far End Block Errors Detected
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20100222, FPGA: 13, spm_count = 0
Framing is CRC4, Line Code is HDB3, Clock Source is Line.
Data in current interval (415 seconds elapsed):
     3399265 Line Code Violations, 91855 Path Code Violations
     41 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 415 Unavail Secs
Total Data (last 1 15 minute intervals):
     7371900 Line Code Violations, 200954 Path Code Violations,
     73 Slip Secs, 7 Fr Loss Secs, 10 Line Err Secs, 0 Degraded Mins,
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 900 Unavail Secs
VoiceRouterSN#

Dec 20 10:49:58.655: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (LOF detected)
Dec 20 10:49:58.655: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10
Dec 20 10:50:00.655: %LINK-3-UPDOWN: Interface Serial0/0/0:15, changed state to down
Dec 20 10:50:43.655: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up
Dec 20 10:50:43.655: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1
Dec 20 10:50:45.655: %LINK-3-UPDOWN: Interface Serial0/0/0:15, changed state to up
Dec 20 10:50:46.655: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (LOF detected)
Dec 20 10:50:46.655: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10
Dec 20 10:50:48.655: %LINK-3-UPDOWN: Interface Serial0/0/0:15, changed state to down
Dec 20 10:50:51.655: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up
Dec 20 10:50:51.655: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1
Dec 20 10:50:52.655: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (LOF detected)
Dec 20 10:50:52.655: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10
Dec 20 10:50:54.655: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up
Dec 20 10:50:54.655: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1
Dec 20 10:50:56.655: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (LOF detected)
Dec 20 10:50:56.655: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10
Dec 20 10:50:57.655: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up
Dec 20 10:50:57.655: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1
Dec 20 10:50:59.655: %LINK-3-UPDOWN: Interface Serial0/0/0:15, changed state to up
Dec 20 10:51:00.655: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (RAI detected)
Dec 20 10:51:00.655: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10
Dec 20 10:51:01.655: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up
Dec 20 10:51:01.655: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1
Dec 20 10:51:02.155: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (10 SES)
Dec 20 10:51:02.155: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10
Dec 20 10:51:02.655: %LINK-3-UPDOWN: Interface Serial0/0/0:15, changed state to down
VoiceRouterSN#

------- have a look to my blog lgrconsulting.com

paolo bevilacqua · ‎12-20-2010

How is cabling made? Was the PBX using unbalanced (coaxial) ?

dennis916 · ‎12-20-2010

Lorenz,

Far End Block Errors Detected is one error you can consider to your problem, this means that you and the other end does not sync up to make the controller up and running. The issue maybe in the cabling, framing, you can refer to the attached document to have another idea of the show controller e1. Also, just to isolate that your E1 is working physically, you can cross out a RJ45 PINS (1245) to perform your own loopback to verify that the Controller will go "up". You can also change your framing to No-CRC4 just to verify if its on the configuration issue. Another thing is that you can try changing the PINs on the old cable and consider the Cisco E1 pinning 12 45 (tx, rx,). This is because you said that when you put it back on the old PBX it begins to work. Sometimes it is just physical issues or connectors :-)

Dennis