User Manual

Chapter 13 ● Loopback testing backhaul links
164 Release 2.0, 910056 Rev01d
Performing external loopback tests on backhaul links
This procedure explains how to perform loopback tests on backhaul links. It is assumed an external
loopback has already been installed on each backhaul. (See Looping back T1/E1 backhaul links
on page 161
and Looping back Ethernet backhaul links
on page 162). A CLI session must be active. (See Establishing the
CLI/serial connection on page 135.) The node must be in diagnostic mode. (See Entering diagnostic mode
and configuring test parameters on page 163.) If the backhaul is T1 or E1, diagnostic parameters must have
been set. (See Entering diagnostic mode and configuring test parameters
on page 163.)
1. Enter the CLI command to start the loopback test.
The command is: commsend <number of tests> <ports>
Where:
• <number of tests> specifies the number times each port is to be tested. The valid range is
between (0 – 100000).
• <ports> specifies the names of the ports to be tested. See Table 24
.
For example, the following command would start the loopback test for a system with two E1 backhaul
links: commsend 10 T1 T2
Table 24 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
NOTE
If your node uses two Ethernet backhaul links (a primary and a
redundant), you need to check them separately. First, establish a
CLI connection with the primary BIO/SC and run the loopback
test, then establish a CLI connection with the redundant BIO/SC
and run the loopback test. You can simply unplug the laptop CLI
cable from the primary BIO/SC craft port and plug it into the
redundant BIO/SC craft port. The CLI command to run the test is
the same: commsend <number of tests> fenet1.