201i/202i HEX display Codes
During startup, and normal operation, the server faceplate display shows one of the following codes:
| Display | Description |
|---|---|
| T:XX | The 8051 controller is starting and running diagnostics. These diagnostics are performed during a cold restart (when the server powers up, or when you press Reset on the 201i/202i server's faceplate. |
| F:XX | At least one diagnostic failed. The displayed error code represents the first failed diagnostic. |
| P:XX | A BIOS diagnostic error, where XX represents a two-character code. If the error is critical, startup may halt. If the error is noncritical, it is entered in the system event log after the OS startup sequence completes and the 8051 device driver starts. |
| HOST | Appears during the startup sequence and means that BIOS diagnostics have started. HOST also appears when the server is booted to ROM-DOS. |
| NT | The operating system (OS) start sequence has started. |
| OK | The operating system start sequence was successful. |
| 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 to start. Check the event log for further information. |
| FAIL | CallPilot failed the start sequence and cannot accept calls. Review the event log for further information. |
| MIN | A Minor alarm has occurred. Review the Alarm Monitor event log for further information. |
| MAJ | A Major alarm has occurred. Review the Alarm Monitor event log for further information. |
| CRI | A Critical alarm has occurred. Review the Alarm Monitor 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. |
| DOWN | The operating system shut down. When the power status LED is on, it is safe to remove the server. |
Critical OS startup diagnostic codes:
| Test code | Test description | Failure code |
|---|---|---|
| T:01 | Internal RAM self-test | F:01 |
| T:02 | ALU self-test | F:02 |
| T:03 | Address mode self-test | F:03 |
| T:04 | Boot ROM self-test | F:04 |
| T:05 | Timer self-test | F:05 |
| T:06 | Watchdog self-test | F:06 |
| T:07 | EEPROM self-test | F:07 |
| T:08 | End of tests (status LED blinks 3 times) | n/a |
| HOST | Start of BIOS diagnostics | n/a |
During startup, the monitor displays the BIOS start screen. If a critical error occurs, the start cycle halts.
Examples of critical errors are memory failure or another type of error resulting in no display on the monitor.
Non-critical OS and PBX diagnostic codes:
| Test code | Test description | Failure code |
|---|---|---|
| HOST | Continuation of BIOS diagnostics | P:XX |
| NT | OS start sequence has started | P:XX |
| CDLN | Cardlan (DS30x) initialization | CDLN |
| C:01 | Initialization of first DS30x bus | C:01 |
| OK | OS system startup is complete | CRI FAIL MAJ MIN WARN |
If FAIL, WARN, CRI, MAJ, or MIN appears in the display instead of OK, a fault occurred!
Use the system and CallPilot Manager event logs and Alarm Monitor to determine what happened.