DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-834EXP-INTF (Expansion Interface Circuit Pack)
9
Expansion Interface Test (#244)
This test is potentially very destructive and requires the Expansion Interface
circuit pack to be busied out prior to execution of this test.
The Expansion Interface Test, which is not a part of either the Short or the Long
Test Sequences, is executed via the reset board PCSS command where PCSS
is the address of the Expansion Interface circuit pack to be reset.
If the system only has one working Expansion Interface (EI) link between a pair of
port networks and one of the EI circuit packs must be reset, the action of busying
ANY FAIL The transmitted data packet was not received correctly by the Packet Interface
circuit pack. The failure may be in the EI under test, the DS1 CONV circuit
packs, or the intervening Center Stage components.
1. Test the Packet Interface circuit pack with the test packet- interface 1CS
command where C is the SPE carrier in a duplicated processor, and S is
the slot number the Packet Interface is located in. If the Packet Interface
circuit pack fails any tests, refer to “PKT-INTF”.
2. If the EI under test is located in an EPN in a high reliability system (2
PPN-to-CSS fibers in a simplex PNC), run the short test sequence on both
of the PPN EI boards and follow procedures for test #589.
3. Enter display errors and resolve any PKT-BUS errors.
4. Perform the ‘‘Fiber Fault Isolation Procedure’’
.
PASS Although this test has passed, there may be related problems on other EI s
used in connectivity to and from this EI. Software may have conducted tests on
these other components and determined that this board was functioning
properly and any problems were probably due to a problem with some other
connectivity component. Check the error and alarm logs for problems with
other EI circuit packs and resolve these errors.
1. Refer to other EI board tests if the link is not functioning correctly.
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, 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-315. TEST #589 Expansion Interface Packet
Interface Test — Continued
Error
Code
Tes t
Result Description/ Recommendation
Continued on next page
