BRI-SET, ASAI-ADJ, BRI-DAT
Issue 4 May 2002
10-297 555-233-123
ASAI adjunct or Avaya adjunct. Execute the test station extension sh
command and pay particular attention to the results of the BRI Layer 3
Query Test (#629). If this test fails, follow the repair procedure for Test
#629.
b. This error type indicates that the circuit pack has been removed or has
been insane for more than 11 minutes. To clear the error, replace or
reinsert the circuit pack.
c. This error occurs when the endpoint does not respond to the service state
query message sent to the adjunct or the endpoint. This error causes an
alarm to be raised. The alarm is retired when the switch receives a
response to the service state query to the endpoint or the adjunct.
For BRI endpoints, the Aux Data field for this error contains “0.” When it
occurs, execute the test station extension sh command and pay
particular attention to the results of the BRI Layer 3 Query Test (#629). If
this test fails, follow the repair procedure for Test #629.
When this error occurs for an ASAI or Avaya adjunct, the Aux Data field
indicates the state of the ASAI link or Avaya link and whether an invalid
response or no response was received to the query from the switch, as
shown in the following table:
(See “Status BRI-Port” in Chapter 8, “Maintenance Commands and
Trouble-Clearing Aids” for an explanation of the ASAI link states.)
For ASAI or Avaya adjuncts, the switch automatically queries the adjunct
every two minutes (and therefore the Layer 3 Query Test is not executed
for ASAI or Avaya adjuncts via a command issued from the G3MT
terminal). While alarmed for this error, the switch momentarily (for five
seconds) takes the associated port out-of-service every 15 minutes. This
action is taken in an attempt to stimulate recovery actions to be taken by
the adjunct.
Aux Data ASAI Link State Error
102 13-restarting No response to RESTART message
104 13-restarting Invalid response to RESTART message
152 13-restarted No response to Layer 3 query
154 13-restarted Invalid response to Layer 3 query
202 13-established No response to Layer 3 query
204 13-established Invalid response to Layer 3 query
To Next Page
Loading...
