Port Audit and Update Test (#36)

This test sends port level translation data from switch processor to the DS1 Interface Media Module to assure that the trunk's translation is correct. Translation updates include the following data: trunk type (in/out), dial type, timing parameters, and signaling bits enabled. The port audit operation verifies the consistency of the current state of trunk.

Table 60. TEST #36 Port Audit and Update Test �
Error Code	Test Result	Description/ Recommendation
	ABORT	Internal system error Retry the command at 1-minute intervals for a maximum of 5 times.
1000	ABORT	System resources required to run this test were not available. 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 for a maximum of 5 times.
1006	ABORT	The DS1 CO 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. If it is OK to put the trunk back in service, issue the release trunk command to put the trunk back in service, and then retry the test.
2000	ABORT	Response to the test was not received within the allowable time period.
2100	ABORT	Could not allocate the necessary system resources to run this test. Retry the command at 1-minute intervals for a maximum of 5 times.
	FAIL	Test failed due to internal system error. Retry the command at 1-minute intervals for 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. This result could be due to incorrect translations, no board inserted, an incorrect board inserted, an insane board inserted, or the board is hyperactive. Check to ensure that the board translations are correct. Use the list config command, and resolve any problems that are found. 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 not, to check that there is a valid board inserted. Hyperactivity causes some special problems with the sequence suggested above. If the ports are translated after issuing the list config command but the 'Vintage' field reports that there is no board (when there really is a board), then the busyout board and the release busy board commands do not work (even though the reset board command does work). The software puts the hyperactive board back in service after the hyperactivity clears.