Event Processing; Alarm Notification; Component Dependencies - Avaya CallPilot 1002rp Maintenance And Diagnostics

Hide thumbs Also See for CallPilot 1002rp:

Table of Contents

Using Avaya CallPilot® Manager to monitor hardware

Event processing

An event is any change in system configuration or operational state. An event is also any action

taken by the system that requires user notification. Events can be as insignificant as a user

logon attempt or as serious as a faulty MPB96 card switching to disabled status.

All events are reported to the fault management server, a subsystem within the CallPilot server.

The fault management server enables the CallPilot server to listen and respond to its clients.

The interaction is called event processing and is the means by which the server detects

hardware faults.

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 are dependent on the operational status of other components.

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

Note:

Based on the CallPilot server type, and the type of switch connected to CallPilot, some of

these components may not appear on your system.

Component

Media Bus

MPB board

Time Switch

MPB96

Avaya CallPilot® 1002rp 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 card.

December 2010

Table of Contents