Table of Contents
Advertisement
The use of parts that are not supplied by Avaya can cause serious system problems or void
your Avaya warranty.
The following table shows a list of the current part numbers of field replacement units for the
600r at the time of publishing. Refer to the latest Avaya product catalog for any interim updates
to the part numbers.
Table 8: Field replacement units (FRUs)
Hard disk drive mechanical tray
External SCSI terminator
Power supply
Fanset
Hard drive
DDR memory (x2)
DVDROM/CDRW combo
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. Try restarting the sever by pressing the power switch. Ensure the power cable for
2. Listen for server-generated beep codes. Make note of any beep codes and contact
3. During the boot sequence, take note of the bootup POST messages
4. Refer to the Troubleshooting Guide (NN44200-700) for other suggestions. If you
To determine why CallPilot failed to come into service
If CallPilot failed to come into service, follow these steps:
1. Assuming the server loads Windows and you are able to log on, note any failed
2. Check the Windows Event Viewer for both Windows system errors and CallPilot
Avaya CallPilot® 600r Server Maintenance and Diagnostics
Description of part
the system monitor and the VGA cable are connected.
Avaya product support.
still cannot determine the cause of the startup failure, call your Avaya technical
support representative.
MPB self-diagnostic failures when you log on to Windows.
application errors. For instructions, see
What to do when the server fails to boot into service
Part number
NTRH9205E5
NTRH9244E6
NTRH9245E5
NTRH9246E5
NTRH9247E6
NTRH9224E5
NTRH9232E5
Viewing event logs
on page 30.
December 2010
27
Advertisement
Table of Contents
