BRI-SET, ASAI-ADJ, BRI-DAT
Issue 1 May 2002
8-367555-233-143
System Technician-Demanded Tests:
Descriptions and Error Codes
When inspecting errors in the system and deciding which ones to address, always
investigate errors associated with the circuit pack and port first. Clearing these
error codes first may also clear errors generated against the endpoint. When
every circuit pack and port error has been cleared, and errors still exist against the
endpoint, always investigate errors in the order they are presented in the table
below. For example, by clearing error codes associated with the Signaling Link
Status test (#626), you may also clear errors generated from other tests in the
testing sequence.
Note:
a. Will execute the test port long PCSSpp command, and review the results
of the BRI Port Local LAN Loop Around test (#618) to verify the repair.
Signaling Link Status Test (#626)
This test determines the current status of the signaling link. This test passes if the
link is “bound” to an endpoint and fails if the link is “not bound.”
The definition of the term “bound” for a link depends upon the type of endpoint
and may depend on the successful completion of procedures at both Layers 2 and
3 of the protocol. The definition of “bound” for each type of endpoint is as follows:
■ BRI endpoints administered for MIM (management information
messages) initialization (multipoint):
NOTE:
An MIM is a level 3 message that conveys management and
maintenance information between a communications system and a
BRI terminal.
Order of Investigation
Short Test
Sequence
Long Test
Sequence D/ND
1
1. D = Destructive; ND = Nondestructive
Signaling Link Status test (#626) X X ND
BRI XID test (#628) X X ND
BRI Layer 3 Query (#629) X(a) X(a) ND
BRI Remote Loop Back (#627) X(a) ND
BRI Set Audits (#630) X(a) X(a) ND
BRI Vendor ID test (#631) X(a) ND
BRI Model/Vintage ID test (#632) X(a) ND
To Next Page
Loading...
