The system displays a blue screen with the following message: Hardware Malfunction, please contact your H/W vendor. The system does not take calls.
All DSP diagnostics fail at system startup.
The system starts up, but attempts to boot to the operating system from the network.
The system ELAN or CLAN is not working, even though they are detected and displayed in the operating system control panel.
The system displays an error message after CallPilot languages are installed.
The HAL does not detect the MPB96 board. All the DSPs report failures in the diagnostic window.
The system does not detect the MPB96 board after CallPilot is migrated from an earlier platform.
1005r server 49
Ensure the MPB96 board is release 5 or later.
Shut down the server and open the lid. Turn on the server and check if the PCI LED on the MPB96 board is still on after startup. If the LED is still on, then shut down the server, reseat the board, and then turn on the server again.
•If the LED is still on, the board is defective and must be replaced.
•If the LED goes on and then off, but the DSP and CTbus FPGA LEDs are still on after the system boots completely to the operating system, then check the HAL and ensure that all its components are working properly. If the HAL components function properly, then at least one of the ctbus.mcs or dsp.mcs files is corrupted. Replace these files and reboot the system. If the PCI LED still stays on, then the MPB96 board is defective and must be replaced.
The RAID card was not detected due to improper seating during PCI assembly. Remove the system from the rack and place
it on a table.
Enable the NIC controllers in the BIOS.
There is an older version of the RAID controller firmware. Upgrade the RAID firmware to a currently supported version. For information about valid RAID firmware, see the 1005r Server Maintenance and Diagnostics guide.
By looking at the LEDs, ensure the MPB96 is not faulty. See MPB96 board LEDs on page.
•Check if the system is detected correctly in the HAL; that is, if the platform information file matches your system information.
•If the platform information and the system information do not match, then load the correct platform information file into the registry.
Nortel CallPilot
Troubleshooting Reference Guide
5.026 June 2007
