ProLiant BL20p G4 - Server HP - Free user manual and instructions
Find the device manual for free ProLiant BL20p G4 HP in PDF.
| Product Type | Blade Server |
| Brand | HP |
| Model | ProLiant BL20p G4 |
| Form Factor | Blade (fits HP BladeSystem c-Class enclosure) |
| Processor | Dual Intel Xeon (up to 3.6 GHz, dual-core) |
| Memory | Up to 32 GB ECC DDR2 SDRAM |
| Storage | Up to two hot-plug SFF SAS hard drives |
| Networking | Embedded dual Gigabit Ethernet |
| Expansion Slots | One mezzanine slot for optional mezzanine cards |
| Power Supply | Dual hot-plug power supplies (800W each) |
| Dimensions (H x W x D) | 8.6 x 37.6 x 50.1 cm (3.4 x 14.8 x 19.7 in) |
| Weight | 6.8 kg (15.0 lb) |
| Management | Integrated Lights-Out (iLO 2) remote management |
| Cooling | Four hot-plug fans (shared in enclosure) |
| Operating Temperature | 10°C to 35°C (50°F to 95°F) |
| Compliance | RoHS, WEEE, ENERGY STAR |
| Safety | IEC 60950, UL 60950, CE Mark |
| Cleaning | Use a soft cloth with mild detergent; avoid harsh chemicals. |
| Spare Parts | Order through HP authorized partners: power supplies, fans, hard drives, memory. |
| Repairability | Hot-swappable components for easy maintenance; support contract recommended for advanced repairs. |
| General Information | Designed for high-density data center deployment; supports HP BladeSystem c7000 enclosures. |
Frequently Asked Questions - ProLiant BL20p G4 HP
User questions about ProLiant BL20p G4 HP
0 question about this device. Answer the ones you know or ask your own.
Ask a new question about this device
Download the instructions for your Server in PDF format for free! Find your manual ProLiant BL20p G4 - HP and take your electronic device back in hand. On this page are published all the documents necessary for the use of your device. ProLiant BL20p G4 by HP.
USER MANUAL ProLiant BL20p G4 HP
HP ProLiant BL20p Generation 4 Server Blade User Guide

© Copyright 2006 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Windows Server is a trademark of Microsoft Corporation.
AMD Athlon is a trademark of Advanced Micro Devices, Inc.
Intel and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Linux is a U.S. registered trademark of Linus Torvalds.
Java is a U.S. trademark of Sun Microsystems, Inc.
March 2006 (First Edition)
Part Number 405591-001
Audience assumptions
This document is for the person who installs, administers, and troubleshoots servers and storage systems. HP assumes you are qualified in the servicing of computer equipment and trained in recognizing hazards in products with hazardous energy levels.
Contents
Component identification....6
Server blade components 6
Front panel components 6
Front panel LEDs....7
Rear panel components 8
SAS and SATA hard drive LEDs....8
SAS and SATA hard drive LED combinations....9
Internal components....10
System maintenance switch....11
Local I/O cable 12
Server blade enclosure bay numbering 12
iLO 2 connections ...... 13
Server blade enclosure compatibility.... 13
Operations.... 15
Power up the server blade....15
Power down the server blade....15
Remove the server blade 16
Remove the access panel....16
Install the access panel....17
Remove the air baffle....17
Setup....19
Installing the HP BladeSystem components....19
Verifying system components 19
Connecting to the network....19
Installing server blade options....20
Installing a server blade 20
Completing the configuration....21
Hardware options installation.... 22
Processor option....22
Memory option 27
FBDIMM guidelines 27
Single- and dual-rank FBDIMMs....27
Installing FBDIMMs 28
Hard drive option....28
Multifunction network adapter option 29
Fibre Channel mezzanine option....30
Interconnect options....31
HP Smart Array Battery-Backed Write Cache Enabler option....31
Local I/O cabling 35
Using the local I/O cable 35
Local administration using iLO 2 35
Connecting locally to a server blade with video and USB devices....36
Accessing a server blade with local KVM 36
Accessing local media devices....37
Configuration and utilities 39
Server blade deployment tools 39
Software drivers and additional components.... 39
ProLiant p-Class Advanced management 39
Network-based PXE deployment 40
Static IP bay configuration 42
Deployment methods....42
Configuration tools 46
SmartStart software....46
HP ROM-Based Setup Utility 46
Array Configuration Utility 48
Option ROM Configuration for Arrays 48
Re-entering the server serial number and product ID 48
Management tools....49
Automatic Server Recovery 49
ROMPaq utility....49
Integrated Lights-Out 2 technology....49
HP Systems Insight Manager 50
Management Agents....50
Redundant ROM support 50
USB support....50
Diagnostic tools 51
HP Insight Diagnostics 51
Integrated Management Log 51
Remote support and analysis tools 52
HP Instant Support Enterprise Edition....52
Web-Based Enterprise Service....52
Open Services Event Manager 52
Keeping the system current 52
Drivers 52
Resource Paqs....53
ProLiant Support Packs 53
Operating system version support....53
System online ROM flash component utility 53
Change control and proactive notification 53
Natural language search assistant....53
Care Pack 54
Troubleshooting 55
Troubleshooting resources 55
Pre-diagnostic steps 55
Important safety information....56
Symptom information 57
Prepare the server for diagnosis 58
Service notifications....58
Loose connections 58
Troubleshooting flowcharts 59
Start diagnosis flowchart 59
General diagnosis flowchart 60
Server blade power-on problems flowchart 62
POST problems flowchart 64
OS boot problems flowchart 66
Server fault indications flowchart 68
POST error messages and beep codes 70
Battery replacement 71
Regulatory compliance notices 72
Regulatory compliance identification numbers....72
Federal Communications Commission notice....72
FCC rating label....72
Class A equipment....73
Class B equipment 73
Declaration of conformity for products marked with the FCC logo, United States only....73
Cables....74
Modifications....74
European Union regulatory notice 74
Disposal of waste equipment by users in private households in the European Union 74
Canadian notice (Avis Canadien)....75
Japanese notice 75
BSMI notice 75
Korean notice 76
Battery replacement notice....76
Taiwan battery recycling notice....76
Electrostatic discharge 78
Preventing electrostatic discharge 78
Grounding methods to prevent electrostatic discharge....78
Specifications 79
Environmental specifications 79
Server specifications....79
Technical support....80
Before you contact HP 80
HP contact information....80
Customer Self Repair 80
Acronyms and abbreviations 88
Index 92
Component identification
In this section
Server blade components 6
Local I/O cable 12
Server blade enclosure bay numbering 12
iLO 2 connections 13
Server blade enclosure compatibility 13
Server blade components
Front panel components

| Item | Description |
| 1 | I/O port* |
| 2 Hot-plug SAS or SATA hard drive bay 1 | |
| 3 Hot-plug SAS or SATA hard drive bay 2 | |
| 4 Server blade handle | |
* The I/O port is used with the local I/O cable to perform some server blade configuration and diagnostic procedures.
Front panel LEDs

| Item | Description | Status |
| 1 UID LED Blue = Identified | Blue flashing = Active remote managementOff = No active remote management | |
| 2 Health LED | Green = Normal | Green flashing = BootingAmber = Degraded conditionRed = Critical condition |
| 3 NIC 1 LED* | Green = Network linked | Green flashing = Network activityOff = No link or activity |
| 4 NIC 2 LED* | Green = Network linked | Green flashing = Network activityOff = No link or activity |
| 5 NIC 3 LED* | Green = Network linked | Green flashing = Network activityOff = No link or activity |
| 6 NIC 4 LED* | Green = Network linked | Green flashing = Network activityOff = No link or activity |
| 7 System power LED Green = On | Amber = Standby (auxiliary power available)Off = Off | |
| 8 Fault/UID | Blue = Unit ID | Amber flashing = Drive failureOff = Not in management mode |
| 9 Drive activity | Green = Active online conditionOff = Inactive online condition | |
* Actual NIC numeration depends on several factors, including the operating system installed on the server blade.
Rear panel components

| Item | Description |
| 1 | Power connector |
| 2 | Signal connector |
SAS and SATA hard drive LEDs

| Item | Description |
| 1 Fault/UID | LED (amber/blue) |
| 2 Online LED (green) | |
SAS and SATA hard drive LED combinations
| Online/activity LED (green) | Fault/UID LED (amber/blue) | Interpretation |
| On, off, or flashing | Alternating amber and blue | The drive has failed, or a predictive failure alert has been received for this drive; it also has been selected by a management application. |
| On, off, or flashing | Steadily blue | The drive is operating normally, and it has been selected by a management application. |
| On | Amber, flashing regularly (1 Hz) | A predictive failure alert has been received for this drive. Replace the drive as soon as possible. |
| On Off The drive is online, but it is not active currently. | ||
| Flashing regularly (1 Hz) | Amber, flashing regularly (1 Hz) | Do not remove the drive. Removing a drive may terminate the current operation and cause data loss.The drive is part of an array that is undergoing capacity expansion or stripe migration, but a predictive failure alert has been received for this drive. To minimize the risk of data loss, do not replace the drive until the expansion or migration is complete. |
| Flashing regularly (1 Hz) | Off | Do not remove the drive. Removing a drive may terminate the current operation and cause data loss.The drive is rebuilding, or it is part of an array that is undergoing capacity expansion or stripe migration. |
| Flashing irregularly | Amber, flashing regularly (1 Hz) | The drive is active, but a predictive failure alert has been received for this drive. Replace the drive as soon as possible. |
| Flashing irregularly | Off The drive is active, and it is operating normally. | |
| Off | Steadily | A critical default condition has been identified for this drive, and the controller has placed it offline. Replace the drive as soon as possible. |
| Off | Amber, flashing regularly (1 Hz) | A predictive failure alert has been received for this drive. Replace the drive as soon as possible. |
| Off | Off | The drive is offline, a spare, or not configured as part of an array. |
Internal components

| Item | Description |
| 1 | HP Smart Array SAS/SATA Battery-Backed Write Cache enabler (optional) * |
| 2 Internal USB connector | |
| 3 SAS backplane power connector | |
| 4 | Fan connectors |
| 5 Power button/LED board connector | |
| 6 SAS backplane power connector | |
| 7 Processor socket 2 | |
| 8 SAS backplane connector | |
| 9 HP Smart Array SAS/SATA memory slot | |
| 10 HP Smart Array SAS/SATA RAID controller | |
| 11 FBDIMM slots 1-8 | |
| 12 | NMI switch |
| 13 | System battery |
| 14 Power converter modules | |
| 15 NIC mezzanine connector | |
| 16 System maintenance switch (SW4) | |
| 17 Fibre Channel adapter connectors | |
| 18 Processor socket 1 (populated) | |
| 19 | HP Smart Array SAS/SATA Battery-Backed Write Cache enabler (optional) * |
* Only one Battery-Backed Write Cache enabler can be installed.
FBDIMM slots

| Item | Description |
| 1 FBDIMM slo | 1A |
| 2 FBDIMM slo | 2C |
| 3 FBDIMM slo | 3A |
| 4 FBDIMM slo | 4C |
| 5 FBDIMM slo | 5B |
| 6 FBDIMM slo | 6D |
| 7 FBDIMM slo | 7B |
| 8 FBDIMM slo | 8D |
System maintenance switch
| Position | Function | Default | |
| 1* iLO 2 security override Off | |||
| 2 | Configuration lock | ||
| 3 | Reserved | Off | |
| 4 | Reserved | Off | |
| 5* | Password disabled | ||
| 6* | Reset configuration | ||
| 7 | Reserved | Off | |
| 8 | Reserved | Off | |
Off
Off
Off
*To access redundant ROM, set S1, S5, and S6 to ON.
Local I/O cable

| Item | Connector | Description |
| 1 | Local I/O | For connecting to the local I/O port on the server blade front panel |
| 2 Video For | connecting a video monitor | |
| 3 USB 1 For | connecting a USB device | |
| 4 USB 2 For | connecting a USB device | |
| 5 | Serial | For trained personnel to connect a null modem serial cable and perform advanced diagnostic procedures |
| 6 | iLO 2 RJ-45(10/100 Ethernet) | For connecting an Ethernet to the server blade iLO 2 interface from a client device |
Server blade enclosure bay numbering
Each server blade enclosure requires a pair of interconnect modules to provide network access for data transfer. Resolve bay numbering before determining connections between the server blades and interconnects.

