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-964PI-LINK (Processor Interface Link)
10
Table 10-323. TEST #182 Processor Interface Loop Around Test
Error
Code
Test
Result Description/Recommendation
1 ABORT Link was not busied out via system technician.
1. Busyout the link via the busyout link lnk-no command.
2. Retry the test command.
2
4
9
ABORT 1. Retry the command at 1-minute intervals a maximum of 5 times.
16
80
84
85
93
94
102
ABORT Internal system error or possible TN765 PI-BD failure.
1. Retry the command at 1-minute intervals a maximum of 5 times.
2. If the test continues to abort, then reset the PI-BD via the test interface
PCS long system technician command.
3. If problem still exists, replace the TN765 PI-BD.
12 FAIL PI-BD reported that Loop Around Test failed.
1. Retry the test.
2. If it continues to fail, try resetting the circuit pack by the test interface
PCS long command. This TEARS down all other links on this circuit
pack (DCS, AUDIX, ISDN, etc.).
3. If the problem still exists, replace the TN765 circuit pack.
PASS The on-board Loop Around Test on the TN765 circuit pack passed. Most of
the hardware on the circuit pack was tested except for the TDM Bus
buffers. If problem is isolated to TN765 and this test passes, then replace
TN765 circuit pack since TDM Bus buffers could be at fault.
13 ABORT The TN765 circuit pack has not been reset yet or is currently being reset.
1. Retry the command at 1-minute intervals a maximum of 5 times.
2. If test continues to abort with error code 13, then check status of all
BX.25 and/or ISDN-PRI links on this TN765 via the status link lnk-no
command. If all links are not in-service, then reset the TN765 using the
test interface PCS long command.
3. If the TN765 fails to reset, refer to the PI-SCI section of this manual.
4. Retry the test link lnk-no command.
5. If the test still aborts with error code 13 or from step 2, and some links
are in-service and an error code is still present, escalate the problem.
Continued on next page