Avaya CallPilot 201i Maintenance And Diagnostics page 30

Troubleshooting your Avaya CallPilot® system
The following table shows the noncritical operating system and switch diagnostic codes with
their corresponding failure codes.
Note:
While the test is in progress, the following codes may appear for a short period. If these
messages display temporarily (that is, no longer than one second), a problem does not exist.
Status code
HOST
NT
CDLN
C:01
C:02
OK
30 Avaya CallPilot® 201i Server Maintenance and Diagnostics
Operation description
Continuation of BIOS diagnostics
The monitor displays the BIOS start screen.
If a noncritical error occurs, the server
continues the start sequence.
The operating system start sequence started
Note:
If the CallPilot server software is not
installed, the HEX display remains at NT.
(This can occur if you are performing a
system rebuild.) During CallPilot software
installation, the 8051 device driver is
copied to the operating system, at which
point the HEX display shows CDLN.
8051 device driver on the operating system
has started; beginning of Cardlan interface
communication (DS30x interface
initialization)
The system controller communicates with
the switch, indicating that two cards are
installed, and waits for switch
acknowledgement.
Initialization of the first DS30x interface
Initialization of the second DS30x interface
Switch acknowledgement complete
The operating system startup is complete,
and CallPilot Fault Management takes over.
Failure code
P:XX
P:XX
Note:
For a description, see
P:XX failure codes on
page 31.
CDLN
Neither DS30x interface
was initialized (both
failed).
C:01
Initialization of the first
DS30x interface failed.
The second DS30x
interface is OK.
C:02
Initialization of the second
DS30x interface failed.
The first DS30x interface
is OK.
CRI, FAIL, MAJ, MIN, or
WARN
December 2010