Server Alarms - Avaya Support

Communication Manager Maintenance Object Repair Procedures
Table 171: CO-TRK Error Log Entries 2 of 2
Error
Type
Aux
Data
3329 (e) 57408
3329 (e) 57484 Dial Tone Test (#0) MAJ
MIN
WRN
3585 (e) 57424
Associated Test Alarm
Level
3840 (g) 8000 ATM Transmission Test
(#844-848)
3841 (g) ATM Transmission Test
(#844-848)
On/Off
Board
Recommended Action
OFF test port location long
OFF test analog-testcall full
MIN OFF test analog-testcall full
1. Major alarms may be downgraded to Warning alarms based on the value used in set options.
Notes:
a. Error Type 0: Run the short test sequence first. If every test passes, run the long test
sequence. Refer to each appropriate test’s description, and follow its recommended
procedures.
b. These are inline errors that have no specific test associated with them. Numerous Error
Types have these errors. Refer to Table 172: CO Trunk Errors with No Tests for an
explanation and appropriate action.
c. Error Type 15: software audit error that does not indicate any hardware malfunction. Run
short test sequence, and investigate associated errors.
d. Error Type 130: the circuit pack has been removed or has been insane for at least 11
minutes. To clear the error, reinsert or replace the circuit pack.
e. Numerous Error Types have these errors.
Aux data 57345: Single polarity ringing current
Aux data 57376: No loop current on incoming call
Aux data 57408: No tip ground detected on outgoing call
Aux data 57424: No loop current on outgoing call
Aux data 57484: No dial tone on outgoing call
These errors will cause Dial Tone Test #0 to run and are only considered a problem if the
Dial Tone test fails (in which case Error Type 1537 will also show up). In this case, the trunk
may be put in “Ready-for-Service” state (shown as “disconnected” by status command), that
allows only incoming calls. Run Dial Tone Test #0, and follow its outlined procedures.
If error count associated with this Error Type is very high (i.e., 255) and if Alarm Status on
the Hardware Error Report is “n” (not alarmed), then the existence of this Error Type
indicates that, despite the fact that many inline error messages have been received, every
660 Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers
2 of 2