PKT-BUS (Packet Bus)
Issue 5 October 2002
1459
555-233-119
System Technician-Demanded Tests: Descriptions
and Error Codes
Always investigate tests in the order presented in the following tables when you
are inspecting errors in the system. By clearing error codes associated with the
Packet Circuit Pack Audit Test, for example, you may also clear errors generated
from other tests in the testing sequence.
Maintenance/Test Circuit Pack Query Test (#572)
This test queries the Maintenance/Test Packet Bus port about the state of health
of the Packet Bus. If the Maintenance/Test circuit pack indicates that the Packet
Bus has faults, the test fails. The corresponding failure code describes the
severity, type, and number of faults. The test passes if the Packet Bus is fault-free.
NOTE:
A Maintenance/Test circuit pack is usually not present in the system unless
the customer has purchased this circuit pack to use for ISDN-PRI test calls,
or to enhance the system’s ability to quickly recognize a Packet Bus failure.
Order of Investigation
Short Test
Sequence
Long Test
Sequence
D/ND
1
1.
D = Destructive; ND = Nondestructive
Packet Circuit Pack Audit Test (#573)
X
X
ND
Maintenance/Test Circuit Pack Query Test (#572)
X
X
ND
Table 388.
TEST #572 Maintenance/Test Circuit Pack Query Test
Error
Code
Test
Result
Description/ Recommendation
1006
ABORT
The Packet Bus port of the Maintenance/Test circuit pack is out of service.
1. Determine if the port is busied out. If so, release the port by entering the
release port PCSS04 command. Re-enter the test command.
1142
ABORT
No Maintenance/Test circuit pack Packet Bus port is in service in this system.
1. The Maintenance/Test Packet Bus Port may not be present. If the port is
present, and if it is busied out or has failed, release or replace the circuit
pack. If there is no Maintenance/Test circuit pack, ignore the results of this
test.
2000
ABORT
The test timed-out while waiting for an uplink CCMS response from the
Maintenance/Test Packet Bus port.
1. Retry the command at 1-minute intervals a maximum of 5 times.
2. If the test continues to abort, check for problems with the
Maintenance/Test Packet Bus port.
Continued on next page