
DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-823EXP-INTF (Expansion Interface Circuit Pack)
9
Expansion Interface Control Channel Test (#316)
This test is nondestructive. If an Expansion Interface circuit pack is a standby
Expansion Interface circuit pack (yellow LED off) or if the Expansion Interface is
active in the PPN (yellow LED on), this test queries the Expansion Interface circuit
pack for its circuit pack type and vintage information. If the Expansion Interface
circuit pack is an active Expansion Interface circuit pack in the EPN (yellow LED
on long off short) the Expansion Interface Control Channel test checks to see if
the Expansion Interface circuit pack can communicate with other circuit packs in
the EPN using the EPN TDM bus.
PASS When this test (#242) and the EI Local Looparound Test #240 pass, this
indicates that the EI board is functioning properly, but it does not verify that the
optical portion of the lightwave transceiver is functioning.
1. Issue the test board UUCSS command on the EI board on both ends of
fiber. If this test passes from both sides, but other tests fail, such as #241,
this condition indicates either a faulty lightwave transceiver or the fiber itself
has failed. To determine if either a lightwave transceiver or the fiber itself
has failed, execute the EI Manual Loopback procedure described in a
previous section.
NOTE:
Test #242 can only be run from both EI s if they are the standby pair and
the active pair is working properly.
2. If this EI board is failing other tests, execute the EI Manual Loopback Test.
3. If problems still exist after the EI Manual Loopback Procedure indicates
both EI boards and both lightwave transceivers are healthy, manually
check out the building fiber. Verify that each optical fiber connects to a
transmitter at one end and a receiver at the other.
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 UUCSS
command.
3. Run the test again. If it fails, the ID chip on board may be bad. Replace the
board and retest.
Table 9-312. TEST #242 Expansion Interface Lightwave Transceiver Looparound — Continued
Error
Code
Tes t
Result Description/ Recommendation
Continued on next page