Line Loop by Remote status on T1

vinh.nguyen · ‎05-30-2013

Recently, my AS5400XM started getting this status on some of my T1(I have DS3). I've worked with our vendor and they indicated it is a Cisco bug. We have never had this issue before until they migrated our system to a different switch. The problem can be resolve if my provider restart their T1. But we are seeing the issue again from time to time. Needless to say, I just wanted to find ways to pin point the issue. I believe it is on their end, but i need to get data or anything at all to prevent this from happening again.

Can anyone help me out? I need some starting point.

Below is the output of "show controllers T1 | section is up":

1 7/0:9 is up. (Line Loop by Remote)

Applique type is Channelized T1

Receiver has no alarms.

alarm-trigger is not set

Soaking time: 3, Clearance time: 10

AIS State:Clear LOS State:Clear LOF State:Clear

Version info of slot 7: HW: 1536, PLD Rev: 7

Framer Version: 0x58

T1 7/0:10 is up. (Line Loop by Remote)

Applique type is Channelized T1

Receiver has no alarms.

alarm-trigger is not set

Soaking time: 3, Clearance time: 10

AIS State:Clear LOS State:Clear LOF State:Clear

Version info of slot 7: HW: 1536, PLD Rev: 7

Framer Version: 0x58

And this is output of my log:

013-05-29 09:20:34 Local7.Notice 192.168.1.6 7207: *Jun 28 04:10:42.775: %CONTROLLER-5-LOOPSTATUS: Controller T1 7/0:3, LINE loopback request from external network

2013-05-29 09:20:34 Local7.Notice 192.168.1.6 7208: *Jun 28 04:10:42.775: %CONTROLLER-5-LOOPSTATUS: Controller T1 7/0:4, LINE loopback request from external network

2013-05-29 09:20:34 Local7.Notice 192.168.1.6 7209: *Jun 28 04:10:42.775: %CONTROLLER-5-LOOPSTATUS: Controller T1 7/0:5, LINE loopback request from external network

2013-05-29 09:20:34 Local7.Notice 192.168.1.6 7210: *Jun 28 04:10:42.775: %CONTROLLER-5-LOOPSTATUS: Controller T1 7/0:6, LINE loopback request from external network

2013-05-29 09:20:34 Local7.Notice 192.168.1.6 7211: *Jun 28 04:10:42.775: %CONTROLLER-5-LOOPSTATUS: Controller T1 7/0:7, LINE loopback request from external network

2013-05-29 09:20:34 Local7.Notice 192.168.1.6 7212: *Jun 28 04:10:42.775: %CONTROLLER-5-LOOPSTATUS: Controller T1 7/0:8, LINE loopback request from external network

2013-05-29 09:20:35 Local7.Notice 192.168.1.6 7213: *Jun 28 04:10:42.775: %CONTROLLER-5-LOOPSTATUS: Controller T1 7/0:9, LINE loopback request from external network

2013-05-29 09:20:35 Local7.Notice 192.168.1.6 7214: *Jun 28 04:10:42.775: %CONTROLLER-5-LOOPSTATUS: Controller T1 7/0:10, LINE loopback request from external network

2013-05-29 11:17:37 Local7.Notice 192.168.1.6 7215: *Jun 28 06:07:46.027: %CONTROLLER-5-UPDOWN: Controller T1 7/0:1, changed state to down

2013-05-29 11:17:37 Local7.Notice 192.168.1.6 7216: *Jun 28 06:07:46.027: %CSM-5-PRI: delete PRI at slot 7, unit 1, channel 23 with index 12

2013-05-29 11:17:37 Local7.Notice 192.168.1.6 7217: *Jun 28 06:07:46.027: %CONTROLLER-5-UPDOWN: Controller T1 7/0:2, changed state to down

2013-05-29 11:17:37 Local7.Notice 192.168.1.6 7218: *Jun 28 06:07:46.035: %CSM-5-PRI: delete PRI at slot 7, unit 2, channel 23 with index 13

2013-05-29 11:17:37 Local7.Notice 192.168.1.6 7219: *Jun 28 06:07:46.039: %CONTROLLER-5-UPDOWN: Controller T1 7/0:12, changed state to down

2013-05-29 11:17:37 Local7.Notice 192.168.1.6 7220: *Jun 28 06:07:46.047: %CSM-5-PRI: delete PRI at slot 7, unit 12, channel 23 with index 11

2013-05-29 11:17:37 Local7.Notice 192.168.1.6 7221: *Jun 28 06:07:46.047: %CONTROLLER-5-UPDOWN: Controller T1 7/0:13, changed state to down

2013-05-29 11:17:37 Local7.Notice 192.168.1.6 7222: *Jun 28 06:07:46.055: %CSM-5-PRI: delete PRI at slot 7, unit 13, channel 23 with index 4

2013-05-29 11:17:37 Local7.Notice 192.168.1.6 7223: *Jun 28 06:07:46.055: %CONTROLLER-5-UPDOWN: Controller T1 7/0:14, changed state to down

paolo bevilacqua · ‎06-01-2013

You can try some loop commands under controller T1.

If that doesn't work, there is nothing that you can do about except stop paying the bill untill they fix it.

cboulanger · ‎06-04-2013

I suggest you use the following controller command:

loopback network ignore

The description mentions "Ignore the remote line loopback reqs from NI". This should prevent your AS5400XM to automatically activate line loopback.

paolo bevilacqua · ‎06-05-2013

cboulanger wrote:

I suggest you use the following controller command:

loopback network ignore

The description mentions "Ignore the remote line loopback reqs from NI". This should prevent your AS5400XM to automatically activate line loopback.

Correct, but chances are that when some remote device is erroneously trying to command remote loopback, traffic will not pass anyway.