Secondary Signaling Link Hardware Check (#639)

Secondary Signaling Link Hardware Check (#639)

The ISDN-PRI Signaling Group D-Channel port depends on the health of the MM710 on which it resides. This test will fail if there are problems with either the ISDN-PRI Secondary D-channel port or the MM-DS1 Media Module. This test will abort if a Secondary D-channel is not administered for the signaling group. If there are problems with the ISDN-PRI Secondary Signaling Channel port (ISDN-LNK), also investigate the MM710.

Table 40. TEST #639 Secondary Signaling Link Hardware Check �
Error Code	Test Result	Description/ Recommendation
	ABORT	Internal system error Retry the command at 1-minute intervals a maximum of 5 times.
1132	ABORT	The Secondary D-Channel is not administered for this Signaling Group. This is a NORMAL ABORT. Only a Primary D-Channel must be administered for a Signaling Group.
8	FAIL	There is a problem with the MM710 or the ISDN-PRI Secondary 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).
	PASS	The basic physical connectivity of the Signaling Group's Secondary D-channel is intact and functional. Try this test repeatedly to ensure the link is up and to uncover any transitory problems.
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.