User Manual

Troubleshooting failed backhaul links
IP-RN 8000 Installation & Commissioning Guide 167
For example, the following command would start the loopback test for a system with two E1 backhaul
links:
BIOSC>commsend 10 T1 T2
4. Evaluate the results.
After the test is complete, the table of data displays for each backhaul tested.
Number of Transmitted Frames : x
Number of Received Frames : x
Number of Error Frames : x
Frames without valid Test ID : x
Frames with invalid Data : x
Frame Error Rate : x
Error Counters
Rx Frame Length Violations ... x
Rx Non-octet alignment ... x
Rx Abort Frames ... x
Rx CRC Errors ... x
If the Number of Received Frames does not equal the Number of Transmitted
Frames, or if there are any errors counted, the node has a fault and you need to contact Airvana. This
is the end of this procedure.
If the Number of Received Frames does equal the Number of Transmitted Frames
and there are no errors, you must troubleshoot the following:
• the backhaul cable
• the physical loopback installed earlier in the loopback testing process
• the backhaul wiring into the punch block
• any external equipment the backhaul cable is attached to, for example a digital cross connect
5. Exit diagnostics mode
Enter the following command to reset the node:
BIOSC>reset
Allow the node to reboot to completion, skipping the diagnostic mode required for loopback testing.
This procedure is complete. Go to Removing physical loopbacks
on page 168.
Table 26 Specifying the backhaul links to be tested
<ports> Indicates the following ports to be tested
T1 The first T1 or E1 backhaul
T2 The second T1 or E1 backhaul
T3 The third T1 or E1 backhaul
T4 The fourth T1 or E1 backhaul
FENET1 The primary Ethernet backhaul