Nortel CallPilot - What to Do When the Server Fails to Boot into Service

What to do when the server fails to boot into service 27
RAID controller diagnostics
Most diagnostic information about RAID is available through beep warnings
and status LEDs when the server is rebooting.
For more information refer to:
•
"Hard drive LED states" (page 19)
•
"RAID controller LED states" (page 23)
•
"When the 703t server does not boot and makes audible beeps" (page
29)
•
"When the 703t server boots to the operating system and makes audible
beeps" (page 30)
What to do when the server fails to boot into service
The following sections suggest tasks you can perform to determine why the
703t server fails the bootup cycle.
To investigate server boot problems
Step Action
1
Ensure that you accurately record any diagnostic codes and error
messages that occur.
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.
Note: Allow 5 minutes for the boot cycle to complete.
4
If errors indicate a hardware problem with a failure to boot to the
operating system or if the server boots to the operating system, but
fails to boot into CallPilot, refer to the CallPilot Troubleshooting Guide
5
If you still cannot find the cause of the boot failure after performing
the tasks described in the following sections, call your Nortel
technical support representative.
—End—
Nortel CallPilot
703t Server Maintenance and Diagnostics
NN44200-702 01.03 Standard
5.0 3 April 2007
Copyright © 2007, Nortel Networks Nortel Networks Confidential
.