Troubleshooting your CallPilot system
Standard 1.0
24
CallPilot
What to do when the server fails to boot
into service
Introduction
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 NT
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
CallPilot Troubleshooting Reference
for other suggestions.
Nortel Networks continually updates this document, and it is made
available on the Nortel Networks Partner Information Center web site at
http://www.my.nortelnetworks.com.
Note:
If you are not a distributor, contact your Nortel Networks technical
support representative for assistance.
5
If you still cannot find the boot failure cause, call your Nortel Networks
technical support representative.
Summary of Contents for CallPilot 702t
Page 2: ...P0949453 ...
Page 6: ...vi CallPilot Publication history Standard 1 0 ...
Page 26: ...Troubleshooting your CallPilot system Standard 1 0 26 CallPilot ...
Page 50: ...Using Windows NT online diagnostic tools Standard 1 0 50 CallPilot ...
Page 62: ...Using serial port diagnostic tools Standard 1 0 62 CallPilot ...
Page 76: ...Using CallPilot Manager to monitor hardware Standard 1 0 76 CallPilot ...
Page 102: ...Using CallPilot Manager to monitor hardware Standard 1 0 102 CallPilot ...
Page 194: ...Performing RAID maintenance Standard 1 0 194 CallPilot ...
Page 240: ...Performing RAID maintenance Standard 1 0 240 CallPilot ...
Page 254: ...Replacing or adding voice processing boards Standard 1 0 254 CallPilot ...
Page 264: ...Replacing DIMMs and the CPU Standard 1 0 264 CallPilot ...
Page 284: ...SSU and BIOS Standard 1 0 284 CallPilot ...
Page 304: ...Index Standard 1 0 304 CallPilot ...
Page 305: ......