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