IMPORTANT: When looking at the rear of the enclosure, server blade bay numbering is reversed.

iLO 2 connections
An iLO 2 connector resides on the server blade management module of the enhanced server blade enclosure. This RJ-45 connector enables remote manageability for each server blade in the enhanced server blade enclosure.

For more information about the enhanced server blade enclosure, refer to the HP ProLiant BL p-Class Server Blade Enclosure Upgrade Installation Guide or the HP ProLiant BL p-Class Server Blade Enclosure Installation Guide.
Server blade enclosure compatibility
Certain configurations of the HP ProLiant BL20p server blade may require the support of an HP BladeSystem p-Class server blade enclosure with enhanced backplane components (enhanced Server
Blade Enclosure). For information on the compatibility of server blade enclosures, refer to the HP website (http://www.hp.com/go/bladesystem/enclosure/compatibility).
Operations
In this section
Power up the server blade.... 15
Power down the server blade 15
Remove the server blade 16
Remove the access panel 16
Install the access panel 17
Remove the air baffle....17
Power up the server blade
By default, the server blade is set to power up automatically when installed in the server blade enclosure. Be sure the server blade is compatible with the server blade enclosure. Refer to "Server blade enclosure compatibility (on page 13)."
If the default setting is changed, use one of the following methods to power up the server blade:
- Press the Power On/Standby button on the server blade front panel.
- A momentary press initiates a power-up request. The server blade determines power availability from the power subsystem. If required power is available, the server blade powers up.
- A press of 5 seconds or more initiates a power-up override. The server blade powers up without power availability detection from the system.
△ CAUTION: Always observe iLO 2 alerts before initiating a power-up override to prevent a hot-plug power supply fault and possible loss of system power. For more information, refer to the HP Integrated Lights-Out User Guide.
NOTE: You can perform a server blade power-up override when the management modules are not in use to manage the power-up request. Be sure that sufficient power is available.
• Use the virtual power button features in iLO 2.
• A momentary power-up selection
• A hold power-up selection
For more information about iLO 2, refer to "Configuration and utilities (on page 39)."
Power down the server blade
Power down the server blade using either of the following methods:
- Press the Power On/Standby button on the server blade front panel.
Be sure that the server blade is in standby mode by observing that the system power LED is amber.
This process may take 30 seconds, during which time some internal circuitry remains active.
- Use the virtual power button feature in iLO 2.
After initiating a manual or virtual power down command, be sure that the server blade goes into standby mode by observing that the system power LED is amber.

IMPORTANT: When the server blade is in standby mode, auxiliary power is still being provided. To remove all power from the server blade, remove the server blade from the server blade enclosure.

IMPORTANT: Remote power procedures require the most recent firmware for the power enclosure and server blade enclosure management modules. For the most recent firmware, refer to the HP website (http://www.hp.com/go/support).
Remove the server blade
- Identify the proper server blade in the server blade enclosure.
- Back up all server blade data.
- Power down the server blade (on page 15).
- Remove the server blade from the server blade enclosure.

- Place the server blade on a flat, level work surface.

WARNING: To reduce the risk of personal injury from hot surfaces, allow the drives and the internal system components to cool before touching them.

CAUTION: To prevent damage to electrical components, properly ground the server blade before beginning any installation procedure. Improper grounding can cause ESD.
Remove the access panel

WARNING: To reduce the risk of personal injury from hot surfaces, allow the drives and the internal system components to cool before touching them.

CAUTION: To prevent damage to electrical components, properly ground the server blade before beginning any installation procedure. Improper grounding can cause ESD.
- Back up all server blade data.
- Power down the server blade (on page 15).
-
Remove the server blade (on page 16).
-
Identify the proper server blade in the server blade enclosure.
-
Loosen the screw on the rear of the access panel.
- Remove the access panel.

Install the access panel
- Place the access panel on top of the server blade, allowing it to extend past the rear of the server approximately 10 mm (0.39 in).
- Slide the access panel forward to lock, and tighten the captive screw to secure the access panel to the server.
Remove the air baffle
To remove the component:
- Power down the server blade (on page 15).
- Remove the server blade (on page 16).
-
Remove the access panel (on page 16).
-
Remove the air baffle.

To replace the component, reverse the removal procedure.

IMPORTANT: To ensure proper cooling, be sure the correct processor air baffle is installed at all times.
Setup
In this section
Installing the HP BladeSystem components.... 19
Verifying system components 19
Connecting to the network.... 19
Installing server blade options....20
Installing a server blade 20
Completing the configuration.... 21
Installing the HP BladeSystem components
Before performing any server blade-specific procedures, install the HP BladeSystem components in your environment. Refer to the hardware installation and configuration poster that ships with the server blade enclosure.
The most current documentation for server blades and other HP BladeSystem p-Class components is available at the HP website (http://www.hp.com/products/servers/proliant-bl/p-class/info).
Documentation is also available in the following locations:
• Documentation CD that ships with the server blade enclosure
• HP Business Support Center website (http://www.hp.com/support)
• HP Technical Documentation website (http://docs.hp.com)
Verifying system components
- Verify that the proper server blade enclosure is installed for the server blade. Refer to "Server blade enclosure compatibility (on page 13)."
- Verify that adequate power is available. Refer to the HP BladeSystem p-Class power calculator on the HP website (http://www.hp.com/go/bladesystem/powercalculator).
Connecting to the network
To connect the HP BladeSystem to a network, each server blade enclosure must be configured with a pair of network interconnects to manage signals between the server blades and the external network. For more information about interconnect options, refer to the HP website (http://www.hp.com/go/bladesystem/interconnects).
For network cabling connections for the server blade, refer to the HP ProLiant BL20p Generation 4 Server Blade Installation Instructions that ship with the server blade.
Installing server blade options
Before installing and initializing the server blade, install any hardware options, such as an additional processor or hard drives. For server blade options installation information, refer to "Hardware options installation (on page 22)."
Installing a server blade
- Remove a 6U server blade blank.

- Install the server blade. When the server blade is fully inserted, it locks into place.

The default setting for server blades initiates automatic power up.

CAUTION: To prevent improper cooling and thermal damage, do not operate the server blade enclosure unless all bays are populated with either a component or a blank.

NOTE: The first server blade must be installed into a server blade enclosure to facilitate naming the server blade enclosure, the rack, and the interconnects. Complete the system configuration before installing additional server blades.
Completing the configuration
To complete the server blade and HP BladeSystem configuration, refer to the hardware installation and configuration poster that ships with the server blade enclosure.
Hardware options installation
In this section
Processor option....22
Memory option 27
Hard drive option.... 28
Multifunction network adapter option....29
Fibre Channel mezzanine option.... 30
Interconnect options.... 31
HP Smart Array Battery-Backed Write Cache Enabler option 31
Processor option
The server blade supports dual-processor operation. With two processors installed, the server blade supports boot functions through the processor installed in processor socket 1. However, if processor 1 fails, the system automatically boots from processor 2 and provides a processor failure message.
△ CAUTION: Removal of the processor or heatsink renders the thermal layer between the processor and heatsink useless. A new heatsink must be ordered and installed before reinstalling the processor.
IMPORTANT: Processor socket 1 must be populated at all times or the server blade does not function.
△ CAUTION: To prevent possible server blade overheating, always populate processor socket 2 with a processor and a heatsink or a processor cover and a heatsink blank.
To install the component:
- Power down the server blade (on page 15).
- Remove the server blade (on page 16).
-
Remove the access panel (on page 16).
-
Open the processor retaining latch and the processor socket retaining bracket.

- Remove the processor socket protective cover.


IMPORTANT: Be sure the processor remains inside the processor installation tool.
- If the processor has separated from the installation tool, carefully re-insert the processor in the tool.

- Align the processor installation tool with the socket and install the processor.

- Press down firmly until the processor installation tool clicks and separates from the processor, and then remove the processor installation tool.

- Close the processor socket retaining bracket and the processor retaining latch.

- Remove the heatsink protective cover.

-
Align the holes in the bottom of the heatsink with the pins in the heatsink retention module.
-
Install the heatsink and close the heatsink retaining latch.

- If installing a second processor, first remove the processor blank, then repeat the previous steps of this procedure.
△ CAUTION: To prevent possible server blade overheating, always populate processor socket 2 with a processor and a heatsink or a processor cover and a heatsink blank.

- Install the access panel (on page 17).
- Install the server blade ("Installing a server blade" on page 20).
- Power up the server blade (on page 15).
NOTE: By default, the server blade powers up on installation.
Memory option
The server blade ships with two FBDIMMs installed. The server blade supports up to 32 GB of memory.
△ CAUTION: Use only HP FBDIMMs. FBDIMMs from other sources may adversely affect data integrity.
FBDIMM guidelines
Observe the following FBDIMM installation guidelines:
All FBDIMMs must be PC-5300 DDR2 667-MHz SDRAM FBDIMMs.
• Both FBDIMM slots in a memory bank must be populated.
• Both FBDIMMs in a memory bank must be identical.
- If mixing dual- and single-rank FBDIMMs, the dual-rank FBDIMMs must be installed in memory bank 1.
Single- and dual-rank FBDIMMs
PC3200 FBDIMMs can either be single- or dual-rank. While it is not normally important for you to differentiate between these two types of FBDIMMs, certain FBDIMM configuration requirements are based on these classifications.
Certain configuration requirements exist with single- and dual-rank FBDIMMs that allow the architecture to optimize performance. A dual-rank FBDIMM is similar to having two separate FBDIMMs on the same module. Although only a single FBDIMM module, a dual-rank FBDIMM acts as if it were two separate FBDIMMs. The purpose of dual-rank FBDIMMs is to provide the largest capacity FBDIMM given the
current FBDIMM technology. If the maximum FBDIMM technology allows for 2-GB single-rank FBDIMMs, a dual-rank FBDIMM using the same technology would be 4-GB.
Installing FBDIMMs
- Power down the server blade (on page 15).
- Remove the server blade (on page 16).
- Remove the access panel (on page 16).
- Open the FBDIMM slot latches.
- Install the FBDIMM.

To remove FBDIMMs, reverse the installation procedure. For FBDIMM slots 1 and 2, remove the air baffle, if necessary. Refer to the instructions located on the air baffle.
Hard drive option
The server blade supports up to two SAS or SATA drives.
△ CAUTION: To prevent improper cooling and thermal damage, do not operate the server blade or the enclosure unless all hard drive and device bays are populated with either a component or a blank.
To install the component:
- Remove the hard drive blank.

- Install the hard drive.

-
Determine the status of the hard drive from the hot-plug hard drive LEDs. ("SAS and SATA hard drive LEDs" on page 8)
-
Resume normal server operations.
Multifunction network adapter option
To install the component:
- Back up all server blade data.
- Power down the server blade (on page 15).
- Remove the server blade (on page 16).
-
Remove the access panel (on page 16).
-
Install the multifunction network adapter.

- Install the access panel (on page 17).
- Install the server blade ("Installing a server blade" on page 20).
- Power up the server blade (on page 15).

NOTE: By default, the server blade powers up on installation.
Fibre Channel mezzanine option
An optional dual port FC mezzanine enables FC support for clustering capabilities and SAN connection when used in conjunction with interconnect devices that support a SAN connection. For more information about connecting to the SAN, refer to "SAN configuration (on page 45)".
Server blades can be configured for SAN connectivity when used with the following components.
- FC mezzanine
• Supported p-Class server blades
• SAN-compatible interconnect
• SFP transceivers (included with the Dual Port FC mezzanine)
• Optical FC cables (not included)
• Supported SAN and associated software
For more detailed SAN configuration information for the server blade, refer to:
• The model-specific QuickSpecs document located on the HP ProLiant p-Class server blade products web page at the HP website (http://www.hp.com/products/servers/proliant-bl/p-class/info)
• The HP StorageWorks SAN documentation at the HP website (http://h18006.www1.hp.com/products/storageworks/san/documentation.html)
• The HP BladeSystem p-Class storage website (http://www.hp.com/go/bladesystem/storage)
To install the component:
- Power down the server blade (on page 15).
- Remove the server blade (on page 16).
-
Remove the access panel (on page 16).
-
Refer to the label on the FC mezzanine to verify compatibility with the server blade.
- Align the FC mezzanine with the FC connectors ("Internal components" on page 10).
- Install the FC mezzanine.

- Connect the FC mezzanine cable to the FC mezzanine connector.
- Install the access panel (on page 17).
- Install the server blade ("Installing a server blade" on page 20).
- If connecting to SAN, install one of the interconnect device options ("Interconnect options" on page 31).
Interconnect options
To connect to SAN using optical cables, you must install either an RJ-45 Patch Panel 2 or a SAN-compatible interconnect option kit in the server blade enclosure.
For information on installing interconnect option kits, refer to the kit documentation:
• For information on installing patch panels, refer to the RJ-45 Patch Panel 2 Installation Instructions.
- For information on installing interconnect devices, refer to the quick setup instructions for the device on the HP website (http://www.hp.com/go/bladesystem/interconnects).
HP Smart Array Battery-Backed Write Cache Enabler option
The optional BBWC enabler provides the system with a means for storing and saving data in the event of an unexpected system shutdown.
To install the component:
- Power down the server blade (on page 15).
- Remove the server blade (on page 16).
- Remove the access panel (on page 16).
- Install the BBWC enabler:
• HP Smart Array E200i Controller battery pack

• HP Smart Array P400i Controller battery pack


- Connect the cable to the cache module:
• HP Smart Array E200i Controller

• HP Smart Array P400i Controller

- Install the access panel (on page 17).
- Install the server blade ("Installing a server blade" on page 20).
- Power up the server blade (on page 15).

NOTE: By default, the server blade powers up on installation.
Local I/O cabling
In this section
Using the local I/O cable....35
Local administration using iLO 2 35
Connecting locally to a server blade with video and USB devices 36
Using the local I/O cable
The local I/O cable enables the user to perform server blade administration, configuration, and diagnostic procedures in two ways:
• Connecting locally to the server blade iLO 2 interface
• Connecting video and USB devices directly to the server blade
Local administration using iLO 2
To connect locally to iLO 2 with the local I/O cable, you must have the following:
• A client device with a 10/100 Ethernet RJ-45 connector
• A network cable with RJ-45 connectors
To connect to iLO 2:
△ CAUTION: Do not connect the local I/O cable to a hub when connecting to iLO 2. All server blades have the same IP address through the I/O port. Multiples on a hub make the server blades indistinguishable on the network.
- Use the RJ-45 network cable to connect the local client device to the local I/O cable.

- Connect the local I/O cable to the I/O port on the server blade.

△ CAUTION: Disconnect the local I/O cable when not in use. The port and connector do not provide a permanent connection. Rear iLO 2 connector performance degrades when the local I/O cable is connected, even if the iLO 2 connector on the cable is not in use.
△ CAUTION: Before disconnecting the local I/O cable, observe the following guidelines:
- Completely log out of the current iLO 2 session before disconnecting from the iLO 2 port. Do not remove the local I/O cable when the UID LED is flashing.
- Always squeeze the locking buttons on the side of the server blade connector before disconnecting from the I/O port. Failure to do so can result in damage to the equipment.
Connecting locally to a server blade with video and USB devices
Use the local I/O cable to connect a monitor and any of the following USB devices:
- USB hub
- USB keyboard
- USB mouse
• USB CD/DVD-ROM drive - USB diskette drive
Numerous configurations are possible. This section offers two possible configurations.
Accessing a server blade with local KVM
△ CAUTION: Disconnect the local I/O cable when not in use. The port and connector do not provide a permanent connection. Rear iLO 2 connector performance degrades when the local I/O cable is connected, even if the iLO 2 connector on the cable is not in use.
NOTE: For this configuration, a USB hub is not necessary. To connect additional devices, use a USB hub.
- Connect the local I/O cable to the server blade ("Local administration using iLO 2" on page 35).
-
Connect the video connector to a monitor.
-
Connect a USB mouse to one USB connector.
- Connect a USB keyboard to the second USB connector.

| Item | Description | |
| 1 | Monitor | |
| 2 | USB | mouse |
| 3 | USB | keyboard |
| 4 Local I/O cable | ||
Accessing local media devices
Use the following configuration when configuring a server blade or loading software updates and patches from a CD-ROM, such as the SmartStart CD, or a diskette.

CAUTION: Disconnect the local I/O cable when not in use. The port and connector do not provide a permanent connection. Rear iLO 2 connector performance degrades when the local I/O cable is connected, even if the iLO 2 connector on the cable is not in use.
- Connect the local I/O cable to the server blade.
- Connect the video connector to a monitor.
- Connect a USB hub to one USB connector.
-
Connect the following to the USB hub:
-
USB CD-ROM drive
- USB keyboard
- USB mouse
NOTE: HP recommends the use of a USB hub when connecting a USB diskette drive and/or USB CD-ROM drive to the server blade. The USB hub provides additional connections.

| Item | Description |
| 1 Local I/O cable | |
| 2 | Monitor |
| 3 | USB hub |
| 4 USB CD-ROM drive or USB diskette drive | |
| 5 | USB keyboard |
| 6 | USB mouse |
Configuration and utilities
In this section
Server blade deployment tools 39
Configuration tools 46
Management tools.... 49
Diagnostic tools 51
Remote support and analysis tools 52
Keeping the system current 52
Server blade deployment tools
Software drivers and additional components
HP offers the following additional software components for server blades:
• Health and Wellness driver and IML viewer
- iLO 2 Advanced Management interface driver
- Rack infrastructure interface service
For Microsoft® Windows® OS users, these items are included in the ProLiant Support Pack for Microsoft® Windows®, available from the HP website (http://h18002.www1.hp.com/support/files/server/us/index.html).
Linux OS users can download these components from the HP website (http://www.hp.com/products/servers/linux).
For information on how to use these components with a Linux OS, refer to the HP website (http://h18000.www1.hp.com/products/servers/linux/documentation.html#howtos).
ProLiant p-Class Advanced management
iLO 2 Advanced is a standard component of ProLiant p-Class server blades that provides server health and remote server blade manageability. Its features are accessed from a network client device using a supported web browser. In addition to other features, iLO 2 Advanced provides keyboard, mouse, and video (text and graphics) capability for a server blade, regardless of the state of the host OS or host server blade.
iLO 2 includes an intelligent microprocessor, secure memory, and a dedicated network interface. This design makes iLO 2 independent of the host server blade and its OS. iLO 2 provides remote access to any authorized network client, sends alerts, and provides other server blade management functions.
Using a supported web browser, you can:
-
Remotely access the console of the host server blade, including all text mode and graphics mode screens with full keyboard and mouse controls.
• Remotely power up, power down, or reboot the host server blade. -
Remotely boot a host server blade to a virtual diskette image to perform a ROM upgrade or install an OS.
- Send alerts from iLO 2 Advanced regardless of the state of the host server blade.
- Access advanced troubleshooting features provided by iLO 2 Advanced.
- Launch a web browser, use SNMP alerting, and diagnose the server blade with HP SIM.
- Configure static IP bay settings for the dedicated iLO 2 management NICs on each server blade in an enclosure for faster deployment.
The server blade must be properly cabled for iLO 2 connectivity. Connect to the server blade with one of the following methods:
- Through an existing network (in the rack)—This method requires you to install the server blade in its enclosure and assign it an IP address manually or using DHCP.
- Through the server blade I/O port (in the rack)—This method requires you to connect the local I/O cable to the I/O port and a client PC. Using the static IP address listed on the I/O cable label and the initial access information on the front of the server blade, you can access the server blade with the iLO 2 Advanced Remote Console.
The p-Class tab enables you to control specific settings for the HP BladeSystem. iLO 2 also provides web-based status for the HP BladeSystem configuration.
For detailed information about iLO 2 Advanced, refer to the HP Integrated Lights-Out User Guide on the HP website (http://www.hp.com/servers/lights-out).
Network-based PXE deployment
PXE is a component of the Intel® WfM specification. The PXE model enables server blades to load and execute an NBP from a PXE server and to execute a pre-configured image. The image can be an OS image created by software utilities or a boot diskette image. This feature enables a user to configure a server blade and install an OS over a network.
Deployment overview
When a PXE-enabled client boots, it obtains an IP address from a DHCP server. The client obtains the name of the NBP from the appropriate boot server. Then, the client uses TFTP to download the NBP from the boot server and executes the image.
For each server blade being deployed, the PXE server must be connected to the NIC designated for PXE. The server blade defaults PXE functions to NIC 1, but any of the two NC series NICs can be designated for PXE in RBSU. For NIC connector locations on RJ-45 patch panels and interconnect switches, refer to the documentation included with the server blade.

NOTE: Actual NIC numeration depends on several factors, including the OS installed on the server blade.
To deploy an OS to multiple server blades, install a PXE deployment server on a network.
Deployment infrastructure
To establish a network-based PXE deployment infrastructure, provide the following software and minimum hardware:
- Client PC (administrative workstation)
- AMD Athlon™ XP processor (700 MHz or greater recommended), AMD Athlon™ 64 processor, or Intel® Pentium® III or higher processor (700 MHz or greater recommended)
• 128 MB of RAM -
Microsoft® Windows® 2000 Professional or Microsoft® Windows® XP OS
-
Microsoft® Internet Explorer 5.5 or above with 128-bit encryption
- Ethernet NIC with 10/11 RJ-45 connector
- TCP/IP networking and an IP address compatible with one of the following: the iLO 2 Diagnostic Port IP address or an assigned DHCP or static IP address
• CD-ROM drive and/or diskette drive
• Any of the following Java™ Runtime Environment versions:
1.3.1_02
1.3.1_07
1.3.1_08
1.4.1 for Windows® users only
1.4.2 for Linux users only
Access the Java™ Runtime Environment versions at the HP website (http://java.sun.com/products/archive/index.html).
• DHCP server (IP address assignment)
- AMD Athlon™ XP processor (700 MHz or greater recommended), AMD Athlon™ 64 processor, or Pentium® or Pentium® II 200-MHz or faster processor
- 64 MB of RAM
- 64 MB of free hard drive space
• 10-Mb/s network adapter
- PXE deployment server (storing boot images)
- AMD Athlon™ XP processor (700 MHz or greater recommended), AMD Athlon™ 64 processor, or Intel® Pentium® III or higher processor (500 MHz recommended)
- 256 MB of RAM
• 10-Mb/s network adapter - CD-ROM drive
• NFS repository server (only required for Red Hat Linux deployment)
• Red Hat Linux 7.2 OS installed
• Network connection
- CD-ROM drive
- NFS installed
• 1.5 GB of available disk space
- Windows® repository server (only required for Windows® deployment)
- Windows® 2000 or Windows® 2003 OS installed
• Network connection - CD-ROM drive
• 1.5 GB of available disk space
- TCP/IP networking and an IP address compatible with one of the following: the iLO 2 Diagnostic Port IP address or an assigned DHCP or static IP address
• CD-ROM drive and/or diskette drive
• Any of the following Java™ Runtime Environment versions:
1.3.1_02
1.3.1_07
1.3.1_08
1.4.1 for Windows® users only
1.4.2 for Linux users only
Access the Java™ Runtime Environment versions at the HP website (http://java.sun.com/products/archive/index.html).
• Network server with an OS installed
Static IP bay configuration
Static IP bay configuration, implemented using the new Static IP Bay Settings on the BL p-Class tab, eases the initial deployment of an entire enclosure or the subsequent deployment of blades within an existing enclosure. While the preferred method for assigning IP addresses the iLO 2 to each blade is through DHCP and DNS, these protocols are not always available on non-production networks.
Static IP bay configuration automates the first step of BL p-Class blade deployment by enabling the iLO 2 management processor in each blade slot to obtain a predefined IP address without relying on DHCP. iLO 2 is immediately accessible for server deployment using Virtual Media and other remote administration functions.
Static IP bay configuration uses the Static IP Bay Configuration addressing method which enables you to assign IP addresses to each iLO based on slot location in the respective server enclosure. By providing a set of IP addresses in the enclosure, you gain the advantages of a static IP bay configuration, without requiring each individual iLO 2 to be configured locally.
Using iLO 2 static IP bay configuration:
• Helps avoid the costs of a DHCP infrastructure to support the blade environment
- Provides easier setup with automatic iLO 2 address generation for all or a few selected bays
For detailed information about iLO configurations, refer to the HP Integrated Lights-Out User Guide on the Documentation CD or to the HP website (http://www.hp.com/servers/lights-out).
Deployment methods
Four primary deployment methods are supported:

IMPORTANT: To deploy a server blade without the RDP, create a bootable diskette or image of a bootable diskette.
• PXE deployment (on page 42)
• CD-ROM deployment (on page 43)
• Diskette image deployment (on page 44)
• SAN configuration (on page 45)
PXE deployment
PXE enables server blades to load an image over the network from a PXE server, and then execute it in memory. The first NIC on the server blade is the default PXE boot NIC, but any of the other NC series NICs can be configured to boot PXE. For more information, refer to "Network-based PXE deployment (on page 40)."

NOTE: Actual NIC numeration depends on several factors, including the OS installed on the server blade.
HP recommends using one of the following methods for PXE deployment:
• HP ProLiant Essentials RDP ("HP ProLiant Essentials Rapid Deployment Pack" on page 43)
• SmartStart Scripting Toolkit (on page 43)
A number of third-party PXE deployment tools are available for Windows® and Linux. For additional information, refer to the HP website
(ftp://ftp.compaq.com/pub/products/servers/management/pxe_wp.pdf).
HP ProLiant Essentials Rapid Deployment Pack

NOTE: To deploy server blades in an existing server blade enclosure, always use the most recent version of RDP available at the HP website (http://www.hp.com/servers/rdp).
The RDP software is the preferred method for rapid, high-volume server deployments. The RDP software integrates two powerful products: Altiris Deployment Solution and the HP ProLiant Integration Module.
The intuitive graphical user interface of the Altiris Deployment Solution console provides simplified point-and-click and drag-and-drop operations that enable you to deploy target servers, including server blades, remotely. It enables you to perform imaging or scripting functions and maintain software images.
For more information about the RDP, refer to the HP ProLiant Essentials Rapid Deployment Pack CD or refer to the HP website (http://www.hp.com/servers/rdp).
SmartStart Scripting Toolkit
The SmartStart Scripting Toolkit is a server deployment product that delivers an unattended automated installation for high-volume server deployments. The SmartStart Scripting Toolkit is designed to support ProLiant BL, ML, and DL servers. The toolkit includes a modular set of utilities and important documentation that describes how to apply these new tools to build an automated server deployment process.
Using SmartStart technology, the Scripting Toolkit provides a flexible way to create standard server configuration scripts. These scripts are used to automate many of the manual steps in the server configuration process. This automated server configuration process cuts time from each server deployed, making it possible to scale server deployments to high volumes in a rapid manner.
For more information, and to download the SmartStart Scripting Toolkit, refer to the HP website (http://www.hp.com/servers/sstoolkit).
CD-ROM deployment
CD-ROM deployment involves using a bootable CD that executes script to configure the hardware and install the OS. After the OS is configured, the server blade can access the network to locate the scripts and files necessary for deployment.
Before beginning the deployment process, connect the server blade to the network with one of the following methods:
- Through an existing network (in the rack)—For this method, install the server blade in its enclosure and assign it an IP address (manually or with DHCP).
- Through an existing network (out of the rack, with the diagnostic station)—For this method, power the server blade with the diagnostic station and connect to an existing network through a hub. The DHCP server on the network assigns the IP address.
Other methods for connecting to the server blade are available, but they do not provide the required network access for deployment. For more information, refer to "ProLiant p-Class Advanced management (on page 39)."

NOTE: For more information about hardware and cabling configurations, refer to the documents that ship with the server blade enclosure or diagnostic station.
Two methods are available for CD-ROM deployment:
• iLO virtual CD-ROM (on page 44)
• USB CD-ROM (on page 44)
iLO virtual CD-ROM
To deploy with a boot CD:
-
Do one of the following:
-
Insert the boot CD into the client PC that is using the iLO 2 Remote Console.
• Use iLO 2 to create an image file of the boot CD. -
Copy the image of the boot CD to a location on the network or the client PC hard drive.
-
Remotely access the server blade through iLO 2. Refer to "ProLiant p-Class Advanced management (on page 39)."
-
Click the Virtual Devices tab.
- Select Virtual Media.
- Use the Virtual Media applet to select the local CD or image file and connect the Virtual CD to the server blade.
- Use the iLO 2 Virtual Power Button feature to reboot the server blade.
- After the server blade boots, follow the normal network installation procedure for the OS.
USB CD-ROM
This method uses SmartStart to facilitate loading the OS. However, SmartStart also allows for manual loading of the OS and drivers.
To deploy with a boot CD:
- Use the local I/O cable to connect a USB CD-ROM drive to the server blade. Refer to "Connecting locally to a server blade with video and USB devices (on page 36)."
- Insert the boot CD into the USB CD-ROM drive.
- Reboot the server blade.
- After the server blade boots, follow the normal installation procedure for an OS.
Windows Server™ 2003 cannot be installed from a USB CD-ROM on the I/O cable if the hard drive is completely blank (no partitions defined). To install Windows Server™ 2003, use one of the following methods:
• Make a partition on the hard drive that Windows Server™ 2003 will be loaded on.
- Use the SmartStart CD 7.0 or higher.
• Use the Rapid Deployment pack.
Diskette image deployment
To deploy with a diskette image, the user creates a DOS-based network-enabled boot diskette that executes a script that configures the hardware and installs the OS. The diskette enables the server blade to access the required deployment scripts and files on the network.
This method implies a deployment infrastructure that may include an administrator workstation, PXE server, Microsoft® Windows® file share, or a Linux file share. For more information, refer to "Deployment infrastructure (on page 40)."
Before beginning the deployment process, connect the server blade to the network with one of the following methods:
- Through an existing network (in the rack)—For this method, install the server blade in its enclosure and assign it an IP address (manually or with DHCP).
- Through an existing network (out of the rack, with the diagnostic station)—For this method, power the server blade with the diagnostic station and connect to an existing network through a hub. The DHCP server on the network assigns the IP address.
Other methods for connecting to the server blade are available, but they do not provide the required network access for deployment. For more information, refer to "ProLiant p-Class Advanced management (on page 39)."

NOTE: For more information about hardware and cabling configurations, refer to the documents that ship with the server blade enclosure or diagnostic station.
Two methods are available for diskette image deployment:
• iLO virtual floppy (on page 45)
• PXE ("PXE deployment" on page 42)
Creating a boot diskette
The SmartStart Scripting Toolkit provides the tools and information for creating a boot diskette. For details, refer to the SmartStart Scripting Toolkit User Guide and download the latest version of the software from the HP website (http://www.hp.com/servers/sstoolkit).
As an alternative method, configure the hardware manually with RBSU and the iLO 2 remote console. With this method, the disk is more generic and integrates with an existing network OS installation process. For more information, refer to "ProLiant p-Class Advanced management (on page 39)."
To operate properly, the server blade must have a supported OS. For the latest information on a supported OS, refer to the HP website (http://www.hp.com/go/supportos).
iLO virtual floppy
To deploy with a boot diskette:
-
Do one of the following:
-
Insert the boot diskette into the client PC that is using the iLO 2 Remote Console.
• Use iLO 2 to create an image file of the boot diskette. -
Copy the image of the boot diskette to a location on the network or the client PC hard drive.
-
Remotely access the server blade through iLO 2. Refer to "ProLiant p-Class Advanced management (on page 39)."
-
Click the Virtual Devices tab.
- Select Virtual Media.
- Use the Virtual Media applet to select the local diskette or image file and connect the Virtual CD to the server blade.
- Use the iLO 2 Virtual Power Button feature to reboot the server blade.
- After the server blade boots, follow the normal network installation procedure for the OS.
SAN configuration
The server blade provides FC support for SAN implementations. This solution uses an optional FCA that offers redundant SAN connectivity and optimization for HP StorageWorks products. The server blade is also compatible with certain third-party SAN products. For more information, refer to the documentation that ships with the FCA option.
For optimal SAN connectivity, observe the following guidelines:
- The FCA option is installed correctly in the server blade. Refer to the documentation that ships with the FCA option.
-
An FC-compatible interconnect is installed in the enclosure. Refer to the documentation that ships with the interconnect option.
-
The server blade enclosure management module firmware is up-to-date. Refer to the HP Business Support Center website (http://www.hp.com/support).
• The server blade is cabled properly to a supported SAN.
• SAN storage drivers are loaded. Refer to supporting white papers and the HP website (http://www.hp.com/servers/rdp).
For SAN configuration information for the server blade, refer to the HP StorageWorks SAN Design Reference Guide on the HP website (http://h18000.www1.hp.com/products/storageworks/san/documentation.html).
Configuration tools
SmartStart software
SmartStart is a collection of software that optimizes single-server setup, providing a simple and consistent way to deploy server configuration. SmartStart has been tested on many ProLiant server products, resulting in proven, reliable configurations.
SmartStart assists the deployment process by performing a wide range of configuration activities, including:
- Configuring hardware using embedded configuration utilities, such as RBSU and ORCA
• Preparing the system for installing "off-the-shelf" versions of leading operating system software
• Installing optimized server drivers, management agents, and utilities automatically with every assisted installation - Testing server hardware using the Insight Diagnostics Utility ("HP Insight Diagnostics" on page 51)
• Installing software drivers directly from the CD. With systems that have internet connection, the SmartStart Autorun Menu provides access to a complete list of ProLiant system software. - Enabling access to the Array Configuration Utility (on page 48), Array Diagnostic Utility, and Erase Utility
SmartStart is included in the HP ProLiant Essentials Foundation Pack. For more information about SmartStart software, refer to the HP ProLiant Essentials Foundation Pack or the HP website (http://www.hp.com/servers/smartstart).
HP ROM-Based Setup Utility
RBSU, an embedded configuration utility, performs a wide range of configuration activities that may include:
- Configuring system devices and installed options
• Displaying system information - Selecting the primary boot controller
- Configuring memory options
- Language selection
For more information on RBSU, refer to the HP ROM-Based Setup Utility User Guide on the Documentation CD or the HP website (http://www.hp.com/servers/smartstart).
Using RBSU
The first time you power up the server blade, the system prompts you to enter RBSU and select a language. Default configuration settings are made at this time and can be changed later. Most of the features in RBSU are not required to set up the server blade.
To navigate RBSU, use the following keys:
- To access RBSU, press the F9 key during power up when prompted in the upper right corner of the screen.
• To navigate the menu system, use the arrow keys.
• To make selections, press the Enter key.

IMPORTANT: RBSU automatically saves settings when you press the Enter key. The utility does not prompt you for confirmation of settings before you exit the utility. To change a selected setting, you must select a different setting and press the Enter key.
Auto-configuration process
The auto-configuration process automatically runs when you boot the server for the first time. During the power-up sequence, the system ROM automatically configures the entire system without needing any intervention. During this process, the ORCA utility, in most cases, automatically configures the array to a default setting based on the number of drives connected to the server.

NOTE: The server may not support all the following examples.

NOTE: If the boot drive is not empty or has been written to in the past, ORCA does not automatically configure the array. You must run ORCA to configure the array settings.
| Drives installed Drives used RAID level | ||
| 1 | 1 | RAID |
| 2 | 2 | RAID |
| 3, 4, 5, or 6 3, 4, 5, or 6 RAID 5 | ||
| More than 6 0 None | ||
To change any ORCA default settings and override the auto-configuration process, press the F8 key when prompted.
By default, the auto-configuration process configures the system for the English language. To change any default settings in the auto-configuration process (such as the settings for language, operating system, and primary boot controller), execute RBSU by pressing the F9 key when prompted. After the settings are selected, exit RBSU and allow the server to reboot automatically.
For more information, refer to the HP ROM-Based Setup Utility User Guide on the Documentation CD or the HP website (http://www.hp.com/servers/smartstart).
Boot options
After the auto-configuration process completes, or after the server reboots upon exit from RBSU, the POST sequence runs, and then the boot option screen is displayed. This screen is visible for several seconds before the system attempts to boot from a diskette, CD, or hard drive. During this time, the menu on the screen allows you to install an operating system or make changes to the server configuration in RBSU.
BIOS Serial Console
BIOS Serial Console allows you to configure the serial port to view POST error messages and run RBSU remotely through a serial connection to the server COM port. The server that you are remotely configuring does not require a keyboard and mouse.
For more information about BIOS Serial Console, refer to the BIOS Serial Console User Guide on the Documentation CD or the HP website (http://www.hp.com/servers/smartstart).
Array Configuration Utility
ACU is a browser-based utility with the following features:
- Runs as a local application or remote service
• Supports online array capacity expansion, logical drive extension, assignment of online spares, and RAID or stripe size migration
• Suggests the optimum configuration for an unconfigured system - Provides different operating modes, enabling faster configuration or greater control over the configuration options
• Remains available any time that the server is on
• Displays on-screen tips for individual steps of a configuration procedure
For optimum performance, the minimum display settings are 800 × 600 resolution and 256 colors. Servers running Microsoft® operating systems require Internet Explorer 5.5 (with Service Pack 1) or later. For Linux servers, refer to the README.TXT file for additional browser and support information.
For more information, refer to the HP Array Configuration Utility User Guide on the Documentation CD or the HP website (http://www.hp.com).
Option ROM Configuration for Arrays
Before installing an operating system, you can use the ORCA utility to create the first logical drive, assign RAID levels, and establish online spare configurations.
The utility also provides support for the following functions:
• Reconfiguring one or more logical drives
• Viewing the current logical drive configuration
- Deleting a logical drive configuration
- Setting the controller to be the boot controller
If you do not use the utility, ORCA will default to the standard configuration.
For more information regarding array controller configuration, refer to the controller user guide.
For more information regarding the default configurations that ORCA uses, refer to the HP ROM-Based Setup Utility User Guide on the Documentation CD.
Re-entering the server serial number and product ID
After you replace the system board, you must re-enter the server serial number and the product ID.
- During the server startup sequence, press the F9 key to access RBSU.
- Select the System Options menu.
- Select Serial Number. The following warning is displayed:
WARNING! WARNING! WARNING! The serial number is loaded into the system during the manufacturing process and should NOT be modified. This option
should only be used by qualified service personnel. This value should always match the serial number sticker located on the chassis.
- Press the Enter key to clear the warning.
- Enter the serial number and press the Enter key.
- Select Product ID.
- Enter the product ID and press the Enter key.
- Press the Esc key to close the menu.
- Press the Esc key to exit RBSU.
- Press the F10 key to confirm exiting RBSU. The server will automatically reboot.
Management tools
Automatic Server Recovery
ASR is a feature that causes the system to restart when a catastrophic operating system error occurs, such as a blue screen, ABEND, or panic. A system fail-safe timer, the ASR timer, starts when the System Management driver, also known as the Health Driver, is loaded. When the operating system is functioning properly, the system periodically resets the timer. However, when the operating system fails, the timer expires and restarts the server.
ASR increases server availability by restarting the server within a specified time after a system hang or shutdown. At the same time, the HP SIM console notifies you by sending a message to a designated pager number that ASR has restarted the system. You can disable ASR from the HP SIM console or through RBSU.
ROMPaq utility
Flash ROM enables you to upgrade the firmware (BIOS) with system or option ROMPaq utilities. To upgrade the BIOS, insert a ROMPaq diskette into the diskette drive and boot the system.
The ROMPaq utility checks the system and provides a choice (if more than one exists) of available ROM revisions. This procedure is the same for both system and option ROMPaq utilities.
For more information about the ROMPaq utility, refer to the HP website (http://www.hp.com/servers/manage).
Integrated Lights-Out 2 technology
The iLO 2 subsystem is a standard component of selected ProLiant servers that provides server health and remote server manageability. The iLO 2 subsystem includes an intelligent microprocessor, secure memory, and a dedicated network interface. This design makes iLO 2 independent of the host server and its operating system. The iLO 2 subsystem provides remote access to any authorized network client, sends alerts, and provides other server management functions.
Using iLO 2, you can:
• Remotely power up, power down, or reboot the host server.
- Send alerts from iLO 2 regardless of the state of the host server.
- Access advanced troubleshooting features through the iLO 2 interface.
• Diagnose iLO 2 using HP SIM through a web browser and SNMP alerting.
For more information about iLO 2 features, refer to the iLO 2 documentation on the Documentation CD or on the HP website (http://www.hp.com/servers/lights-out).
HP Systems Insight Manager
HP SIM is a web-based application that allows system administrators to accomplish normal administrative tasks from any remote location, using a web browser. HP SIM provides device management capabilities that consolidate and integrate management data from HP and third-party devices.

IMPORTANT: You must install and use HP SIM to benefit from the Pre-Failure Warranty for processors, SAS and SCSI hard drives, and memory modules.
For additional information, refer to the Management CD in the HP ProLiant Essentials Foundation Pack or the HP SIM website (http://www.hp.com/go/hpsim).
Management Agents
Management Agents provide the information to enable fault, performance, and configuration management. The agents allow easy manageability of the server through HP SIM software, and third-party SNMP management platforms. Management Agents are installed with every SmartStart assisted installation or can be installed through the HP PSP. The Systems Management homepage provides status and direct access to in-depth subsystem information by accessing data reported through the Management Agents. For additional information, refer to the Management CD in the HP ProLiant Essentials Foundation Pack or the HP website (http://www.hp.com/servers/manage).
Redundant ROM support
The server enables you to upgrade or configure the ROM safely with redundant ROM support. The server has a 4-MB ROM that acts as two, separate 2-MB ROMs. In the standard implementation, one side of the ROM contains the current ROM program version, while the other side of the ROM contains a backup version.

NOTE: The server ships with the same version programmed on each side of the ROM.
Safety and security benefits
When you flash the system ROM, ROMPaq writes over the backup ROM and saves the current ROM as a backup, enabling you to switch easily to the alternate ROM version if the new ROM becomes corrupted for any reason. This feature protects the existing ROM version, even if you experience a power failure while flashing the ROM.
USB support
HP provides both standard USB support and legacy USB support. Standard support is provided by the OS through the appropriate USB device drivers. Before the OS loads, HP provides support for USB devices through legacy USB support, which is enabled by default in the system ROM. HP hardware supports USB version 1.1 or 2.0, depending on the version of the hardware.
Legacy USB support provides USB functionality in environments where USB support is normally not available. Specifically, HP provides legacy USB functionality for:
POST
• RBSU
• Diagnostics
• DOS
• Operating environments which do not provide native USB support
For more information on ProLiant USB support, refer to the HP website (http://h18004.www1.hp.com/products/servers/platforms/usb-support.html).
Diagnostic tools
HP Insight Diagnostics
HP Insight Diagnostics is a proactive server blade management tool, available in both offline and online versions, that provides diagnostics and troubleshooting capabilities to assist IT administrators who verify server blade installations, troubleshoot problems, and perform repair validation.
HP Insight Diagnostics Offline Edition performs various in-depth system and component testing while the OS is not running. To run this utility, launch the SmartStart CD.
HP Insight Diagnostics Online Edition is a web-based application that captures system configuration and other related data needed for effective server blade management. Available in Microsoft® Windows® and Linux versions, the utility helps to ensure proper system operation.
For more information or to download the utility, refer to the HP website (http://www.hp.com/servers/diags).
Survey Utility
Survey Utility, a feature within HP Insight Diagnostics (on page 51), gathers critical hardware and software information on ProLiant server blades.
This utility supports operating systems that may not be supported by the server blade. For operating systems supported by the server blade, refer to the HP website (http://www.hp.com/go/supportos).
If a significant change occurs between data-gathering intervals, the Survey Utility marks the previous information and overwrites the Survey text files to reflect the latest changes in the configuration.
Survey Utility is installed with every SmartStart-assisted installation or can be installed through the HP PSP ("ProLiant Support Packs" on page 53).

NOTE: SmartStart version 7.5 and later provides the memory spare part numbers for the server.
Integrated Management Log
The IML records hundreds of events and stores them in an easy-to-view form. The IML timestamps each event with 1-minute granularity.
You can view recorded events in the IML in several ways, including the following:
• From within Survey Utility (on page 51)
• From within operating system-specific IML viewers
• For NetWare: IML Viewer
- For Windows®: IML Viewer
• For Linux: IML Viewer Application
• From within HP SIM ("HP Systems Insight Manager" on page 50)
• From within the iLO 2 user interface
• From within HP Insight Diagnostics (on page 51)
For more information, refer to the Management CD in the HP ProLiant Essentials Foundation Pack.
Remote support and analysis tools
HP Instant Support Enterprise Edition
ISEE is a proactive remote monitoring and diagnostic tool to help manage your systems and devices, a feature of HP support. ISEE provides continuous hardware event monitoring and automated notification to identify and prevent potential critical problems. Through remote diagnostic scripts and vital system configuration information collected about your systems, ISEE enables fast restoration of your systems. Install ISEE on your systems to help mitigate risk and prevent potential critical problems.
For more information on ISEE, refer to the HP website (http://www.hp.com/hps/hardware/hw_enterprise.html).
To download HP ISEE, visit the HP website (http://www.hp.com/hps/hardware/hw_downloads.html).
For installation information, refer to the HP ISEE Client Installation and Upgrade Guide (ftp://ftp.hp.com/pub/services/hardware/info/isee_client.pdf).
Web-Based Enterprise Service
WEBES enables administrators to manage hardware events proactively, either locally or online. The service provides real-time multiple event analysis, crash analysis, and notification, locally through SMTP and remotely through ISEE for OpenVMS, Tru64, and Microsoft® Windows® operating system binary error logs.
For more information, refer to the HP website (http://h18000.www1.hp.com/support/svctools/).
Open Services Event Manager
OSEM is a standalone tool that performs real-time reactive and proactive service event filtering, analysis, and notification. The tool gathers event data from SNMP traps or information provided over an HTTP interface and notifies an administrator or HP through SMTP and ISEE.
For more information, refer to the HP website (http://h18000.www1.hp.com/support/svctools/).
Keeping the system current
Drivers
The server includes new hardware that may not have driver support on all operating system installation media.
If you are installing a SmartStart-supported operating system, use the SmartStart software (on page 46) and its Assisted Path feature to install the operating system and latest driver support.

NOTE: If you are installing drivers from the SmartStart CD or the Software Maintenance CD, refer to the SmartStart website (http://www.hp.com/servers/smartstart) to be sure that you are using the latest version of SmartStart. For more information, refer to the documentation provided with the SmartStart CD.
If you do not use the SmartStart CD to install an operating system, drivers for some of the new hardware are required. These drivers, as well as other option drivers, ROM images, and value-add software can be downloaded from the HP website (http://www.hp.com/support).

IMPORTANT: Always perform a backup before installing or updating device drivers.
Resource Paqs
Resource Paqs are operating system-specific packages of tools, utilities, and information for HP servers running certain Microsoft® or Novell operating systems. The Resource Paqs include utilities to monitor performance, software drivers, customer support information, and white papers on the latest server integration information. Refer to the Enterprise Partnerships website
(http://h18000.www1.hp.com/partners), select Microsoft or Novell, depending on the operating system, and follow the link to the appropriate Resource Paq.
ProLiant Support Packs
PSPs represent operating system-specific bundles of ProLiant optimized drivers, utilities, and management agents. Refer to the PSP website
(http://h18000.www1.hp.com/products/servers/management/psp.html).
Operating system version support
Refer to the operating system support matrix (http://www.hp.com/go/supportos).
System online ROM flash component utility
The Online ROM Flash Component Utility enables system administrators to efficiently upgrade system or controller ROM images across a wide range of servers and array controllers. This tool has the following features:
• Works offline and online
• Supports Microsoft®, Windows® 2000, Windows Server™ 2003, Novell Netware, and Linux operating systems

IMPORTANT: This utility supports operating systems that may not be supported by the server. For operating systems supported by the server, refer to the HP website (http://www.hp.com/go/supportos).
• Integrates with other software maintenance, deployment, and operating system tools
• Automatically checks for hardware, firmware, and operating system dependencies, and installs only the correct ROM upgrades required by each target server
To download the tool and for more information, refer to the HP website (http://h18000.www1.hp.com/support/files/index.html).
Change control and proactive notification
HP offers Change Control and Proactive Notification to notify customers 30 to 60 days in advance of upcoming hardware and software changes on HP commercial products.
For more information, refer to the HP website (http://h18023.www1.hp.com/solutions/pcsolutions/pcn.html).
Natural language search assistant
The natural language search assistant (http://www.hp.com/support/natural_language_search) is a search engine that finds information on HP products, including ProLiant servers. The search engine responds to queries entered in question form.
Care Pack
HP Care Pack Services offer upgraded service levels to extend and expand standard product warranty with easy-to-buy, easy-to-use support packages that help you make the most of your server investments. Refer to the Care Pack website (http://www.hp.com/hps/carepack/servers/cp_proliant.html).
Troubleshooting
In this section
Troubleshooting resources 55
Pre-diagnostic steps 55
Service notifications....58
Loose connections 58
Troubleshooting flowcharts 59
POST error messages and beep codes....70
Troubleshooting resources

NOTE: For common troubleshooting procedures, the term "server" is used to mean servers and server blades.
The HP ProLiant Servers Troubleshooting Guide provides simple procedures for resolving common problems as well as a comprehensive course of action for fault isolation and identification, error message interpretation, issue resolution, and software maintenance.
To obtain the guide, refer to any of the following sources and then select the HP ProLiant Servers Troubleshooting Guide:
• The server-specific Documentation CD
- The Business Support Center on the HP website (http://www.hp.com/support). Navigate to the server technical support page. Under self-help resources, select ProLiant Troubleshooting Guide.
- The Technical Documentation website (http://www.docs.hp.com). Select Enterprise Servers, Workstations and Systems Hardware, and then the appropriate server.
Pre-diagnostic steps

WARNING: To avoid potential problems, ALWAYS read the warnings and cautionary information in the server documentation before removing, replacing, reseating, or modifying system components.

IMPORTANT: This guide provides information for multiple servers. Some information may not apply to the server you are troubleshooting. Refer to the server documentation for information on procedures, hardware options, software tools, and operating systems supported by the server.
- Review the important safety information (on page 56).
- Gather symptom information (on page 57).
- Prepare the server for diagnosis (on page 58).
- Use the Start diagnosis flowchart (on page 59) to begin the diagnostic process.
Important safety information
Familiarize yourself with the safety information in the following sections before troubleshooting the server.

Important safety information
Before servicing this product, read the Important Safety Information document provided with the server.
Symbols on equipment
The following symbols may be placed on equipment to indicate the presence of potentially hazardous conditions.

This symbol indicates the presence of hazardous energy circuits or electric shock hazards. Refer all servicing to qualified personnel.
WARNING: To reduce the risk of injury from electric shock hazards, do not open this enclosure. Refer all maintenance, upgrades, and servicing to qualified personnel.

This symbol indicates the presence of electric shock hazards. The area contains no user or field serviceable parts. Do not open for any reason.
WARNING: To reduce the risk of injury from electric shock hazards, do not open this enclosure.

This symbol on an RJ-45 receptacle indicates a network interface connection.
WARNING: To reduce the risk of electric shock, fire, or damage to the equipment, do not plug telephone or telecommunications connectors into this receptacle.

This symbol indicates the presence of a hot surface or hot component. If this surface is contacted, the potential for injury exists.
WARNING: To reduce the risk of injury from a hot component, allow the surface to cool before touching.

This symbol indicates that the component exceeds the recommended weight for one individual to handle safely.
9.43 kg
WARNING: To reduce the risk of personal injury or damage to the equipment, observe local occupational health and safety requirements and guidelines for manual material handling.
20.08 lb

These symbols, on power supplies or systems, indicate that the equipment is supplied by multiple sources of power.
WARNING: To reduce the risk of injury from electric shock, remove all power cords to completely disconnect power from the system.
Warnings and cautions

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:
• The leveling feet are extended to the floor.
• The full weight of the rack rests on the leveling feet.
- The stabilizing feet are attached to the rack if it is a single-rack installation.
- The racks are coupled 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.
⚠ WARNING: To reduce the risk of electric shock or damage to the equipment:
- Do not disable the power cord grounding plug. The grounding plug is an important safety feature.
- Plug the power cord into a grounded (earthed) electrical outlet that is easily accessible at all times.
- Unplug the power cord from the power supply to disconnect power to the equipment.
- Do not route the power cord where it can be walked on or pinched by items placed against it. Pay particular attention to the plug, electrical outlet, and the point where the cord extends from the server.

9.43 kg
20.08 lb
WARNING: To reduce the risk of personal injury or damage to the equipment:
- Observe local occupation health and safety requirements and guidelines for manual handling.
- Obtain adequate assistance to lift and stabilize the chassis during installation or removal.
- The server is unstable when not fastened to the rails.
- When mounting the server in a rack, remove the power supplies and any other removable module to reduce the overall weight of the product.
△ CAUTION: To properly ventilate the system, you must provide at least 7.6 cm (3.0 in) of clearance at the front and back of the server.
△ CAUTION: The server is designed to be electrically grounded (earthed). To ensure proper operation, plug the AC power cord into a properly grounded AC outlet only.
Symptom information
Before troubleshooting a server problem, collect the following information:
• What events preceded the failure? After which steps does the problem occur?
• What has been changed since the time the server was working?
- Did you recently add or remove hardware or software? If so, did you remember to change the appropriate settings in the server setup utility, if necessary?
• 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 51) and use the survey page to view the current configuration or to compare it to previous configurations.
• Refer to your hardware and software records for information.
• Refer to server LEDs and their statuses.
Prepare the server for diagnosis
- Be sure the server is in the proper operating environment with adequate power, air conditioning, and humidity control. Refer to the server documentation for required environmental conditions.
- Record any error messages displayed by the system.
- Remove all diskettes and CDs from the media drives.
- Power down the server and peripheral devices if you will be diagnosing the server offline. Always perform an orderly shutdown, if possible. This means you must:
a. Exit any applications.
b. Exit the operating system.
c. Power down the server.
- 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.
- Collect all tools and utilities, such as a Torx screwdriver, loopback adapters, ESD wrist strap, and software utilities, necessary to troubleshoot the problem.
• You must have the appropriate Health Drivers and Management Agents installed on the server.

NOTE: To verify the server configuration, connect to the System Management homepage and select Version Control Agent. The VCA gives you a list of names and versions of all installed HP drivers, Management Agents, and utilities, and whether they are up to date.
- HP recommends you have access to the SmartStart CD for value-added software and drivers required during the troubleshooting process.
• HP recommends you have access to the server documentation for server-specific information.
Service notifications
To view the latest service notifications, refer to the HP website (http://www.hp.com/go/bizsupport). Select the appropriate server model, and then click the Troubleshoot a Problem link on the product page.
Loose connections
Action:
- Be sure all power cords are securely connected.
- Be sure all cables are properly aligned and securely connected for all external and internal components.
- Remove and check all data and power cables for damage. Be sure no cables have bent pins or damaged connectors.
- If a fixed cable tray is available for the server, be sure the cords and cables connected to the server are correctly routed through the tray.
-
Be sure each device is properly seated.
• If a device has latches, be sure they are completely closed and locked. -
Check any interlock or interconnect LEDs that may indicate a component is not connected properly.
- If problems continue to occur, remove and reinstall each device, checking the connectors and sockets for bent pins or other damage.
Troubleshooting flowcharts
To effectively troubleshoot a problem, HP recommends that you start with the first flowchart in this section, "Start diagnosis flowchart (on page 59)," and follow the appropriate diagnostic path. If the other flowcharts do not provide a troubleshooting solution, follow the diagnostic steps in "General diagnosis flowchart (on page 60)." The General diagnosis flowchart is a generic troubleshooting process to be used when the problem is not server-specific or is not easily categorized into the other flowcharts.
The available flowcharts include:
• Start diagnosis flowchart (on page 59)
• General diagnosis flowchart (on page 60)
• Server blade power-on problems flowchart (on page 62)
• POST problems flowchart (on page 64)
• OS boot problems flowchart (on page 66)
• Server fault indications flowchart (on page 68)
Start diagnosis flowchart
Use the following flowchart to start the diagnostic process.
| Item | Refer to |
| 1 "General diagnosis flowchart (on page 60)" | |
| 2 | "Power-on problems flowchart ("Server blade power-on problems flowchart" on page 62)" |
| 3 "POST problems flowchart (on page 64)" | |
| 4 "OS boot problems flowchart (on page 66)" | |
| 5 | "Server fault indications flowchart (on page 68)" |
![graph TD A["Start diagnosis"] --> B{Do you want to perform the General Diagnosis?} B -->|Yes| C["(1) Go to General diagnosis"] B -->|No| D{Does server power on?} D -->|No| E["(2) Go to Power-on problems"] D -->|Yes| F{Does server complete POST OK?} F -->|No| G["(3) Go to POST problems"] F -->|Yes| H…](/content/2026/07/1524157/images/d6a934e6754b5636cceff5ed5a1c4ad432302beb8a6d8eac1672b6ce6decc370.jpg)
General diagnosis flowchart
The General diagnosis flowchart provides a generic approach to troubleshooting. If you are unsure of the problem, or if the other flowcharts do not fix the problem, use the following flowchart.
| Item | Refer to |
| 1 "Symptom information (on page 57)" | |
| 2 "Loose connections (on page 58)" | |
| 3 "Service notifications (on page 58)" | |
| 4 | The most recent version of a particular server or option firmware is available on the following websites:HP Support website (http://www.hp.com/support)HP ROM-BIOS/Firmware Updates website (http://h18023. www1.hp.com/support/files/server/us/romflash.html) |
| 5 | "General memory problems are occurring" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support) |
| 6 | Server maintenance and service guide, located on the Documentation CD or the HP website (http://www.hp.com/products/servers/proliant-bl/p-class/info) |
| 7 | Server maintenance and service guide, located on the Documentation CD or the HP website (http://www.hp.com/products/servers/proliant-bl/p-class/info)"Hardware problems" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support) |
| 8 | "Server information you need" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support)"Operating system information you need" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support) |
| 9 "HP contact information (on page 80)" | |
![graph TD A["Start General diagnosis"] --> B["(1) Record symptom information."] B --> C["Reboot server to see if condition still exists."] C --> D{Is this a newly installed server?} D -->|Yes| E["(2) Reseat any components that may have come loose during shipping and reboot the server."] D -->|No| F{W…](/content/2026/07/1524157/images/0be6ece7bbbfea653f385124e560a1ef9f8adcca773d7ea04c1b9184f4037e66.jpg)
Server blade power-on problems flowchart
Symptoms:
• The server does not power on.
• The system power LED is off or amber.
• The health LED is red or amber.
Possible causes:
- Improperly seated or faulty power supply
- Loose or faulty power cord
• Power source problem
• Power on circuit problem
• Improperly seated component or interlock problem - Faulty internal component
| Item | Refer to |
| 1 "Component identification (on page 6)" | |
| 2 "General diagnosis flowchart (on page 60)" | |
| 3 "Loose connections (on page 58)" | |
| 4 | Power Calculator on the HP website(http://www.hp.com/go/bladesystem/powercalculator) |
| 5 | HP BladeSystem Maintenance and Service Guide located on the HP website (http://www.hp.com/products/servers/proliant-bl/p-class/info) |
| 6 | Integrated Lights-Out User Guide located on the HP website(http://www.hp.com/products/servers/proliant-bl/p-class/info) |
| 7 | Server maintenance and service guide located on the HP website(http://www.hp.com/products/servers/proliant-bl/p-class/info) |
![graph TD A["Start"] --> B{Does the server automatically power on?} B -->|Yes| C["End"] B -->|No| D{Is the power switch on the power enclosure, server blade enclosure, and bus bars on?} D -->|Yes| E["Replace or troubleshoot the blade system infrastructure components."] D -->|No| F{Are any server blad…](/content/2026/07/1524157/images/2092322e020e4160413d82a230b32c1403b33f516687af62a749b388db0b5bc5.jpg)
POST problems flowchart
Symptoms:
• Server does not complete POST

NOTE: The server has completed POST when the system attempts to access the boot device.
• Server completes POST with errors
Possible Problems:
- Improperly seated or faulty internal component
- Faulty KVM device
- Faulty video device
| Item | Refer to |
| 1 "POST error messages and beep codes" | |
| 2 | "Video problems" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support) |
| 3 KVM or iLO 2 documentation | |
| 4 "Loose connections (on page 58)" | |
| 5 "Symptom information (on page 57)" | |
| 6 | Server maintenance and service guide, located on the Documentation CD or the HP website (http://www.hp.com/products/servers/proliant-bl/p-class/info) |
| 7 | "Port 85 and iLO messages" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support) |
| 8 | "General memory problems are occurring" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support) |
| 9 | • "Hardware problems" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support)• Server maintenance and service guide, located on the Documentation CD or the HP website (http://www.hp.com/products/servers/proliant-bl/p-class/info) |
| 10 | • "Server information you need" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support)• "Operating system information you need" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support) |
![graph TD A["Start POST Problems"] --> B{Have video output?} B -->|No| C["(2) Verify video is cabled correctly."] B -->|Yes| D{POST errors messages displayed?} D -->|No| E{Are the fans on?} D -->|Yes| F["(1) Refer to "Post Error Messages.""] E -->|No| G{Are there any beep codes?} E -->|Yes|…](/content/2026/07/1524157/images/739bfa352480fa3413d3d5c984992af5a170de861c447939894924cbf8da656f.jpg)
OS boot problems flowchart
Symptoms:
• Server does not boot a previously installed OS
• Server does not boot SmartStart
Possible causes:
- Corrupted OS
• Hard drive subsystem problem
• Incorrect boot order setting in RBSU
| Item | Refer to |
| 1 | HP ROM-Based Setup Utility User Guide(http://www.hp.com/servers/smartstart) |
| 2 "POST problems flowchart (on page 64)" | |
| 3 | "Hard drive problems" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support)Controller documentation |
| 4 | "HP Insight Diagnostics (on page 51)" or in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support) |
| 5 | "Loose connections (on page 58)""CD-ROM and DVD drive problems" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support)Controller documentation |
| 6 | "General memory problems are occurring" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support) |
| 7 | "Operating system problems" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support)"HP contact information (on page 80)" |
| 8 | "Hardware problems" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support)Server maintenance and service guide located on the Documentation CD or the HP website (http://www.hp.com/products/servers/proliant-bl/p-class/info) |
| 9 "General diagnosis flowchart (on page 60)" | |
![graph TD A["Start OS boot problems"] --> B{Does the server boot SmartStart CD?} B -->|No| C["(1) Disable Fast Boot in RBSU and check server boot order."] C --> D{Does server still boot with errors?} D -->|Yes| E["(2) Go to POST Problems"] D -->|No| F{Does server still fail to boot SmartStart?} F -->…](/content/2026/07/1524157/images/a745e6a8ff2ed01f49bf5a755878f5850ed150cbb69852e0913069944da72537.jpg)
Server fault indications flowchart
Symptoms:
• Server boots, but a fault event is reported by Insight Management Agents (on page 50)
• Server boots, but the internal health LED, external health LED, or component health LED is red or amber

NOTE: For the location of server LEDs and information on their statuses, refer to the server documentation.
Possible causes:
• Improperly seated or faulty internal or external component
• Unsupported component installed
- Redundancy failure
• System overtemperature condition
| Item | Refer to |
| 1 | "Management agents (on page 50)" or in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support) |
| 2 | • "Integrated Management Log" or in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support)• "Event list error messages" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support) |
| 3 "Component identification (on page 6)" | |
| 4 System | Management Homepage (https://localhost:2381) |
| 5 | "Power-on problems flowchart ("Server blade power-on problems flowchart" on page 62)" |
| 6 | • "Smart Array SCSI Diagnosis feature" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support)• Server maintenance and service guide, located on the Documentation CD or the HP website (http://www.hp.com/products/servers/proliant-bl/p-class/info)• "HP contact information (on page 80)" |
| 7 | "HP Insight Diagnostics (on page 51)" or in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support) |
| 8 | • "Hardware problems" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support)• Server maintenance and service guide, located on the Documentation CD or the HP website (http://www.hp.com/products/servers/proliant-bl/p-class/info) |
![graph TD A["Start Server fault indications"] --> B["Select an appropriate fault indicator."] B --> C{(1) Insight Management Agents} C --> D{Was event reported by Insight Management Agents?} D -->|No| E{Is there an IML entry identifying the problem?} D -->|Yes| F{(4) Gather information from the Syste…](/content/2026/07/1524157/images/805a1008ea08700ac859a1880b81ddaa59490a5734b0e30d38e08d24101a90f8.jpg)
POST error messages and beep codes
For a complete listing of error messages, refer to the "POST error messages" in the HP ProLiant Servers Troubleshooting Guide located on the Documentation CD or on the HP website (http://www.hp.com/support).

WARNING: To avoid potential problems, ALWAYS read the warnings and cautionary information in the server documentation before removing, replacing, reseating, or modifying system components.
Battery replacement
If the server blade no longer automatically displays the correct date and time, you may need to replace the battery that provides power to the real-time clock. Under normal use, battery life is 5 to 10 years.

WARNING: The computer contains an internal lithium manganese dioxide, a vanadium pentoxide, or an alkaline battery pack. A risk of fire and burns exists if the battery pack is not properly handled. To reduce the risk of personal injury:
• Do not attempt to recharge the battery.
- Do not expose the battery to temperatures higher than 60°C (140°F).
- Do not disassemble, crush, puncture, short external contacts, or dispose of in fire or water.
- Replace only with the spare designated for this product.
To remove the component:
- Power down the server blade (on page 15).
- Remove the server blade (on page 16).
- Remove the access panel (on page 16).
- Identify the battery location.
- Remove the battery.


IMPORTANT: Replacing the system board battery resets the system ROM to its default configuration. After replacing the battery, reconfigure the system through RBSU.
To replace the component, reverse the removal procedure.
For more information about battery replacement or proper disposal, contact an authorized reseller or an authorized service provider.
Regulatory compliance notices
In this section
Regulatory compliance identification numbers....72
Federal Communications Commission notice 72
Declaration of conformity for products marked with the FCC logo, United States only....73
Cables 74
Modifications....74
European Union regulatory notice 74
Disposal of waste equipment by users in private households in the European Union 74
Canadian notice (Avis Canadien) 75
Japanese notice 75
BSMI notice 75
Korean notice 76
Battery replacement notice 76
Taiwan battery recycling notice....76
Regulatory compliance identification numbers
For the purpose of regulatory compliance certifications and identification, this product has been assigned a unique regulatory model number. The regulatory model number can be found on the product nameplate label, along with all required approval markings and information. When requesting compliance information for this product, always refer to this regulatory model number. The regulatory model number is not the marketing name or model number of the product.
Federal Communications Commission notice
Part 15 of the Federal Communications Commission (FCC) Rules and Regulations has established Radio Frequency (RF) emission limits to provide an interference-free radio frequency spectrum. Many electronic devices, including computers, generate RF energy incidental to their intended function and are, therefore, covered by these rules. These rules place computers and related peripheral devices into two classes, A and B, depending upon their intended installation. Class A devices are those that may reasonably be expected to be installed in a business or commercial environment. Class B devices are those that may reasonably be expected to be installed in a residential environment (for example, personal computers). The FCC requires devices in both classes to bear a label indicating the interference potential of the device as well as additional operating instructions for the user.
FCC rating label
The FCC rating label on the device shows the classification (A or B) of the equipment. Class B devices have an FCC logo or ID on the label. Class A devices do not have an FCC logo or ID on the label. After you determine the class of the device, refer to the corresponding statement.
Class A equipment
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at personal expense.
Class B equipment
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
- Reorient or relocate the receiving antenna.
- Increase the separation between the equipment and receiver.
- Connect the equipment into an outlet on a circuit that is different from that to which the receiver is connected.
- Consult the dealer or an experienced radio or television technician for help.
Declaration of conformity for products marked with the FCC logo, United States only
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
For questions regarding this product, contact us by mail or telephone:
• Hewlett-Packard Company
P. O. Box 692000, Mail Stop 530113
Houston, Texas 77269-2000
- 1-800-HP-INVENT (1-800-474-6836). (For continuous quality improvement, calls may be recorded or monitored.)
For questions regarding this FCC declaration, contact us by mail or telephone:
• Hewlett-Packard Company
P. O. Box 692000, Mail Stop 510101
Houston, Texas 77269-2000
1-281-514-3333
To identify this product, refer to the part, series, or model number found on the product.
Cables
Connections to this device must be made with shielded cables with metallic RFI/EMI connector hoods in order to maintain compliance with FCC Rules and Regulations.
Modifications
The FCC requires the user to be notified that any changes or modifications made to this device that are not expressly approved by Hewlett-Packard Company may void the user's authority to operate the equipment.
European Union regulatory notice
This product complies with the following EU Directives:
• Low Voltage Directive 73/23/EEC
• EMC Directive 89/336/EEC
Compliance with these directives implies conformity to applicable harmonized European standards (European Norms) which are listed on the EU Declaration of Conformity issued by Hewlett-Packard for this product or product family.
This compliance is indicated by the following conformity marking placed on the product:

This marking is valid for non-Telecom products and EU harmonized Telecom products (e.g. Bluetooth).

This marking is valid for EU non-harmonized Telecom products.
*Notified body number (used only if applicable—refer to the product label)
Disposal of waste equipment by users in private households in the European Union

This symbol on the product or on its packaging indicates that this product must not be disposed of with your other household waste. Instead, it is your responsibility to dispose of your waste equipment by handing it over to a designated collection point for the recycling of waste electrical and electronic equipment. The separate collection and recycling of your waste equipment at the time of disposal will help to conserve natural resources and ensure that it is recycled in a manner that protects human health and the environment. For more information about where you can drop off your waste equipment for recycling, please contact your local city office, your household waste disposal service or the shop where you purchased the product.
Canadian notice (Avis Canadien)
Class A equipment
This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations.
This Class B digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations.
Battery replacement notice
WARNING: The computer contains an internal lithium manganese dioxide, a vanadium pentoxide, or an alkaline battery pack. A risk of fire and burns exists if the battery pack is not properly handled. To reduce the risk of personal injury:
• Do not attempt to recharge the battery.
- Do not expose the battery to temperatures higher than 60°C (140°F).
- Do not disassemble, crush, puncture, short external contacts, or dispose of in fire or water.

Batteries, battery packs, and accumulators should not be disposed of together with the general household waste. To forward them to recycling or proper disposal, please use the public collection system or return them to HP, an authorized HP Partner, or their agents.
For more information about battery replacement or proper disposal, contact an authorized reseller or an authorized service provider.
Taiwan battery recycling notice
The Taiwan EPA requires dry battery manufacturing or importing firms in accordance with Article 15 of the Waste Disposal Act to indicate the recovery marks on the batteries used in sales, giveaway or promotion. Contact a qualified Taiwanese recycler for proper battery disposal.

廢電池請回收
Electrostatic discharge
In this section
Preventing electrostatic discharge....78
Grounding methods to prevent electrostatic discharge 78
Preventing electrostatic discharge
To prevent damaging the system, be aware of the precautions you need to follow when setting up the system or handling parts. A discharge of static electricity from a finger or other conductor may damage system boards or other static-sensitive devices. This type of damage may reduce the life expectancy of the device.
To prevent electrostatic damage:
- Avoid hand contact by transporting and storing products in static-safe containers.
- Keep electrostatic-sensitive parts in their containers until they arrive at static-free workstations.
- Place parts on a grounded surface before removing them from their containers.
- Avoid touching pins, leads, or circuitry.
• Always be properly grounded when touching a static-sensitive component or assembly.
Grounding methods to prevent electrostatic discharge
Several methods are used for grounding. Use one or more of the following methods when handling or installing electrostatic-sensitive parts:
- Use a wrist strap connected by a ground cord to a grounded workstation or computer chassis. Wrist straps are flexible straps with a minimum of 1 megohm ±10 percent resistance in the ground cords. To provide proper ground, wear the strap snug against the skin.
- Use heel straps, toe straps, or boot straps at standing workstations. Wear the straps on both feet when standing on conductive floors or dissipating floor mats.
- Use conductive field service tools.
• Use a portable field service kit with a folding static-dissipating work mat.
If you do not have any of the suggested equipment for proper grounding, have an authorized reseller install the part.
For more information on static electricity or assistance with product installation, contact an authorized reseller.
Specifications
In this section
Environmental specifications....79
Server specifications....79
Environmental specifications
| Specification Value | |
| Temperature range* | |
| Operating | 10°C to 35°C (50°F to 95°F) |
| Shipping | -40°C to 60°C (-40°F to 140°F) |
| Storage -20°C to 60°C (-4 to 140°C) | |
| Maximum wet bulb temperature | 30°C (86°F) |
| Relative humidity (noncondensing)** | |
| Operating 10% to 90% | |
| Shipping 10% to 90% | |
| Storage 10% to 95% | |
* All temperature ratings shown are for sea level. An altitude derating of 1°C per 304.8 m (1.8°F per 1,000 ft) to 3048 m (10,000 ft) is applicable. No direct sunlight allowed. Upper operating limit is 3,048m (10,000 ft) or 70 Kpa/10.1 psia. Upper non-operating limit is 9,144 m (30,000 ft) or 30.3 KPa/4.4 psia.
** Storage maximum humidity of 95% is based on a maximum temperature of 45°C (113°F). Altitude maximum for storage corresponds to a pressure minimum of 70 KPa.
Server specifications
| Specification | Value |
| Height 4.29 cm (1.69 in) | |
| Depth 71.1 cm (28.00 in) | |
| Width 26.14 cm (10.29 in) | |
| Weight (maximum) 9.43 kg (20.8 lb) | |
Technical support
In this section
Before you contact HP....80
HP contact information....80
Customer Self Repair 80
Before you contact HP
Be sure to have the following information available before you call HP:
• Technical support registration number (if applicable)
• Product serial number
• Product model name and number
• Applicable error messages
- Add-on boards or hardware
• Third-party hardware or software
- Operating system type and revision level
HP contact information
For the name of the nearest HP authorized reseller:
• In the United States, see the HP US service locator webpage (http://www.hp.com/service_locator).
- In other locations, see the Contact HP worldwide (in English) webpage (http://welcome.hp.com/country/us/en/wwcontact.html).
For HP technical support:
• In the United States, for contact options see the Contact HP United States webpage (http://welcome.hp.com/country/us/en/contact_us.html). To contact HP by phone:
- Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7 days a week. For continuous quality improvement, calls may be recorded or monitored.
- If you have purchased a Care Pack (service upgrade), call 1-800-633-3600. For more information about Care Packs, refer to the HP website (http://www.hp.com).
- In other locations, see the Contact HP worldwide (in English) webpage (http://welcome.hp.com/country/us/en/wwcontact.html).
Customer Self Repair
HP products are designed with many Customer Self Repair (CSR) parts to minimize repair time and allow for greater flexibility in performing defective parts replacement. If during the diagnosis period HP (or HP service providers or service partners) identifies that the repair can be accomplished by the use of a CSR part, HP will ship that part directly to you for replacement. There are two categories of CSR parts:
- Mandatory—Parts for which customer self repair is mandatory. If you request HP to replace these parts, you will be charged for the travel and labor costs of this service.
- Optional—Parts for which customer self repair is optional. These parts are also designed for customer self repair. If, however, you require that HP replace them for you, there may or may not be additional charges, depending on the type of warranty service designated for your product.
NOTE: Some HP parts are not designed for customer self repair. In order to satisfy the customer warranty, HP requires that an authorized service provider replace the part. These parts are identified as "No" in the Illustrated Parts Catalog.
Based on availability and where geography permits, CSR parts will be shipped for next business day delivery. Same day or four-hour delivery may be offered at an additional charge where geography permits. If assistance is required, you can call the HP Technical Support Center and a technician will help you over the telephone. HP specifies in the materials shipped with a replacement CSR part whether a defective part must be returned to HP. In cases where it is required to return the defective part to HP, you must ship the defective part back to HP within a defined period of time, normally five (5) business days. The defective part must be returned with the associated documentation in the provided shipping material. Failure to return the defective part may result in HP billing you for the replacement. With a customer self repair, HP will pay all shipping and part return costs and determine the courier/carrier to be used.
For more information about HP's Customer Self Repair program, contact your local service provider. For the North American program, refer to the HP website (http://www.hp.com/go/selfrepair).
Customer Self Repair
Customer Self Repair
Array Configuration Utility
ASR
Automatic Server Recovery
BBWC
battery-backed write cache
BIOS
Basic Input/Output System
DDR
double data rate
DHCP
Dynamic Host Configuration Protocol
DNS
domain name system
ESD
electrostatic discharge
FBDIMM
fully buffered DIMM
FC
Fibre Channel
FCA
Fibre Channel Adapter
I/O
input/output
IEC
International Electrotechnical Commission
iLO
Integrated Lights-Out
IML
Integrated Management Log
IP
Internet Protocol
ISEE
Instant Support Enterprise Edition
KVM
keyboard, video, and mouse
LED
light-emitting diode
NBP
Network Bootstrap Program
NEMA
National Electrical Manufacturers Association
NFPA
National Fire Protection Association
NFS
network file system
NIC
network interface controller
ORCA
Option ROM Configuration for Arrays
OSEM
Open Services Event Manager
POST
Power-On Self Test
PSP
ProLiant Support Pack
PXE
Preboot Execution Environment
RAID
redundant array of inexpensive (or independent) disks
RBSU
ROM-Based Setup Utility
RDP
Rapid Deployment Pack
ROM
read-only memory
SAN
Storage Area Network
SCSI
small computer system interface
SFF
small form-factor
SFP
small form-factor pluggable
SIM
Systems Insight Manager
SNMP
Simple Network Management Protocol
TCP/IP
Transmission Control Protocol/Internet Protocol
TFTP
Trivial File Transfer Protocol
UID
unit identification
USB
universal serial bus
VCA
Version Control Agent
WEBES
Web-Based Enterprise Service
WfM
Wired for Management
Index
A
access panel 16, 17
ACU (Array Configuration Utility) 48
air baffle 17
Array Configuration Utility (ACU) 48
ASR (Automatic Server Recovery) 49, 88
authorized reseller 80
auto-configuration process 47
Automatic Server Recovery (ASR) 49, 88
Autorun menu 46
B
batteries, replacing 71
battery 71,76
battery-backed write cache enabler 31
bay numbering 12
BIOS Serial Console 48
BIOS upgrade 49
boot diskette 45
BSMI notice 75
buttons 6
C
cables 35, 58, 74
cabling 19
Care Pack 54
cautions 56
CD-ROM deployment 43
Change Control 53
component identification 6,8
configuration of system 46
configuration parameters 45
configuration tools 46
configuration, network 40
connection problems 58
connectors 6
contacting HP 80
creating a network boot diskette 45
CSR (customer self repair) 80
customer self repair (CSR) 80
D
Declaration of Conformity 73
default settings 40
deployment methods 40, 42
DHCP (Dynamic Host Configuration Protocol) 88
DHCP server 39
diagnosing problems 58, 60
diagnostic tools 46, 49, 51
diagnostics utility 51
diskette boot 45
diskette image 44
diskette image deployment 44
documentation 45, 55
drivers 39,52
E
electrostatic discharge 78
environmental specifications 79
error messages 70
European Union notice 74
F
FBDIMM slot locations 11
FBDIMMs 27, 28
Federal Communications Commission (FCC) notice 72, 73, 74
Fibre Channel adapters 30
flash ROM 49
flowcharts 59, 60, 62, 64, 66, 68
front panel components 6
G
general diagnosis flowchart 60
grounding methods 78
H
hard drive LEDs 8, 9
hard drives 8, 28
hard drives, determining status of 8
hardware options 22
hardware options installation 22
health driver 49
HP Insight Diagnostics 51
HP ProLiant Essentials Foundation Pack 50
HP Systems Insight Manager, overview 50
HP Technical Support 80
|
identification number 72
iLO (Integrated Lights-Out) 39, 44, 45, 49, 89
iLO Advanced Functionality 39
IML (Integrated Management Log) 51
Important Safety Information document 56
Insight Diagnostics 51
installation, server options 22
installing operating system 21
Instant Support Enterprise Edition 52
Integrated Lights-Out (iLO) 49, 89
Integrated Management Log (IML) 51
interconnect devices 19, 40
J
Japanese notice 75
K
Korean notices 76
L
LAN cable connection 19
LEDs 6, 8, 9
LEDs, hard drive 8, 9
LEDs, troubleshooting 55
Lights-Out network-based deployment 39, 40, 42
local administration 35
local I/O cable 35, 36
loose connections 58
M
Management Agents 50
management tools 39, 49
memory 27
multifunction network adapter 29
N
Natural Language Search Assistant 53
network component information 19
network server 40
network-based PXE deployment 40
NIC (network interface controller) 89
NIC configuration 40
O
Online ROM Flash Component Utility 53
Open Services Event Manager 52
operating systems 53
Option ROM Configuration for Arrays (ORCA) 48
options installation 20, 22
ORCA (Option ROM Configuration for Arrays) 48
OS boot problems flowchart 66
OS Installation 21
P
phone numbers 80
POST error messages 70
POST problems flowchart 64
power calculator 19
power cord 56
powering down 15
powering up 47
power-on problems flowchart 62
preparation procedures 58
problem diagnosis 55
ProLiant Support Packs 53
PSPs, overview 53
PXE (preboot execution environment) 40, 42
PXE deployment 42
PXE deployment server 40
R
rack stability 56
rack warnings 56
Rapid Deployment Pack 43
RBSU (ROM-Based Setup Utility) 46
RBSU configuration 47
redundant ROM 50
regulatory compliance notices 72, 74
remote support and analysis tools 52
removing the server blade 16
Repository server 40
required information 80
Resource Paqs 53
resources 45, 55
resources, troubleshooting 55
RJ-45 patch panels 19, 40
ROM redundancy 50
ROM-Based Setup Utility (RBSU) 46
ROMPaq utility 49, 50
s
safety considerations 56
safety information 50
SAN configuration 45
scripted installation 43
serial number 48
series number 72
server blade bay numbering 12
server blade enclosure 12
server blade enclosure bay numbering 12
server blade installation 20
server blade removal 16
server fault indications flowchart 68
server features and options 22
service notifications 58
setting up a network 40
SmartStart autorun menu 46
SmartStart Scripting Toolkit 43
SmartStart, overview 46
software 39
software components 39
specifications 79
specifications, server 79
start diagnosis flowchart 59
static electricity 78
support 52,80
support packs 46
supported operating systems 53
Survey Utility 51
switches, interconnect 19, 40
symbols on equipment 56
system board battery 76
Systems Insight Manager 50
T
Taiwan battery recycling notice 76
TCP/IP (Transmission Control Protocol/Internet Protocol) 90
technical support 80
telephone numbers 80
troubleshooting 55
U
updating drivers 39
updating the system ROM 50, 53
updating, FCA device driver 45
USB device cabling 35, 36
USB devices 44
USB support 50
utilities 46, 48, 49, 50, 51, 53
utilities, deployment 43, 46
V
virtual CD-ROM 44
virtual floppy 45
W
warnings 56
Web-Based Enterprise Service 52