To Determine Why The Server Failed To Boot To Windows; To Determine Why The Server Failed To Boot Into Callpilot; What To Do When The Server Fails To Boot Into Service - Nortel 1002rp Maintenance And Diagnostics

Troubleshooting your CallPilot system
What to do when the server fails to boot
into service
This section suggests tasks you can perform to determine why the server
fails the bootup cycle.
To determine why the server failed to boot to
Windows
1 Make a note of any diagnostic codes.
2 Try restarting the server by pressing the power button on the server.
3 During the boot sequence, view the diagnostic codes on the monitor
for failures.
4 Refer to the Troubleshooting Guide (555-7101-501) for other
suggestions. If you still cannot determine the cause of the startup
failure, call your Nortel technical support representative.
To determine why the server failed to boot into
CallPilot
If the system-ready indicator indicates that the system is not booting into
CallPilot, follow these steps:
1 Make a note of any diagnostic codes.
2 Try restarting the server by pressing the power button on the server.
3 During the boot sequence, view the diagnostic codes on the monitor
for failures.
4 View the event logs. For instructions, see "Viewing event logs" on
page 33.
28
Standard 1.11
CallPilot