MA5612: How to perform loopback of E1 interface
|
Dears, in case you are using MA5612 as mobile backhaul access device, and delivery E1 services, if you need to check if a circuit is working you can do it in the following ways: 1. CBU_11VP2(config)# interface tdm 0/1 2. CBU_11VP2(config-if-tdm-0/1)# port 7 udt system 3. CBU_11VP2(config-if-tdm-0/1)#l loopback 7 local or CBU_11VP2(config-if-tdm-0/1)#loopback 7 remote the difference of local and remote loopback is the direction where the loop takes effect. For example if I choose local is because I want to check the circuit state from the MDU to the transport network side (I my case is to check if the circuit close in the BSC). If you choose remote, then you will check the state of the circuit between the MDU and the terminal device directly connected to the MDU (In my case is the BTS). Hope this information can be useful for somebody! |
| The function loopback is very useful for trouble shooting. |
| Loopback is very useful in troubleshooting. |
|
Thats right! Local loopback, also called inloop, is the loopback from the port processing module of the board to the backplane. In the local loopback, the signals that are transmitted from the backplane to the E1 port are directly sent back to the backplane to check whether the board that houses the E1 port can communicate with the backplane normally
Remote loopback, also called outloop, is the loopback from the port processing module of the board to the line. In the remote loopback, the signals that are transmitted from the peer device to the port processing module are directly sent back to the peer device to check whether the board that houses the E1 port can communicate with the peer device normally
|
|
More details in the document, see "Performing a Loopback on an E1 Port".
|
Reply 2 #
| I can not see the picture. |

Favorite (0)