Filter
Top Products
DEFINITY Enterprise Communications Server Release 6
Maintenance for R6vs/si
555-230-127
Issue 1
August 1997
Maintenance Object Repair Procedures
Page 10-638EXP-INTF (Expansion Interface Circuit Pack)
10
Expansion Interface Packet Interface Test (#589)
This test attempts to send a data packet from the TN778 Packet Control circuit
pack through any intervening Expansion Interface circuit packs and through the
Expansion Interface circuit pack to be tested. The path the data packet takes is
dependent on the location of the Expansion Interface circuit pack to be tested
and whether the Expansion Interface circuit pack is par of the Active link or
Standby link.
5016
5017
5018
5019
5032
5033
5048
5064
5080
5096
5112
FAIL Initialization failure: Expansion Interface circuit pack reset successfully
and restarted execution. But the Expansion Interface circuit pack detected
communication errors during the self-test phase of the hardware
initialization. The nature of the failure may prevent the Expansion Interface
circuit pack from communicating with its neighbor Expansion Interface
circuit pack on the opposite end of the fiber. The fault itself may be either
on the Expansion Interface circuit pack or on the lightwave transceiver.
1. If all other tests on this Expansion Interface circuit pack are passing
and no other errors have been logged against this circuit pack,
replacement of the lightwave transceiver or the circuit pack are
recommended, but not critical.
2. If all other tests on this Expansion Interface circuit pack are not
passing or other errors have been logged against this circuit pack, the
lightwave transceiver and/or the Expansion Interface circuit pack
should be replaced.
PASS The Expansion Interface was successfully reset, and it did restart
execution. Also, it passed all its initialization tests and detected a lightwave
transceiver. Remove the Expansion Interface circuit pack from the busyout
state by using the release board PCSS command.
1. Execute test board PCSS short command. Refer to errors for each
test.
0NO
BOARD
No board was detected by the test.
1. Check the error log for wrong board (error 125) or no board (error 131).
Resolve either of these issues, if applicable.
2. Check that the board is properly translated and inserted. If so, check
for hyperactivity (error 1538). If hyperactive, use the reset board
PCSS command.
3. Run the test again. If it fails, the ID chip on board may be bad. Replace
the board and retest.
Table 10-215. TEST #336 Expansion Interface Reset Test — Continued
Error
Code
Test
Result Description/ Recommendation
Continued on next page