Layer 2 Status Test (#647)

The Layer 2 Status Test checks the layer 2 status of the ISDN-PRI Signaling Channel (D-channel). This test will fail if there is a hardware failure or a facility problem, or if the primary and secondary ISDN-PRI D-channels are not administered correctly.

The Primary and Secondary Signaling Link Hardware tests (test 637 and 639) and the Remote Layer 3 Query test (test 637) will detect most problems caused by hardware failures or incorrect administration. However, the Layer 3 test (test 637) cannot detect end-to-end transmission problems with the Standby D-channel since Layer 3 messages are not sent on the standby channel.

The SYS-LINK Maintenance Object reports Layer 2 ISDN-PRI D-channel problems. The Layer 2 Query test is provided to detect D-Channel Layer 2 failures and generate an associated Warning alarm independent of the hardware configuration used for the D-channels.

Table 41. TEST #647 Layer 2 Status Query Test �
Error Code	Test Result	Description/ Recommendation
1132	ABORT	Internal system error: The port location for the primary ISDN-PRI D-channel is not known. This condition should not be possible since an administered DS1 Media Module must be specified when a Signaling Group is administered: Retry the command at one minute intervals a maximum of five times.
1134	ABORT	Internal system error: The associated DS1 Media Module is not administered. This condition should not be possible since an administered DS1 Media Module must be specified when a Signaling Group is administered. Retry the command at one minute intervals a maximum of three times.
2500	ABORT	Internal system error: Retry the command at one minute intervals a maximum of five times.
1	FAIL	Layer 2 of the primary signaling channel is down: Examine the results of the Primary Signaling Test (#636) and follow recommendations provided there. If test #636 passes, the Layer 2 Query test may still fail if the Signaling Channel at the far end has not been administered correctly or if the Signaling Channel has been busied out. Verify that the Primary Signaling Channel (D-channel) at the far end has been administered correctly. Verify that the DS1 port used for the Primary D-channel has not been busied out at the far end.
2	FAIL	Layer 2 of the secondary signaling channel is down. Examine the results of Secondary Signaling Link Hardware Test (#639) and follow recommendations provided there. If tests #639 passes, the Layer 2 Query test may still fail if the Signaling Channel at the far end has not been administered correctly or if the Signaling Channel has been busied out. Verify that the Secondary Signaling Channel (D-channel) at the far end has been administered correctly. Verify that the DS1 port used for the Secondary D-channel has not been busied out at the far end.
3	FAIL	Both the primary and secondary are down. Examine the results of the Primary and Secondary Signaling Link Hardware Tests (#636 and #639) and follow recommendations provided there. If tests #636 and #639 pass, the Layer 2 Query test may still fail if the Signaling Channel at the far end has not been administered correctly or if the Signaling Channel has been busied out. Verify that the Primary and Secondary Signaling Channel (D-channel) at the far end has been administered correctly. Verify that the DS1 port used for the Primary and Secondary D-channels has not been busied out at the far end.
	PASS	The Primary Signaling Channel is up and, if administered the Secondary Channel is up.
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.