Performing A Hardware Shutdown - Nortel CallPilot User Manual

28 Chapter 3 Troubleshooting your CallPilot system
To determine why the server failed to boot to Windows
Step
1
2
3
4
To determine why CallPilot failed to come into service
Step
If CallPilot failed to come into service, follow these steps:
1
2
3
4

Performing a hardware shutdown

If you cannot shut the server down using Windows, press the power switch
on the front panel and hold it in for more than 1 second. The server saves
all system data and then powers off.
Copyright © 2007, Nortel Networks
.
Action
Try restarting the sever by pressing the power switch. Ensure
the power cable for the system monitor and the VGA cable are
connected.
Listen for server-generated beep codes. Make note of any beep
codes and contact Nortel product support.
During the boot sequence, take note of the bootup POST messages
Refer to the Troubleshooting Guide (NN44200-700) for other
suggestions. If you still cannot determine the cause of the startup
failure, call your Nortel technical support representative.
Action
Assuming the server loads Windows and you are able to log on, note
any failed MPB self-diagnostic failures when you log on to Windows.
Check the Windows Event Viewer for both Windows system errors
and CallPilot application errors. For instructions, see
logs" (page 29).
Perform a cold reboot by powering off the server through the
Windows Shut Down procedure.
Refer to the Troubleshooting Guide (NN44200-700) for other
suggestions. If you still cannot determine the cause of the startup
failure, call your Nortel technical support representative.
Nortel CallPilot
600r Server Maintenance and Diagnostics
NN44200-703 01.04 Standard
5.0 25 April 2007
—End—
—End—
"Viewing event