Demand test descriptions and error codes - Avaya Support

ATM Remote Layer 3 Query (#1291)
ATM Remote Layer 3 Query (#1291)
The ATM Remote Layer 3 Query Test queries the far-end switch or terminal adapter to
determine whether the signaling connection is functioning properly at Layer 3. It selects a
B-Chel in the in-service or maintenance service state and sends an ISDN Layer-3 SERVice
message, which requires a response from the far end. The test is not performed if there are no
B-Chels in an appropriate ISDN service state (for example, when none are administered or they
are all out of service).
Note:
Note: The service state can be displayed by using the status trunk grp#/mem# or
status pri-endpoint command.
A PASS only indicates that a message was successfully sent to the far-end switch or terminal
adapter. The ISDN PRI Specification allows up to 2 minutes for a response. Check the Error Log
for ATM-SGRP errors of type 2305 for evidence of an ATM Remote Layer 3 Query failure.
This test checks the communication path from the processor, through the TDM/packet bus and
ATM Interface circuit pack, and on to the far-end switch or terminal adapter. It is designed to
ensure that the communication path between the switch and the far end is up and operational,
and that the two endpoints can properly exchange ISDN control messages.
This test runs on ATM-SGRP (ATM Signaling Group).
Table 508: ATM Remote Layer 3 Query Test (#1291) 1 of 2
Error
Code
Test
Result
Description / Recommendation
1006 ABORT There are no associated B-Chels in an ISDN “in-service” or
“maintenance” service state. This is a NORMAL ABORT.
1. Administer or release an ISDN trunk or PRI endpoint before retrying
the test. For an ATM trunk, use status trunk grp#/mem# to
verify the ISDN trunk state.
2. Retry this test when at least one B-Chel is in the “in-service” or
“maintenance” states.
1113 ABORT The signaling chel is down. Therefore, no messages can be sent to the
far-end switch or terminal adapter.
1. Examine the results of Test #636, and follow the recommendations
for Primary Signaling Link Hardware Check (#636).
2100 ABORT Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1 of 2
Issue 5 May 2009 1631