Table of Contents
Advertisement
Stage
12
Troubleshooting startup problems
Introduction
This section suggests tasks you can perform to determine why the 201i server fails the startup
cycle.
To determine why the 201i server failed the 8051 startup
1. Make a note of any diagnostic codes.
2. Try restarting the server by pressing Reset on the 201i server's faceplate.
3. During the restart sequence, view the diagnostic codes on the HEX display for
4. Refer to the CallPilot Troubleshooting Guide for other suggestions.
5. If you still cannot find the cause of the failure, call your Avaya technical support
Avaya CallPilot® 201i Server Maintenance and Diagnostics
Description
The 201i Avaya CallPilot software loads.
OK means that CallPilot has loaded. CallPilot
Fault Management takes over.
If FAIL, WARN, CRI, MAJ, or MIN appears instead
of OK, a fault has occurred. Use the system and
CallPilot Manager event logs and Alarm Monitor
to determine what happened.
Approximate duration: 5 minutes
failures.
For a description, see
Note:
Allow 5 minutes for the start cycle to complete.
representative.
Startup sequence description
Troubleshooting startup problems
HEX
Status LED
display
One of the
OFF
following,
as
applicable:
• BOOT
• PASS
• FAIL
• WARN
• CRI
• MAJ
• MIN
on page 31.
December 2010
33
Advertisement
Table of Contents
Troubleshooting
