Table of Contents
Advertisement
To check why server does not boot and makes beeps
1. Make a note of the number of beeps and any error messages or POST codes.
2. Refer to
3. Replace any component that is indicated as faulty.
If beeps are long
If the beeps are a series of high-pitched, long beeps, they are from the RAID system.
Typically, you will see messages displayed on the monitor indicating that the system is in a
critical state.
1. Ensure that internal hard drive cables are properly connected.
2. If the problem continues, RAID BIOS may be corrupted.
3. If the problem continues, the drive is faulty. Replace the hard drive as described in
When the 703t server boots to the operating system and
makes audible beeps
If the 703t server boots to the operating system but still makes audible beeps, one of the hard
drives is in critical condition.
To check if server has a hard drive in critical condition
Rebuild the hard drive as soon as the operating system has finished loading. Refer to
RAID splitting
When the 703t server boots to the operating system but
does not boot to CallPilot
If the 703t server does not boot to CallPilot, it may be due to the failure of a multimedia board.
Avaya CallPilot® 703t Server Maintenance and Diagnostics
Table 4: Bootblock error beep codes
error 3-beep codes
on page 29, and use the collected information to identify the
cause of the failure.
Replacing a faulty hard drive
on page 132.
on page 29 and
on page 106.
If beeps are long
Table 5: Bootblock
December 2010
33
Advertisement
Table of Contents
