
HEX display codes
During startup and normal 202i server operation, the HEX display on the server faceplate
displays one of the codes in the following table.
HEX display output
Description
Startup codes
T:XX
The 8051 controller is starting and running
diagnostics. These diagnostics occur during a cold
restart (when the server is powered up, or if you press
Reset on the 202i server faceplate).
For more details, see
page 25.
F:XX
At least one diagnostic failed. The displayed error
code represents the first failed diagnostic.
For more details, see
page 25.
P:XX
An Extended POST error occurred, where XX
represents a two-character code. If the error is a
critical error, the start cycle may halt. If the error is a
non critical error, the error code is logged in the
operating system event log after the operating system
starts and the CallPilot 8051 device driver starts.
Important:
POST Terminal errors that result in a system halt do
not appear on the HEX display. If you cannot use
the HEX display to determine the cause of a system
halt, contact your Avaya technical support
representative.
HOST
This code appears during the startup sequence and
means that BIOS diagnostics started.
NT
The operating system start sequence has started.
OK
The operating system start sequence was successful
and the 8051 controller is operating normally.
CallPilot and 202i server operation codes
BOOT
CallPilot is starting and is not yet fully operational.
PASS
CallPilot is fully operational and ready to accept calls.
WARN
CallPilot is ready to accept calls. However, some
services failed the start sequence. Review the event
log for further information.
HEX display codes
Avaya CallPilot 202i Server Maintenance and Diagnostics
December 2010 23