Maintenance strategy
Alarm and error reporting
28
Maintenance Procedures
December 2003
An ON-BOARD alarm causes every alarm against that MO to report as ON-BOARD.
NOTE:
To determine the actual level and origin of each alarm when there are more than one
against the same MO, see the Hardware Error Log Entries table for that MO.
The alarm log is restricted in size. If the log is full, a new entry overwrites the oldest resolved alarm. If
there are no resolved alarms, the oldest error that is not alarmed is overwritten. If the full log consists of
only active alarms, the new alarm is dropped and not recorded.
Alarm reporting
Every major or minor alarm is reported to the Avaya alarm receiver system to generate a trouble report in
the Avaya Services Ticketing System. Some warning alarms can be upgraded in conjunction with the
Enhanced Remote Support (ERS) offer. These alarms are external to the product and the customer can
choose these options for an additional charge (see
Figure 2, Alarm reporting flowchart,
Table 4: Multiple alarms against an MO
If...
And...
Then...
An active error
causes a minor alarm
An active error
causes a major alarm
The alarm log shows two major
alarms.
The minor alarm is
resolved first
The error is marked as alarmed until
the major alarm is resolved, and the
alarm log shows two major alarms.
The major alarm is
resolved first
The error is marked as alarmed until
the minor alarm is resolved, and the
alarm log shows two minor alarms.
Summary of Contents for CMC1
Page 1: ...Maintenance Procedures 555 245 103 Issue 1 1 December 2003 ...
Page 14: ...Contents 14 Maintenance Procedures December 2003 ...
Page 416: ...Additional maintenance procedures IP Telephones 416 Maintenance Procedures December 2003 ...
Page 426: ...Index X 426 Maintenance Procedures December 2003 ...