UDS1-BD (UDS1 Interface Circuit Pack)
Issue 1 May 2002
8-1781
555-233-143
2000
ABORT
Response to the test was not received within the allowable time period. This
may be due to hyperactivity. Error Type 1538 in the error log indicates
hyperactivity. The hyperactive circuit pack is out of service, and one or more of
the following symptoms may be exhibited.
1. The UDS1-BD tests (such as Tests #138 and #139) are aborting with error
code 2000.
2. The tests run on the ports of this circuit pack are returning a no-board
result.
3. A busyout or a release command has no effect on the test results.
4. A list config command shows that the circuit pack and the ports are
properly installed.
NOTE:
When hyperactivity occurs, the circuit pack is isolated from the system,
and all of its trunks are placed into the out-of-service state. The system
will try to restore the circuit pack within 15 minutes. When no faults are
detected for 15 minutes, the UDS1 interface circuit pack is restored to
normal operation. Every UDS1 Interface trunk is then returned to the
in-service state. Hyperactivity is often caused by the associated facility.
In such a case, faults (such as slips, misframes, or blue alarms) would
be entered in the error log. In addition, many hardware errors would be
logged against the associated trunk circuits. If the facility is OK and the
error occurs again after 15 minutes, replace the circuit pack.
2100
ABORT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
FAIL
UDS1 Interface circuit pack failed the CSU Equipment Loopback test.
1. Retry the test ds1-loop UUCSS ds1/csu-loopback-tests command.
2. If the ELB test continues to fail, then either the UDS1-BD board, the CSU
module/T1 sync splitter, or the I/O cable between the backplane and the
CSU module/T1 sync splitter (or any combination thereof) has failed.
Attempt to isolate the problem to one of these areas. Begin by replacing
the CSU module/T1 sync splitter and running the test ds1-loop UUCSS
ds1/csu-loopback-tests command again.
3. If the ELB test continues to fail, then replace the UDS1-BD board, and run
the test ds1-loop UUCSS ds1/csu-loopback-tests command again.
4. If the ELB test continues to fail, the problem could be in the I/O cable
between the backplane and the CSU module/T1 sync splitter.
Table 8-683.
Test #1210 CSU Equipment 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 ...