Overview; Component Dependencies; Detecting Hardware Problems - Avaya CallPilot 202i Manual

Overview

This section describes how to use the CallPilot Manager tools to detect, isolate, and fix potential
or real hardware problems.

Component dependencies

The status of some components depend on the operational status of other components. If a
component fails or stops, 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
Motherboard (IPE
server)
Time Switch
DS30X

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 page
Avaya CallPilot 202i Server Maintenance and Diagnostics
Dependent components
All DSPs, and all multimedia and call channels associated with the IPE
server.
All multimedia and call channels associated with the same MPB as the
time switch.
All DS30X channels associated with the DS30X link.
Overview
December 2010 47