Maintenance-Object Repair Procedures
555-233-143
8-658
Issue 1 May 2002
Table 8-262.
Test #1227 ICSU Status LEDs Test
Error
Code
Test
Result
Description / Recommendation
ABORT
Internal system error
1. Retry the command at 1-minute intervals up to 5 times.
1005
ABORT
The ICSU Status LEDs test cannot be executed for the current configuration.
The test applies only to TN767E or later DS1 circuit packs administered for
24-channel (1.544-Mbps) operation.
1. If the circuit pack is a TN767E (or higher-suffixed) DS1 circuit pack, then
retry the command.
1951
ABORT
The ICSU Status LEDs test cannot be executed because a 120A1 (or
higher-suffixed) CSU module or a 401A (or higher-suffixed) T1 sync splitter is
not physically installed. If using a 120A1 CSU module
/T1 sync splitter
,
physically connect it to the TN767E board behind the port carrier. Otherwise,
ignore this abort.
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.
2500
ABORT
Internal system error.
1. Retry the command.
PASS
The ICSU Status LEDs test executed successfully. A PASS result, however,
does not necessarily mean that the status LEDs behaved properly. It only
means that the software successfully attempted to light the status LEDs. This
is a visual test. The service technician must visually exam the behavior of the
LEDs while the test is running. The LEDs are functioning properly if the four
status LEDs are lit red for 5 seconds, then lit green for 5 seconds, then lit
yellow for 5 seconds. If the LEDs behave differently, escalate this problem.
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 linkage between the internal ID and the port.
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 ...