Critical startup diagnostic codes
All critical startup diagnostics must pass before the 201i can proceed with the start sequence. If
a critical diagnostic fails, the start sequence indefinitely halts, an error code displays, and a
continuous beep is heard.
The following table shows the critical startup diagnostic codes with their corresponding failure
codes. Failure of these diagnostics means that there has been a server failure. The start cycle
is halted.
Note:
When a test is successfully completed, the next test code appears.
Test code
T:01
T:02
T:03
T:04
T:05
T:06
T:07
T:08
HOST
Non-critical operating system and switch diagnostic codes
If a noncritical operating and switch diagnostic test fails, the HEX display stops at the failed
test. The remaining diagnostics are not performed. The start sequence continues, but server
functionality can be compromised.
Avaya CallPilot® 201i Server Maintenance and Diagnostics
Test description
Internal RAM self-test
ALU self-test
Address mode self-test
Boot ROM self-test
Timer self-test
Watchdog self-test
EEPROM self-test
End of system controller self-tests
The power status LED blinks three times.
Start of BIOS diagnostics
The monitor displays the BIOS start screen.
If a critical error occurs, the start cycle is
halted. Examples of critical errors are
memory failure or another type of error
resulting in no display on the monitor.
Critical startup diagnostic codes
Failure code
F:01
F:02
F:03
F:04
F:05
F:06
F:07
not applicable
HOST continues to
scroll across the HEX
display
December 2010
29