Avaya S8700 Maintenance Manual page 1358

For multi-connect configurations

Hide thumbs Also See for S8700:

Table of Contents

Maintenance-Object Repair Procedures

Table 8-255. Test #1210 CSU Equipment Loop-Back Test — Continued

Description / Recommendation

DS1 Interface circuit pack failed the CSU Equipment Loopback test.

1. Retry test ds1-loop UUCSS ds1/csu-loopback-tests.

2. If the ELB test continues to fail, then either the TN767E board, the CSU

3. If the ELB test continues to fail, then replace the TN767E board and run

4. If the ELB test continues to fail, the problem could be in the I/O cable

The ELB test executed successfully. The test pattern was transmitted and

received successfully over the connection from the TN767E DS1 board to the

near-edge of the 120A1 CSU module/T1 sync splitter.

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

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.

Issue 1 May 2002

module/T1 sync splitter, or the I/O cable between the backplane and the

120A1 CSU module or the 401A T1 sync splitter (or any combination

thereof) has failed. Attempt to isolate the problem to one of these areas.

Replace the CSU module/T1 sync splitter, and run test ds1-loop UUCSS

ds1/csu-loopback-tests again.

test ds1-loop UUCSS ds1/csu-loopback-tests again.

between the backplane and the 120A1 CSU module or the 401A T1 sync

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

Troubleshooting