Port Audit and Update Test (#36)

This test sends port level translation data from the switch processor to the DS1 Interface Media Module to assure that the trunk's translation is correct. The port audit operation verifies the consistency of the current state of the trunk as kept in the DS1 Interface Media Module and in the switch software.

Table 11. TEST #36 Port Audit and Update Test �
Error Code	Test Result	Description/ Recommendation
	ABORT	Internal system error Retry the command at 1-minute intervals a maximum of 5 times.
1000	ABORT	The port may be busy with a valid call. Issue display port GGGVSpp to determine the trunk group/member number of the port. Use the status trunk command to determine the service state of the port. If the port is in use, wait until the port is idle before testing. If the port status is active but the port is not in use (no calls), check the error log for error type 1025. The port may be locked up. If the port status is idle, retry the command at 1-minute intervals a maximum of 5 times.
1006	ABORT	The test was aborted because the trunk is out of service. Use status trunk to verify that the trunk is out of service. If the trunk is out of service, determine why. To put the trunk back in service, issue the release trunk command. Retry the test.
2000	ABORT	Response to the test was not received in the allowable time period.
2100	ABORT	Could not allocate resources to run this test. Retry the command at 1-minute intervals a maximum of 5 times.
	FAIL	Test failed due to internal system error. Retry the command at 1-minute intervals a maximum of 5 times.
	PASS	Trunk translation has been updated successfully. The current trunk states kept in the DS1 Interface Media Module and switch software are consistent. If the trunk is busied out, the test will not run but will return PASS. To verify that the trunk is in-service: Enter status trunk to verify that the trunk is in-service. If the trunk is in-service, no further action is necessary. If the trunk is out-of-service. Enter release trunk to put the trunk back into in-service. Retry the test command.
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. Check to ensure that the board translations are correct. Use the list config command, and resolve any problems that are found. If the board was found to be correctly inserted in step 1, 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. If this is not the case, check to see that there is a valid board inserted.