READ THIS FIRST
*** WARNING ***
This article directs you to enter configuration mode in order to execute the commands. When performing these steps, session logging should be turned on to record commands entered, and extra care should be taken to verify the commands are being entered properly. Failure to do so could result in potentially critical information loss, up to and including loss of all device configuration.
*** WARNING ***
*** WARNING ***
Looping a circuit from remote equipment will cause connection to be lost unless an alternate means of connection is available. If connection is lost and there is no alternate means of connecting, you will be unable to remove the loop without physical access to the device.
*** WARNING ***
*** CAUTION ***
Looping a circuit will cause loss of connectivity for that connection. Ensure that intrusive testing is authorized and the connection is not in use.
*** NOTE ***
Initial Steps
Looping a circuit is a test in and of itself, as well as a tool to enable and enhance other testing methods. There are several types of loops available that can be broken down in to two groups - local and remote. Typically you will only loop from core equipment (A-end) to the remote location (Z-end) in order to verify whether a connectivity loss is on the carrier side or customer side. This article will cover the most commonly used local and remote loopbacks.
The most common core equipment you will be dealing with will be Cisco based. Core routers have several different types of controllers that may be used, each requiring a slightly different command set to loop the circuit.
Multichannel T1
configure terminal command: Router#configure terminalcontroller t1 [s/p] command: Router(config)#controller t1 3/4loopback local line command:Router(config-controller)#loopback local lineloopback remote iboc command: Router(config-controller)#loopback remote ibocshow controller t1 [s/p] brief command. The resulting output should state that the controller is in loopback configuration:Router#sh controller t1 3/4 briefT1 3/4 is up. (Local Line Loopback) Applique type is Channelized T1 Cablelength is long gain36 0db Receiver has no alarms.no loopback command:Router(config-controller)#no loopbackPA-MC-T3 / PA-MC-2T3+ / SPA-2XCT3 / 2CT3+
configure terminal command: Router#configure terminalcontroller t3 [c/s] command: Router(config)#controller t3 1/0t1 [p] loopback local command: Router(config-controller)#t1 1 loopback localt1 [p] loopback remote line fdl bellcore command: Router(config-controller)#t1 1 loopback remote line fdl bellcoreshow controller t3 [c/s/p] brief command. The resulting output should state that the controller is in loopback configuration: Router#sh controller t3 1/0/1 briefT3 1/0 is up. T1 1 is down timeslots: 1-24 FDL per AT&T 54016 spec. Configured for locally looped Currently in locally looped Transmitter is sending AIS. Receiver is getting AIS. Framing is ESF, Clock Source is Internalshow interface serial [c/s/p:x] command: Router#show interface serial 1/0/1:0Serial1/0/1:0 is up, line protocol is up (looped) Hardware is PA-MC-T3 MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255no t1 [p] loopback command: Router(config-controller)#no t1 1 loopbackSPAC-4XT3/E3 / M1T-T3+ pa
Router#configure terminalRouter(config)#interface serial [s/p]loopback local command:Router(config-if)#loopback localloopback remote command:Router(config-if)#loopback remoteshow controller t3 [s/p] brief command. The resulting output should state that the controller is in loopback configuration.show interface serial [s/p] command.no loopback command:Router(config-if)#no loopbackRouter#conf terminalinterface t1 [s/p] command:Router(config)#int t1 1/1loopback remote line fdl command:Router(config-t1 [x])#loopback remote line fdlno loopback command command:Router(config-t1 1/1)#no loopback*** NOTE ***
Router#testRouter/test#t1 0/0 loopback remote line ansi fdl command:Router/test/t1 (p/s)#loopback remote line ansi_fdlRouter/test/t1 (0/0)#no loopbackCurrently we do not have access to any Juniper equipment that carries T1/T3 interfaces. For reference, information on monitoring and troubleshooting can be found here: https://www.juniper.net/documentation/en_US/junos/topics/topic-map/interfaces-investigate-interface-steps-and-commands.html
If a circuit goes down and you are able to loop to the smartjack, the problem most likely lies with the customer premise equipment.
If a circuit goes down and you are unable to loop to the smartjack, the problem most likely lies with the line carrier.
Interface Indications
The state of the interface once a loop has been applied can be used as an additional indicator for troubleshooting.
Advanced Testing
There are several follow up troubleshooting steps that can be taken while the circuit is still looped. See Advanced T1 Troubleshooting for in-depth instructions.
====[[Troubleshooting T3 Circuits]]====
http://www.cisco.com/c/en/us/support/docs/asynchronous-transfer-mode-atm/permanent-virtual-circuits-pvc-switched-virtual-circuits-svc/10435-d3e3-tshoot.html
http://en.wikipedia.org/wiki/Remote_error_indication