DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126 Issue 4
June 1999
Maintenance Object Repair Procedures
9-827EXP-INTF (Expansion Interface Circuit Pack)
9
3 FAIL The reset over the optical fiber failed.
1. Execute the test board UUCSS command on the PPN neighbor EI circuit
pack located on the opposite end of the fib er from this EI circuit pack. If
Test #238 does not pass, follow the maintenance procedure associated
with this test result. Then perform the reset again.
2. If the EI circuit pack is in the EPN, temporarily remove the EPN
Maintenance circuit pack.
3. Repeat the reset board UUCSS command.
4. Reinsert EPN Maintenance circuit p ack if it was removed.
5. If the symptoms match those described in the ‘‘EI and Tone-Clock
Interactions’’ section, follow those guidelines.
6. Check the Error Log for the EPN T one-Clock errors that were resolv ed when
the EPN went down. These errors may have been resolved BECAUSE the
EPN went down. When there is no Tone-Clock generating the system clock
on an EPN, then an Expansion Interface (EI) circuit pack can only be reset
once. All subsequent reset attempts fail. It is also possible that the system
itself may have already tried to reset the EI circuit pack. Refer to ‘‘TONE-BD
(Tone-Clock Circuit Pack)’’ for Tone-Clock problems.
7. If the reset still fails, execute the Manual Loop Back Procedure on the
opposite PPN EI circuit pack. This procedure is described in the section
preceding the Error Log Entries and Test to Clear V alue s table for this MO. If
the EI circuit pack and the lightwave transceiver are healthy, the problem is
the EI circuit pac k and its lightwave transc eiver on the EPN end of the fiber
or the fiber itself. Test the EPN EI circuit pack with the manual loop back
procedure and investigate the test results.
PASS The EI was successfully reset. Remove the Expansion Interface circuit pack
from the busyout state by us ing the release board UUCSS command.
1. Execute test board UUCSS short command. Refer to errors for each test.
0NO
BOARD No board was detected by the test.
1. Resolve either wrong board (error 125) or no board (error 131) issues.
2. Check that the board is properly translated and inserted. If so, chec k 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-314. TEST #336 Expansion Interface Reset Test — Continued
Error
Code Test
Result Description/ Recommendation
Continued on next page