Avaya callpilot 1002rp, Maintenance And Diagnostics

Page: 49 / 150

Component Dependent components
DS30X All DS30X channels associated with the DS30X link.
T1 board Telephony Interface. All DS0 (zero) channels associated with the
telephony interface.
Detecting hardware problems
Typically, you first become aware of a hardware problem when an alarm is raised. All hardware
faults produce an alarm (or series of alarms, depending on the problem) in the Alarm Monitor.
Other indications of a hardware problem include the following:
• user complaints
• call processing difficulties, such as busy signals, static, dropped calls, connection
problems, and cross talk (hearing other conversations)
• system administrator logon difficulties
• alert icons on the Maintenance screen
Alarm Monitor
Use the Alarm Monitor to investigate one or more raised alarms.
About alarms
Alarms are warnings generated by events. Alarms communicate the same information as
events. However, alarms are reported in the Alarm Monitor instead of the Event Browser, and
are managed differently than events:
• Alarms appear in the Alarm Monitor only for Minor, Major, and Critical events (not
Information events). All events can be reported in the Event Browser (depending on
filtering criteria defined in the Event Browser).
• The first time an event occurs, it generates an alarm that appears in the Alarm Monitor.
If the same event continues to occur, a new alarm is not generated. Instead, the time and
date assigned to the original generated alarm is updated.
• Alarms can be cleared from the Alarm Monitor, but the event that generated the alarm is
not cleared from the event log or the Event Browser.
Detecting hardware problems
Avaya CallPilot® 1002rp Server Maintenance and Diagnostics December 2010 49