PRI errors

[Bluecrack]

Hey guys and help on this would be appreciated. We have a 3661 router with a PRI interface for our voice calls. Just a few minutes ago voice calls could not be made to the PSTN. Also these errors showed up in the log on the router.

Aug 30 13:45:00 192.168.100.2 local7.notice 54: 1d10h: %SYS-5-CONFIG_I: Configured from console by vty0 (192.168.100.201)
Aug 30 14:15:10 192.168.100.2 local7.notice 55: 1d11h: %CONTROLLER-5-UPDOWN: Controller T1 5/0, changed state to down (RAI detected)
Aug 30 14:16:00 192.168.100.2 local7.notice 56: 1d11h: %CONTROLLER-5-UPDOWN: Controller T1 5/0, changed state to up
Aug 30 14:16:06 192.168.100.2 local7.info 57: 1d11h: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se5/0:23, TEI 0 changed to down
Aug 30 14:16:07 192.168.100.2 local7.notice 58: 1d11h: %CONTROLLER-5-UPDOWN: Controller T1 5/0, changed state to down (LOF detected)
Aug 30 14:18:11 192.168.100.2 local7.notice 59: 1d11h: %CONTROLLER-5-UPDOWN: Controller T1 5/0, changed state to up
Aug 30 14:18:14 192.168.100.2 local7.info 60: 1d11h: %ISDN-6-LAYER2UP: Layer 2 for Interface Se5/0:23, TEI 0 changed to up
Aug 30 14:18:56 192.168.100.2 local7.notice 61: 1d11h: %CONTROLLER-5-UPDOWN: Controller T1 5/0, changed state to down (LOF detected)
Aug 30 14:19:41 192.168.100.2 local7.notice 62: 1d11h: %CONTROLLER-5-UPDOWN: Controller T1 5/0, changed state to up
Aug 30 14:19:51 192.168.100.2 local7.notice 63: 1d11h: %CONTROLLER-5-UPDOWN: Controller T1 5/0, changed state to down (LOF detected)
Aug 30 14:20:05 192.168.100.2 local7.notice 64: 1d11h: %CONTROLLER-5-UPDOWN: Controller T1 5/0, changed state to up
Aug 30 14:20:11 192.168.100.2 local7.info 65: 1d11h: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se5/0:23, TEI 0 changed to down
Aug 30 14:20:33 192.168.100.2 local7.notice 66: 1d11h: %CONTROLLER-5-UPDOWN: Controller T1 5/0, changed state to down (RAI detected)
Aug 30 14:20:45 192.168.100.2 local7.notice 67: 1d11h: %CONTROLLER-5-UPDOWN: Controller T1 5/0, changed state to up
Aug 30 14:20:49 192.168.100.2 local7.notice 68: 1d11h: %CONTROLLER-5-UPDOWN: Controller T1 5/0, changed state to down (LOF detected)
Aug 30 14:21:03 192.168.100.2 local7.notice 69: 1d11h: %CONTROLLER-5-UPDOWN: Controller T1 5/0, changed state to up
Aug 30 14:21:08 192.168.100.2 local7.err 70: 1d11h: %E1T1_MODULE-3-IBOCLOOPUP: Controller T1 5/0 - IBOC loopup code detected, activating line loopback mode.
Aug 30 14:22:20 192.168.100.2 local7.err 71: 1d11h: %E1T1_MODULE-3-IBOCLOOPDOWN: Controller T1 5/0 - IBOC loopdown code detected, deactivating line loopback.
Aug 30 14:22:28 192.168.100.2 local7.notice 72: 1d11h: %CONTROLLER-5-UPDOWN: Controller T1 5/0, changed state to down (RAI detected)
Aug 30 14:22:42 192.168.100.2 local7.notice 73: 1d11h: %CONTROLLER-5-UPDOWN: Controller T1 5/0, changed state to up
Aug 30 14:22:45 192.168.100.2 local7.info 74: 1d11h: %ISDN-6-LAYER2UP: Layer 2 for Interface Se5/0:23, TEI 0 changed to up

Sorry for the long list of errors. Can anyone explain what it all means? Did the telco take down the circuit for some reason?

Thanks,
Bluecrack

 

[UNIX72]

Definitly telco is at fault unless you physically unplug your connection. Just look at the Layer 2 status down. Customer is not seeing CO switch. Probably jeter or wybnormal could fill in with more info.

 

[Bluecrack]

Thanks UNIX72. That's what I figured. Do you know what the E1T1_MODULE-3-IBOCLOOPUP and E1T1_MODULE-3-IBOCLOOPDOWN mean?

Bluecrack

 

[MyHeadHurts]

Bluecrack,

Just happen to be searching around and noticed this one. It's been a year, but here is the answer to your last question.

What this message is indicating is the Telco remotely looping up and then dropping the loop on your CSU in the Cisco. This is definitely the Telco has issues with the circuit (whether the LD carrier or LEC), and then once they got the circuit back up, the normal thing for them to do is to try and loop the customer CSU.