ProLiant ML530 Servers Maintenance and Service Guide
Table Of Contents
- Compaq ProLiant ML530 Servers Maintenance and Service Guide
- Notice Page
- Table of Contents
- About This Guide
- Chapter 1: Illustrated Parts List
- Chapter 2: Removal and Replacement Procedures
- Electrostatic Discharge Information
- Symbols on Equipment
- Preparation Procedures
- Tower Model Front Bezel Door
- Rack Mount Bezel
- Access Panel
- Fans
- Removable Media and Mass Storage Devices
- Cable Routing Diagrams
- System Board Tray
- System Board Components
- Hot Plug Power Supplies
- Power Backplane Board
- Power On/Standby Switch
- Chapter 3: Diagnostics and Troubleshooting
- Diagnostic Tools Utility Overview
- Default Configuration
- Utilities Access
- Power On Self Test
- Diagnostics Software
- Steps for Diagnostics
- 100–199, Primary Processor Test Error Codes
- 200–299, Memory Test Error Codes
- 300–399, Keyboard Test Error Codes
- 400–499, Parallel Printer Test Error Codes
- 500–599, Video Display Unit Test Error Codes
- 600–699, Diskette Drive Test Error Codes
- 800–899, Video Board Test Error Codes
- 1100–1199, Serial Test Error Codes
- 1200–1299, Modem Communications Test Error Codes
- 1700–1799, Hard Drive Test Error Codes
- 1900–1999, Tape Drive Test Error Codes
- 2400–2499, Advanced VGA Board Test Error Codes
- 6000–6099, Compaq NIC Boards Test Error Codes
- 6500–6599, SCSI Hard Drive Test Error Codes
- 6700–6799, SCSI Tape Drive Test Error Codes
- 8600–8699, Pointing Device Interface Test Error Codes
- Array Diagnostic Utility
- Integrated Management Log
- Rapid Error Recovery
- Remote Service Features
- ROMPaq Error Recovery Options
- Compaq Insight Manager
- Chapter 4: Connectors, Switches, Jumpers, and LED Indicators
- Chapter 5: Physical and Operating Specifications
- Index
Diagnostics and Troubleshooting 3-59
Compaq Integrated Remote Console
The standard Compaq Integrated Remote Console performs a wide range of configuration
activities. Console features include:
■ Is accessible using ANSI terminal
■ Operates independently of the operating system
■ Provides for remote server reboot
■ Provides access to system configuration
■ Uses out-of-band communication with dedicated management modem installed in the
server
For more information, see the Integrated Remote Console User Guide that shipped with the
server.
IMPORTANT: Before configuring ASR-2, verify that the System Configuration Utility and Diagnostics
software are installed on the system partition. ASR-2 requires this software to start Compaq Utilities after
a system restart. Compaq recommends software installation even if you configure ASR-2 to start the
operating system.
Compaq Health Driver
The Compaq Health Driver continually resets the ASR-2 timer according to the frequency you
specified in the System Configuration Utility (for example, 10 minutes). If the ASR-2 timer
counts down to zero before being reset, due to an operating system crash or a server lockup,
ASR-2 restarts the server into either Compaq Utilities or the operating system (as indicated by
the System Configuration parameters). The default value is 10 minutes. The allowable settings
are 5, 10, 20, and 30 minutes.
For remote and off-site (unattended) servers, setting the software error recovery timeout for
5 minutes reduces server downtime and allows the server to recover quickly. For local
(attended) servers located on site, you can set the software error recovery timeout for
20 or 30 minutes, giving you time to arrive at the server if you wish to manually diagnose the
problem.
The Compaq Health Driver is independent of the ASR-2 timer. You should load it and enable
the ASR-2 timer. This allows the driver to detect and log information in the IML regarding
numerous hardware and software errors. However, you cannot enable the ASR-2 timer without
loading the Compaq Health Driver.
Before ASR-2 restarts the server, it records any information available about the condition of the
operating system in the Critical Error Log, or the IML depending on the server support. This
information can be used to diagnose an operating system crash or server lock-up, while still
allowing the server to be restarted.