Lucent Technologies lucent Server User Manual


  Open as PDF
of 2392
 
DEFINITY Enterprise Communications Server Release 6
Maintenance for R6vs/si
555-230-127
Issue 1
August 1997
Maintenance Object Repair Procedures
Page 10-906OPS-LINE (DS1 OPS Line)
10
2000 ABORT The test was aborted because response to the test was not received within
the allowable time period.
1. Retry the command at 1-minute intervals for a maximum of 5 times.
2. If the test aborts with error code 2000 again, run short test sequence on
the associated DS1-BD or UDS1-BD. If tests 138 through 145 on the
associated DS1-BD or UDS1-BD are also aborting with error code 2000,
hyperactivity on the board or facility is indicated. In this case, the
hyperactivity problem should be dealt with first.
3. If the test continues to abort and the board is OK, escalate the problem.
2012 ABORT The test was aborted due to a system error.
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.
2. If the test continues to abort, escalate the problem.
1 FAIL Internal System Error.
1. Look for DS1-BD errors in the Hardware Error Log. If present, refer to the
DS1-BD (DS1 Interface Circuit Pack) Maintenance documentation.
2. If a channel multiplexer is used as the remote DS1 endpoint to which the
station connects, refer to the multiplexer vendor’s maintenance
document for diagnosis.
3. Retry the command at one-minute intervals a maximum of five times.
4. If the test continues to fail, escalate the problem.
PASS The station hook states in both switch software and DS1 Interface circuit pack
are consistent.
0
2012
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. Check to ensure that the board translations are correct. Use the list
config command, and resolve any problems that are found.
2. If the board was found to be correctly inserted in step 1, issue the
busyout board command.
3. Issue the reset board command.
4. Issue the release busy board command.
5. Issue the test board long command. This should re-establish the linkage
between the internal ID and the port. If this is not the case, dispatch to
check to ensure that there is a valid board inserted.
Table 10-306. TEST #312 DS1OPS Switchhook Inquiry Test — Continued
Error
Code
Test
Result Description/ Recommendation
Continued on next page