Filter
Top Products
DEFINITY ECS Release 8.2 Maintenance for R8.2csi
555-233-119 Issue 1
April 2000
Maintenance Objects
3-621DS1-BD (DS1 Interface Circuit Pack)
3
Table 3-256. TEST #1227 ICSU Status LEDs Test
Error
Code
Tes t
Result Description/ Recommendation
ABORT Internal system error
1. Retry the command at 1-minute intervals a maximum of 5 times.
1005 ABORT The ICSU Status LEDs test can not be executed for the current configuration.
The test applies only to TN767E or later DS1 circuit packs administered for
24-channel operation (1.544 bit rate).
1. If the circuit pack is a TN767E or later suffix DS1 circuit pack, then retry the
command.
1951 ABORT The ICSU Status LEDs Test can not be executed because a 120A1 or later suffix
CSU Module or a 401A or later suffix T1 Sync Splitter is not physically installed.
If using a 120A1 CSU Module/T1 Sync Splitter, physically connect it to the
TN767E board on the back of 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 for a maximum of 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.
0NO
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. Check to ensure that the board 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 if the board is hyperactive. If this is the case, the board is shut
down. Reseating the board will re-initialize the board.
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