Avaya CallPilot 201i Maintenance And Diagnostics page 27

HEX display output
HOST
NT
OK
CallPilot and 201i server operation codes
BOOT
PASS
WARN
FAIL
MIN
MAJ
CRI
???
Avaya CallPilot® 201i Server Maintenance and Diagnostics
Description
Startup codes
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
startup completes 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.
This code appears during the startup sequence and
means that BIOS diagnostics have started.
HOST also appears on the HEX display when the
server has been started to ROM-DOS.
The operating system start sequence has started.
The operating system start sequence was successful.
CallPilot is starting and is not yet fully operational.
CallPilot is fully operational and ready to accept calls.
CallPilot is ready to accept calls. However, some
services failed the start sequence. Review the event
log for further information.
CallPilot failed the start sequence and cannot accept
calls. Review the event log for further information.
A minor alarm has occurred. Review the event log for
further information.
A major alarm has occurred. Review the event log for
further information.
A critical alarm has occurred. Review the event log for
further information.
An alarm of unknown severity occurred. This error
should not occur on a properly installed system. The
severity of this event is treated as higher-than-critical.
Note:
If you observe "???" or anything else on the display,
contact your Avaya technical support
representative.
HEX display codes
December 2010 27