Avaya Definity SI, Maintenance Manual, Page: 43 / 2968

Alarm and Error Reporting
Issue 4 May 2002 1-7 555-233-123
Alarm and Error Reporting
During normal operations, software or firmware may detect error conditions
relevant to specific MOs. The system attempts to fix or circumvent these problems
automatically. However, if a hardware component incurs too many errors, an
alarm is raised. Errors are detected in two ways:
■
For “in-line” errors, firmware on the component detects the
occurrence of an error during ongoing operations.
■
For other types of errors, a “periodic test” or a “scheduled test”
started by the software detects the error. The technician can run
these tests on demand by using the maintenance commands
described in
Chapter 8, ‘‘Maintenance Commands and
Trouble-Clearing Aids’’ , and Chapter 10, ‘‘Maintenance Object
Repair Procedures’’ .
Software puts the error in the error log, and increments the error counter for that
error. When an error counter is “active,” (greater than zero), there is a
maintenance record for the MO.
Alarms are classified as MAJOR, MINOR, or WARNING, depending on the effect
on system operation. They are also classified as ON-BOARD or OFF-BOARD.
— MAJOR alarms identify failures that cause a critical degradation of service.
These alarms require immediate attention.
— MINOR alarms identify failures that cause some service degradation but
that do not render a crucial portion of the system inoperable. MINOR
alarms require attention. However, typically a MINOR alarm affects only a
few trunks or stations or a single feature.
— WARNING alarms identify failures that cause no significant degradation of
service or equipment failures external to the switch. These failures are not
reported to INADS or to the attendant console.
— ON-BOARD problems originate in the circuitry on the alarmed circuit pack.
— OFF-BOARD problems originate in a process or component that is external
to the circuit pack.
Alarms are discussed further in Chapter 10, ‘‘Maintenance Object Repair
Procedures’’ .