Table of Contents
Advertisement
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 (NN44200-700) for other suggestions. If you
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
5. Refer to the Troubleshooting Guide (NN44200-700) for other suggestions. If you
Avaya CallPilot® 1002rp Server Maintenance and Diagnostics
still cannot determine the cause of the startup failure, call your Avaya technical
support representative.
still cannot determine the cause of the startup failure, call your Avaya technical
support representative.
What to do when the server fails to boot into service
Viewing event logs
on page 25.
December 2010
23
Advertisement
Table of Contents
