Off-Line Distant-End Loopback Test; Off-Line Network Loopback Test - Avaya Communication Server 1000M Single Group Manual

Maintenance
Figure 65: Off-line Near-end loopback test
This test can also be issued with a distant modifier. Entering T D will cause your MCR card to
command the far-end MCR to run its Off-line Near-end Loopback test.
Note:
This command is limited to 10 minutes because you will be unable to stop the far-end MCR
from running the command.

Off-line Distant-end Loopback test

Test 3, the Off-line Distant-end Loopback test loops the distant-end signal back towards the
near end. You can perform the Off-line Distant-end Loopback test on the distant-end MCR. A
failure is detected if the MCR does not receive the data word that was sent. If a failure occurs,
the failure peg counter is incremented. This counter will saturate at 65,000 counts. At the end
of the test, the test results message will indicate how many failures occurred during the test.
A failure on test 3 indicates a far-end defective MCR Circuit Card or a bad T1 link.
Figure 66: Off-line Distant-end Loopback test

Off-line Network Loopback Test

Test 4, the Off-line Network Loopback test assumes that a loopback is configured somewhere
in the network. Test data is generated at the near-end MCR and received at the near end. You
can perform the Off-line Network Loopback test on the near end or the distant end. A failure
is detected if the MCR does not receive the data word within 100 ms. In this case, a failure peg
counter is incremented. This counter will saturate at 65,000 counts. At the end of the test, the
112 Mini-Carrier Remote Fundamentals
Comments? infodev@avaya.com
March 2013