Alarm Notification; Component Dependencies; Detecting Hardware Problems - Avaya CallPilot 1005r Maintenance And Diagnostics

Hide thumbs Also See for CallPilot 1005r:

Table of Contents

Monitoring multimedia hardware

All events are reported to the fault management server. The fault management server lets the

CallPilot server listen and respond to its clients. The interaction is called event processing and

the server detects hardware faults in the multimedia hardware.

Alarm notification

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.

When an alarm appears in the Alarm Monitor, you must investigate the problem, isolate it, and

then fix the cause of the problem. When you fix the problem, the alarm is cleared from the

Alarm Monitor.

The status of some components is dependent on the operational status of other components. If

a component fails or is stopped, the dependent components go out of service.

Note:

The components in your system are based on your CallPilot server type and switch type.

Disregard dependencies for components not in your system.

Component

Media bus

MPB board

Time switch

MPB96

DS30X or DS30

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.

Avaya CallPilot® 1005r Server Maintenance and Diagnostics

Dependent components

All MPBs, all multimedia channels, and all call channels.

All multimedia and call channels associated with the MPB board.

All multimedia and call channels associated with the same MPB as

the time switch.

All multimedia channels on the MPB96 board.

All DS30X or DS30 channels associated with the DS30X or DS30

link. (depending on MPB96 board version)

December 2010

Table of Contents