User guide
Table Of Contents
- HP ProLiant SL6000/6500 Scalable System User Guide
- Notice
- Contents
- Operations
- Setup
- Hardware options installation
- Introduction
- Processor option
- Memory options
- Hard drive options
- Hard drive backplane options
- Optical drive option
- PCI I/O device option
- Fan option
- Power supply options
- SAS or SATA power cabling options
- HP Trusted Platform Module option
- Cable management options
- Rack Control Manager option
- Switch options
- PDU rack-mounting hardware options
- Software and configuration utilities
- SmartStart Scripting Toolkit
- HP ROM-Based Setup Utility
- Array Configuration Utility
- Option ROM Configuration for Arrays
- ROMPaq Utility
- StorageWorks library and tape tools
- HP Systems Insight Manager
- HP Insight Diagnostics
- Integrated Management Log
- Lights-Out 100i Remote Management
- Array Diagnostic Utility
- Drivers
- Updating firmware
- Troubleshooting
- Common problem resolution
- Problem diagnosis
- Hardware problems
- Software tools and solutions
- Battery replacement
- Regulatory compliance notices
- Regulatory compliance identification numbers
- Federal Communications Commission notice
- Declaration of conformity for products marked with the FCC logo, United States only
- Modifications
- Cables
- Canadian notice (Avis Canadien)
- European Union regulatory notice
- Disposal of waste equipment by users in private households in the European Union
- Japanese notice
- BSMI notice
- Korean notice
- Chinese notice
- Laser compliance
- Battery replacement notice
- Taiwan battery recycling notice
- Power cord statement for Japan
- Acoustics statement for Germany (Geräuschemission)
- Electrostatic discharge
- Technical support
- Acronyms and abbreviations
- Index

Troubleshooting 42
3.
Be sure the memory modules are seated properly.
4. Be sure no operating system errors are indicated.
5. Restart the server and check to see if the error message is still displayed.
6. Run HP Insight Diagnostics (on page 20). Then, replace failed components as indicated.
Server fails to recognize existing memory
Action:
1. Reseat the memory. Use care when handling DIMMs.
2. Be sure the memory is configured properly. See the server documentation.
3. Be sure a memory count error did not occur ("Memory count error exists" on page 41). See the
message displaying memory count during POST.
Server fails to recognize new memory
Action:
1. Be sure the memory is the correct type for the server and is installed according to the server
requirements. Refer to the server documentation or HP website (
http://www.hp.com).
2. Be sure you have not exceeded the memory limits of the server or operating system. Refer to the
server documentation.
3. Be sure the memory is properly seated.
4. Be sure no conflicts are occurring with existing memory. Run the server setup utility.
5. Test the memory by installing the memory into a known working server. Be sure the memory meets
the requirements of the new server on which you are testing the memory.
6. Replace the memory. Refer to the server documentation.
Processor problems
Action:
1. If applicable, check the processor LEDs to identify if a PPM failure occurred. For information on LEDs,
refer to the server documentation.
2. Be sure each processor is supported by the server and is installed properly. Refer to the server
documentation for processor requirements.
3. Be sure the server ROM is up to date.
4. Be sure you are not mixing processor stepping, core speeds, or cache sizes if this is not supported
on the server. Refer to the server documentation for more information.
CAUTION: Removal of some processors and heatsinks require special considerations for
replacement, while other processors and heatsinks are integrated and cannot be reused once
separated. For specific instructions for the server you are troubleshooting, refer to processor
information in the Hardware options installation (on page
11) section on the Documentation
CD.
5. If the server has only one processor installed, replace it with a known functional processor. If the
problem is resolved after you restart the server, the original processor failed.
6. If the server has multiple processors installed, test each processor:










