DS1-BD (DS1 Interface Circuit Pack)
Issue 1 May 2002
8-633
555-233-143
CSU Equipment Loop-Back Test (#1210)
This test is destructive.
The CSU ELB (Equipment Loopback) test causes a loop back at the near-edge of
the local 120A CSU module or T1 sync splitter, and tests the connection from the
TN767E DS1 board to the CSU module/T1 sync splitter (DS1 board edge
interconnecting cable, and CSU module/T1 sync splitter edge). This test will only
be performed if the 120A CSU module/T1 sync splitter is present, administered,
and connected to a 1.544-Mbps TN767E DS1 circuit pack behind the port carrier.
The test is destructive and can only be initiated by a technician-demanded
test ds1-loop UUCSS ds1/csu-loopback-tests command.
All trunks or ports on the DS1 Interface circuit pack must be busied out via the
system technician busyout board command before running the ELB test.
PASS
The BLB test executed successfully. The test pattern was transmitted and
received successfully up to the TN767E DS1 board edge.
0
NO
BOARD
The test could not relate the internal ID to the port (no 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
command to administer the DS1 interface if it is not already administered.
2. If board was already administered correctly, check the error log to
determine whether the board is hyperactive. If so, the board was shut
down. Reseating the board will re-initialize it.
3. If the board was found to be correctly inserted in step 1, issue the busyout
board command.
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 link between the internal ID and the port.
Table 8-254.
Test #1209 DS1 Board Loop-Back Test —
Continued
Error
Code
Test
Result
Description / Recommendation
Continued on next page
Summary of Contents for S8700 Series
Page 50: ...Maintenance Architecture 555 233 143 1 26 Issue 1 May 2002 ...
Page 74: ...Initialization and Recovery 555 233 143 3 12 Issue 1 May 2002 ...
Page 186: ...Alarms Errors and Troubleshooting 555 233 143 4 112 Issue 1 May 2002 ...
Page 232: ...Additional Maintenance Procedures 555 233 143 5 46 Issue 1 May 2002 ...
Page 635: ...status psa Issue 1 May 2002 7 379 555 233 143 status psa See status tti on page 7 406 ...
Page 722: ...Maintenance Commands 555 233 143 7 466 Issue 1 May 2002 ...