Remote Layer 3 Query (#637)

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.

Tests #639 and #636 check the health of the D-channels and DS1 Interface Media Modules. This test goes one step further by checking the communication path from the processor, and on to the far-end switch or terminal adapter. A special ISDN message is sent to the far-end switch or terminal adapter, which must respond within a specified amount of time. This test 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.

Table 39. TEST #637 Remote Layer 3 Query �
Error Code	Test Result	Description/ Recommendation
1006	ABORT	There are no associated B-channels in an ISDN "in-service" or "maintenance" service state. This is a NORMAL ABORT. Administer or release an ISDN trunk or PRI endpoint before retrying the test. For an ISDN trunk, use the status trunk group#/member# command to verify the ISDN trunk state. For a PRI endpoint use status pri-endpoint extension. Then, retry this test when at least one B-channel is in the "in-service" or "maintenance" states.
1113	ABORT	The signaling channel is down. Therefore, no messages can be sent to the far-end switch or terminal adapter. Examine the results of Tests #636 and #639 and follow recommendations provided there.
2100	ABORT	Could not allocate the necessary system resources to run this test. Retry the command at 1-minute intervals a maximum of 5 times.
2500 or none	ABORT	Internal system error OR Administration Problem Determine if any B-channels are administered. If there are none, then this is a normal ABORT, since this test cannot run unless at least one B-channel is administered. If at least one B-channels is administered, there is an internal system error. Retry the command at 1-minute intervals a maximum of 5 times.
	FAIL	Internal system error. See description of ABORT with error code 2500.
	PASS	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 reply. Check the Error Log for ISDN-SGR (ISDN-PRI Signaling Group) for errors of type 2305 for evidence of a Remote Layer 3 Query failure. If no new errors were logged since this test was run, then this switch and the far-end switch or terminal adapter can exchange call control messages. If there is still a problem with a particular ISDN trunk or PRI endpoint, busyout the trunk and run the long test sequence, paying particular attention to the results of Test #258 (ISDN Test Call).
Any	NO BOARD	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 DS1-MM 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 issue the busyout board command. Issue the reset board command. Issue the release busy board command. Issue the test board long command. This should re-establish the linkage between the internal ID and the port.