Avaya S8700 Maintenance Manual page 1370

Maintenance-Object Repair Procedures
Table 8-258. Test #1213 Far CSU Loop-Back Test — Continued
Error Test
Code Result Description / Recommendation
2 FAIL The far CSU Loopback test was not set up properly. The DS1 Interface circuit
pack could not put the far-end CSU into loop-back mode.
3 FAIL The far CSU Loopback test was not set up properly. The framed 3-in-24 test
pattern, generated by the DS1 Interface circuit pack and looped back through
the far-end CSU, could not be detected by the DS1 circuit pack.
1. Retry test ds1-loop UUCSS far-csu-loopback-test-begin.
2. If the Far CSU Loopback test continues to fail with this error code, the
PASS The Far CSU Loopback test has successfully began executing. The test will
continue to run until the system technician enters test ds1-loop UUCSS
end-loopback/span-test or the release board UUCSS.
0 NO The test could not relate the internal ID to the port (no board).
BOARD
This could be due to incorrect translations, no board is inserted, an incorrect
board is inserted, or an insane board is inserted.
1. Verify that the board's translations are correct. Use the add ds1 UUCSS
2. If board was already administered correctly, check the error log to
3. If the board was found to be correctly inserted in step 1, issue the busyout
4. Issue the reset board command.
5. Issue the release busy board command.
6. Issue the test board long command.
8-648 Issue 1 May 2002
problem could be with the TN767E board, the far-end CSU equipment, or
somewhere in between. Run test ds1-loop UUCSS
cpe-loopback-jack-test-begin to see if the CPE Loopback Jack test that
is closer to the TN767E board is successful. (If a CPE loop-back jack
device is not being used, then run test ds1-loop UUCSS
ds1/csu-loopback-tests to see if these even closer loop-back tests
succeed). If the closer loop-back test fails, follow the maintenance strategy
associated with that loop back
command to administer the DS1 interface if it is not already administered.
determine whether the board is hyperactive. If so, the board was shut
down. Reseating the board will re-initialize it.
board command.
This should re-establish the link between the internal ID and the port.
Continued on next page
555-233-143