
DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-682DS1 CONV-BD
9
Far-end DS1 Converter Circuit Pack Loopback
Test (#788)
This test is destructive.
This test is executed by the TN574 DS1 Converter circuit pack only. Test #790
covers this testing for the TN1654 DS1 Converter.
This test starts at the DS1 CONV circuit pack whose equipment location was
entered and loops all fiber timeslots at the far edge Fiber Optic Interface of the
DS1 CONV circuit pack at the other end of the DS1 CONV Complex. See
diagram below.
Every part of this test is executed under firmware control and the result is sent
back to the maintenance software. Test is executed by sending digital data
Table 9-263. TEST #787 Reset Board
Error
Code
Te st
Result Description/ Recommendation
2100 ABORT Could not allocate the necessary system resources to run this test.
2300 ABORT The downlink message necessary to run this test could not be sent.
2301 ABORT The timer could not be set before sending the downlink message necessary to
run this test.
1. Retry the command at 1-minute intervals a maximum of 3 times.
2316 ABORT Fiber link is not administered. Administer the DS1 CONV fiber link via the add
fiber-link command.
2321 ABORT DS1 CONV circuit pack is not busied out. Busyout the DS1 CONV circuit pack
via the busyout board command.
2500 ABORT Internal system error
1. Retry the command at 1-minute intervals a maximum of 3 times.
PASS Reset sequence was executed successfully. This test result does not indicate if
the firmware diagnostic tests have passed. Display error log via the display
errors command to see if any one of the diagnostic firmware test have failed,
this will be indicated by an entry of error type 1 for this circuit pack location, and
the alarm log will have an entry of ON-BOARD MAJOR alarm, display the alarm
log via the display alarms command.
0NO
BOARD
The system software found no board.
1. Reset the board.
2. Remotely retry the command.
Continued on next page