Remote Layer 3 Query (#637) - Avaya G350 Maintenance Manual

Table 82: Primary Signaling Link Hardware Check (#636) 2 of 2
Error Test
Code Result
8 FAIL
PASS
Any NO
BOARD

Remote Layer 3 Query (#637)

This test will query the far-end switch or terminal adapter to determine if the signaling connection is
functioning properly at Layer 3. It will select a B-channel in the in-service or maintenance service state
and send an ISDN Layer 3 SERVice message, which requires a response from the far end (similar to
performing Test #256 on an ISDN trunk. The test will not be performed if there are no B-channels in an
appropriate ISDN service state (as when none are administered or they are all out of service).
NOTE:
The service state can be displayed by using the status trunk <trunk group/trunk
member> or status pri-endpoint command.
As is the case with Test #256 for an ISDN trunk, a PASS only indicates that a message was composed and
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 ISDN-SGR (ISDN-PRI Signaling Group) errors of type 2305 for
evidence of a Remote Layer 3 Query failure.
Maintenance of the Avaya G350 Media Gateway
June 2004
Avaya Communication Manager controlled maintenance
Description/ Recommendation
There is a problem with the MM710 or the ISDN-PRI Signaling Channel
(D-Channel). No ISDN trunk or PRI endpoint calls can be made until the
problem is resolved.
Consult the procedures for the MM710 and the ISDN-PRI Signaling
Channel (ISDN-LNK).
The basic physical connectivity of the primary D-channel is intact and
functional. One might try this test repeatedly to ensure the link is up and to
uncover any transitory problems.
The test could not relate the internal ID to the port (no board). This could be
due to incorrect translations, no board is inserted, an incorrect board is
inserted, or an insane board is inserted.
Ensure that the board translations are correct. Execute the add ds1
GGGVS command to administer the MG-DS1 interface if it is not already
administered.
If the board was already administered correctly, check the error log to
determine whether the board is hyperactive. If this is the case, the board is
shut down. Reseating the board will re-initialize the board.
If the board was found to be correctly inserted in step 1, then use the
busyout board command.
Use the reset board command.
Use the release busy board command.
Use the test board long command.
This should re-establish the linkage between the internal ID and the port.
ISDN-SGR (ISDN-PRI Signaling Group)
2 of 2
147