Owner manual
Table Of Contents
- HP ProLiant BL495c Generation 5 Server Blade User Guide
- Notice
- Contents
- Component identification
- Operations
- Setup
- Hardware options installation
- Cabling
- Software and configuration utilities
- Server blade deployment tools
- Configuration tools
- Management tools
- Automatic Server Recovery
- ROMPaq utility
- iLO 2 technology
- Erase Utility
- StorageWorks library and tape tools
- HP Systems Insight Manager
- Management Agents
- HP ProLiant Essentials Virtualization Management Software
- HP ProLiant Essentials Vulnerability and Patch Management Pack
- HP Insight Server Migration software for ProLiant
- HP ProLiant Essentials Performance Management Pack
- HP Insight Control Environment Suites
- HP Insight Control Linux Edition
- Redundant ROM support
- USB support and functionality
- Diagnostic tools
- Remote support and analysis tools
- Keeping the system current
- Troubleshooting
- 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 private households in the European Union
- Japanese notice
- BSMI notice
- Korean notice
- Laser compliance
- Battery replacement notice
- Taiwan battery recycling notice
- Electrostatic discharge
- Specifications
- Technical support
- Acronyms and abbreviations
- Index

WARNING: Only authorized technicians trained by HP should attempt to repair this
equipment. All troubleshooting and repair procedures are detailed to allow only
subassembly/module-level repair. Because of the complexity of the individual boards and
subassemblies, no one should attempt to make repairs at the component level or to make
modifications to any printed wiring board. Improper repairs can create a safety hazard.
WARNING: To reduce the risk of personal injury or damage to the equipment, be sure that:
ched to the rack if it is a single-rack installation.
led together in multiple-rack installations.
• Only one component is extended at a time. A rack may become unstable if more than one
component is extended for any reason.
• The leveling feet are extended to the floor.
• The full weight of the rack rests on the leveling feet.
• The stabilizing feet are atta
• The racks are coup
Symptom information
• failure? After which steps does the problem occur?
e the server was working?
ttings in the server setup utility, if necessary?
• 49) and use the survey page to view the current configuration
for information.
Prepa
itioning,
uired environmental conditions, see the server documentation.
y the system.
, and USB drive keys.
be diagnosing the server offline. If
rver blade" on page 11).
5. Disconnect any peripheral devices not required for testing (any devices not necessary to power up
the server). Do not disconnect the printer if you want to use it to print error messages.
Before troubleshooting a server problem, collect the following information:
What events preceded the
• What has been changed since the tim
• Did you recently add or remove hardware or software? If so, did you remember to change the
appropriate se
• How long has the server exhibited problem symptoms?
• If the problem occurs randomly, what is the duration or frequency?
To answer these questions, the following information may be useful:
Run HP Insight Diagnostics (on page
or to compare it to previous configurations.
• Refer to your hardware and software records
• Refer to server LEDs and their statuses.
re the server for diagnosis
1. Be sure the server is in the proper operating environment with adequate power, air cond
and humidity control. For req
2. Record any error messages displayed b
3. Remove all diskettes, CD-ROMs, DVD-ROMs
4. Power down the server and peripheral devices if you will
possible, always perform an orderly shutdown:
a. Exit any applications.
b. Exit the operating system.
c. Power down the server ("Power down the se
Troubleshooting 55