Avaya S8700 Maintenance Manual page 2517

UDS1-BD (UDS1 Interface Circuit Pack)
Table 8-686. Test #1213 Far CSU Loop-Back Test — Continued
Error Test
Code Result Description / Recommendation
3 FAIL The Far CSU Loopback test was not set up properly. The framed 3-in-24 test
pattern, generated by the UDS1 Interface circuit pack and looped back through
the far-end CSU, could not be detected properly by the UDS1 circuit pack.
1. Retry the test ds1-loop UUCSS far-csu-loopback-test-begin command.
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 the test ds1-loop UUCSS
end-loopback/span-test command or the release board UUCSS command.
0 NO The test could not relate the internal ID to the port (no board). This could be
BOARD 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. Execute the add ds1
2. If the board was already administered correctly, check the error log to
3. If the board was found to be correctly inserted in step 1, then issue the
4. Issue the reset board command.
5. Issue the release busy board command.
6. Issue the test board long command.
This should re-establish the linkage between the internal ID and the port.
555-233-143
problem could be with the UDS1-BD board, the far-end CSU equipment, or
somewhere in between. Run the test ds1-loop UUCSS
cpe-loopback-jack-test-begin command to see if the CPE Loop-Back
Jack test which is closer to the UDS1-BD board is successful. (If a CPE
Loop-back Jack device is not being used, then run the test ds1-loop
UUCSS ds1/csu-loopback-tests command to see if these even closer
loop-back tests succeed). If the closer loop-back test fails, follow the
maintenance strategy associated with that loopback.
UUCSS command to administer the UDS1 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.
busyout board command.
Continued on next page
Issue 1 May 2002 8-1795