Server Alarms - Avaya Support

Communication Manager Maintenance Object Repair Procedures
Table 388: Port Diagnostic Test (#35) 2 of 6
Error
Code
Test
Result
Description / Recommendation
1000 ABORT System resources required to run this test are not available.
ALARM-PT: The port may be reporting an external device alarm.
1. Enter test external-device-alarm port location to
determine whether the port is reporting an EXT-DEV failure.
2. If the port has no EXT-DEV failures, retry the command at
1-minute intervals up to 5 times.
ANL-16-L, ANL-LINE, AN-LN-PT, MET-LINE, RANL-STA: The port
may be busy with a valid call.
1. Enter display port location to determine the station
extension or attendant number of the port.
2. Enter status station extension or status attendant
extension to determine the service state of the port. If the
service state indicates that the port is in use, wait until the port is
idle before retesting. Attendants are always in use (off-hook) if the
handset is plugged in and the port is not busied out.
3. If the port status is idle, retry the command at 1-minute intervals a
maximum of 5 times.
DID-TRK: The port may be busy with a valid call.
1. Enter display port location to determine the trunk group/
member number of the port.
2. Enter status trunk to determine the service state of the port. If
the port is in use, wait until it is idle before testing.
3. If the port status is active but the port is idle (no calls), check the
error log for Error Type 513 for this maintenance object. The port
may be locked up.
4. If the port status is idle, busyout and release the trunk, and retry
the command at 1-minute intervals up to 5 times.
5. If the test continues to abort, check for wiring errors toward the CO
which may cause the trunk to lock up.
6. If the wiring is good and the test continues to abort, replace the
circuit pack or media module.
1484 Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers
2 of 6