HP P800 User Manual

HP Smart Array Controllers for HP Integrity Servers User Guide

Part Number 469987-002 March 2009 (Second Edition)

© Copyright 2008, 2009 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, Windows, and Windows Server are U.S. registered trademarks of Microsoft Corporation. Bluetooth is a trademark owned by its proprietor and used by Hewlett-Packard Company under license.

Intended audience

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.

Hardware features........................................................................................................................ 5

E500 model .............................................................................................................................................5

P700m model...........................................................................................................................................6

P800 model ............................................................................................................................................. 6

Summary of controller features and capabilities............................................................................................. 7

Features common to all controller models............................................................................................ 7

Model-specific features..................................................................................................................... 8

Overview of the installation procedure ..........................................................................................10

Quick installation procedure (Windows or Linux)......................................................................................... 10

Installing the controller hardware.................................................................................................. 12

Preparing the server................................................................................................................................. 12

Installing the controller board.................................................................................................................... 12

Connecting storage devices...................................................................................................................... 13

Connecting internal storage ............................................................................................................ 13

Connecting external storage ...........................................................................................................13

SAS cable part numbers................................................................................................................. 14

Updating the firmware ................................................................................................................ 15

Methods for updating the firmware (Windows or Linux)................................................................................ 15

Configuring an array .................................................................................................................. 16

Utilities available for configuring an array.................................................................................................. 16

Comparing the utilities ............................................................................................................................. 16

Using ORCA........................................................................................................................................... 17

Using ACU............................................................................................................................................. 18

Installing device drivers and Management Agents .......................................................................... 19

Systems using Microsoft Windows............................................................................................................. 19

Installing device drivers .................................................................................................................. 19

Installing the Event Notification Service ............................................................................................ 19

Installing Management Agents ........................................................................................................19

Systems using Linux ................................................................................................................................. 19

Installing Management Agents ........................................................................................................20

Upgrading or replacing controller options ..................................................................................... 21

Replacing the E500 cache........................................................................................................................ 21

Replacing the P700m cache battery........................................................................................................... 21

Replacing a P800 cache battery ...............................................................................................................24

Replacing the P800 cache module or controller........................................................................................... 29

Replacing, moving, or adding hard drives..................................................................................... 32

Identifying the status of a hard drive .......................................................................................................... 32

Recognizing hard drive failure .................................................................................................................. 33

Effects of a hard drive failure .......................................................................................................... 34

Compromised fault tolerance .......................................................................................................... 34

Recovering from compromised fault tolerance.................................................................................... 34

Contents 3

Replacing hard drives.............................................................................................................................. 35

Factors to consider before replacing hard drives................................................................................35

Automatic data recovery (rebuild).................................................................................................... 36

Upgrading hard drive capacity ....................................................................................................... 38

Moving drives and arrays ........................................................................................................................ 38

Adding drives......................................................................................................................................... 39

Diagnosing array problems.......................................................................................................... 41

Controller board runtime LEDs................................................................................................................... 41

Runtime LEDs for E500 model ......................................................................................................... 41

Runtime LEDs for P700m model ....................................................................................................... 42

Runtime LEDs for P800 model.......................................................................................................... 43

Battery pack LEDs.................................................................................................................................... 44

Diagnostic tools ...................................................................................................................................... 45

Electrostatic discharge................................................................................................................. 47

Preventing electrostatic discharge..............................................................................................................47

Grounding methods to prevent electrostatic discharge.................................................................................. 47

Regulatory compliance notices ..................................................................................................... 48

Federal Communications Commission notice............................................................................................... 48

FCC rating label............................................................................................................................ 48

Class A equipment......................................................................................................................... 48

Class B equipment......................................................................................................................... 48

Declaration of conformity for products marked with the FCC logo, United States only....................................... 49

Modifications.......................................................................................................................................... 49

Cables................................................................................................................................................... 49

Canadian notice (Avis Canadien).............................................................................................................. 49

European Union regulatory notice .............................................................................................................50

BSMI notice............................................................................................................................................ 50

Chinese notice ........................................................................................................................................ 50

Japanese notice ...................................................................................................................................... 51

Korean notice ......................................................................................................................................... 51

Battery replacement notice........................................................................................................................ 51

Taiwan battery recycling notice................................................................................................................. 52

Acronyms and abbreviations........................................................................................................ 53

Index......................................................................................................................................... 54

Contents 4

Hardware features

E500 model

Item ID Description

1 Connector for mini-SAS port 1E (external), 4x wide 2 Connector for mini-SAS port 2E (external), 4x wide 3 40-bit, 256-MB cache module (also known as array accelerator)

CAUTION: Do not use this controller with cache modules designed for other controller models,

because the controller can malfunction and you can lose data. Also, do not transfer this cache module to a different controller module, because you can lose data.

Hardware features 5

P700m model

Item ID Description

1 Status LEDs (runtime LEDs). To interpret the illumination pattern of

these LEDs, see "Controller board runtime LEDs (on page 41)". 2 Connector (not used on HP Integrity servers). 3 Cache module (also known as array accelerator). 4 Connector for the cable to an optional cache battery that upgrades

the cache to BBWC. This connector is absent on some P700m

models. 5 Mezzanine connector to system board.

P800 model

Hardware features 6

Item ID Description

1 Connector for mini-SAS ports 1E and 2E (external), each 4x wide 2 Heartbeat LED (flashes green when operating normally and amber

if the board has failed) 3 Activity LED for external ports 4 SAS port 3I (internal), 4x wide 5 SAS port 4I (internal), 4x wide 6 Cache module (also known as array accelerator) 7 (Optional) Batteries for cache module

Two batteries are normally sufficient, but you can add a third

battery to provide extra security against loss of system power.

Summary of controller features and capabilities

This section describes the most commonly referenced controller features. For other features, specifications, and information about system requirements, see the HP website (http://www.hp.com/products/smartarray the controller is loaded with the latest firmware.

). To get the full benefit of all controller features, be sure that

Features common to all controller models

Feature Details

Temperature range Operating, 10° to 55°C (50° to 131°F)

Storage, -30° to 60°C (-22° to 140°F)

Relative humidity (noncondensing)

Time required to recharge battery*

Duration of battery backup* If the battery is fully charged and less than 3 years old, more than 2

Battery life expectancy* More than 3 years PCIe transfer rate Up to 2 GB/s in each direction SAS transfer rate 1.2 GB/s for each wide port at peak bandwidth Drive types supported 3.0 Gb/s SAS or 1.5 Gb/s SATA hard drives. Also supports OBDR

Maximum logical drive size 8 ZB (8 x 1021 bytes) Maximum number of physical

devices Maximum number of logical

drives

*For controllers that use battery-backed write cache.

Operating, 10% to 90% Storage, 5% to 90%

From 15 minutes to 2 hours, depending on the initial battery charge level

days

tape drives. For more information about OBDR, see the HP website (http://www.hp.com/go/obdr

255 (total of hard drives, expanders, and SEPs)

Hardware features 7

Model-specific features

HP Smart Array E500 Controller features

In HP Integrity servers, the E500 controller does not support RAID-level or stripe-size migration, array capacity expansion, or logical drive extension.

Feature Description

Board type Low-profile, PCIe stand-up board Dimensions, cm* 16.8 x 7.0 x 1.8 Dimensions, in* 6.6 x 2.8 x 0.7 Maximum number

of physical drives Maximum power

required (approximate)

RAID levels 0, 1, and 1+0; with cache battery, also RAID 5 Battery kit option

part number Cache size 40 bits, 256 MB I/O connection to

the system board

*These dimensions exclude the board bracket.

100 external

14 W

Not supported on Integrity servers

PCIe x8 edge connector

HP Smart Array P700m Controller features

Feature Description

Board type Type I, 4-port, PCIe mezzanine board Dimensions, cm 11.3 x 10.0 x 2.0 Dimensions, in 4.5 x 4.0 x 0.8 Maximum number

of physical drives Maximum power

required (approximate)

RAID levels 0, 1, 1+0, and 5; with cache battery, also RAID 6 Battery kit option

part number Cache size 72 bits, 512 MB (64 MB is used by the onboard

I/O connection to the system board

*These dimensions exclude the board bracket.

108 external

9.30 W

453779-001

processor) Grid array mezzanine connector

Hardware features 8

HP Smart Array P800 Controller features

Feature Description

Board type Full-size, PCIe stand-up board Dimensions, cm* 31.1 x 11.1 x 1.2 Dimensions, in* 12.3 x 4.4 x 0.5 Maximum number of

physical drives Maximum power

required (approximate)

RAID levels 0, 1, 1+0, and 5; with cache battery, also RAID 6 Battery kit option part

number Cache size 72 bits, 512 MB (48 MB is used by the onboard

I/O connection to the system board

*These dimensions exclude the board bracket.

108 (internal + external)

25 W

398648-001

processor) PCIe x8 edge connector

Hardware features 9

Overview of the installation procedure

Quick installation procedure (Windows or Linux)

Before installing the controller, refer to the support matrix on the HP website (http://www.hp.com/products1/serverconnectivity support the controller.

To install the controller:

1. Power down the server.

2. Unplug the AC power cord from the power outlet.

3. Unplug the power cord from the server.

4. Install the controller hardware ("Installing the controller hardware" on page 12).

5. If necessary, install additional physical drives.

) to confirm that the server and operating system

The number of drives in the server determines the RAID level that is autoconfigured when the server is powered up (next step).

6. Power up the server.

7. Update the controller firmware ("Methods for updating the firmware (Windows or Linux)" on page

15).

When the firmware update process is complete, the server reboots and runs through a POST procedure. This POST procedure halts briefly during controller initialization and prompts you to open ORCA.

8. Open ORCA ("Configuring an array" on page 16).

o If using a headless console, press the Esc+8 key combination. o Otherwise, press the F8 key.

9. Configure the logical boot drive, and then exit from ORCA.

If the server is using Linux, controller installation is complete. When the server is next rebooted, the operating system detects the controller hardware and automatically installs the required driver.

If the server is using Microsoft® Windows®, continue as follows:

1. Load the controller driver from EBSU on the Smart Setup media. (To load the driver, select Load OEM

Boot Drivers in EBSU. For more information about Smart Setup, refer to the HP Smart Setup Guide on

the Smart Setup media.)

2. Run Express Setup.

3. When you have finished installing the operating system as directed during the Express Setup

procedure, remove the operating system CD, and then insert the Smart Setup media.

4. Install the Integrity Support Pack ("Installing device drivers and Management Agents" on page 19).

Controller installation is complete.

Overview of the installation procedure 10

The latest firmware, drivers, utilities, software, and documentation for HP Integrity servers are available on the support page of the HP website (http://www.hp.com/support/itaniumservers

Overview of the installation procedure 11

Installing the controller hardware

Preparing the server

1. Back up all data.

2. Close all applications.

3. Power down the server.

CAUTION: In systems that use external data storage, be sure that the server is the first unit to

be powered down and the last to be powered back up. Taking this precaution ensures that the

4. Power down all peripheral devices that are attached to the server.

5. Unplug the AC power cord from the outlet and then from the server.

system does not erroneously mark the drives as failed when the server is powered up.

6. Disconnect all peripheral devices from the server.

Installing the controller board

WARNING: To reduce the risk of personal injury or damage to the equipment, consult the

safety information and user documentation provided with the server before attempting the installation.

Many servers are capable of providing energy levels that are considered hazardous and are intended to be serviced only by qualified personnel who have been trained to deal with these hazards. Do not remove enclosures or attempt to bypass any interlocks that may be provided

1. Remove or open the access panel.

2. Select an available x8 or larger PCIe slot.

3. Remove the slot cover. Save the retaining screw, if one is present.

4. Install the cache module on the controller.

for the purpose of removing these hazardous conditions.

WARNING: To reduce the risk of personal injury from hot surfaces, allow the drives and the

internal system components to cool before touching them.

If the cache module is absent, the controller will not boot.

5. Slide the controller board along the slot alignment guide, if one is present, and then press the board

firmly into the slot so that the contacts on the board edge are properly seated in the system board connector.

6. Secure the controller board in place with the retaining screw. If the slot alignment guide has a latch

(near the rear of the board), close the latch.

7. Connect storage devices to the controller. (For details of the procedure, see "Connecting storage

devices (on page 13).")

Installing the controller hardware 12

Close or replace the access panel, and then secure it with thumbscrews, if any are present.

CAUTION: Do not operate the server for long periods with the access panel open or removed.

Operating the server in this manner results in improper airflow and improper cooling that can lead to thermal damage.

Connecting storage devices

Depending on the controller model, you can connect SAS or SATA drives to the controller internally ("Connecting internal storage" on page 13), externally, or both.

For information about supported drive models for a particular controller, see the controller-specific page

Connecting internal storage

on the HP website (http://www.hp.com/products/smartarray

1. Power down the server.

2. Install hard drives, if necessary. If you want to group some of the drives in an array, they must meet

the following criteria:

o They must be of the same type, either all SAS or all SATA. (This controller does not support

parallel SCSI drives.)

o For efficient use of drive space, they must have comparable capacity.

For additional information about drive installation, see the appropriate section in this guide ("Replacing, moving, or adding hard drives" on page 32) and consult the server documentation and the documentation that accompanied the drives.

3. Use the internal wide SAS cable provided with the server to connect the controller to the drives.

o If the drives are hot-plug capable, connect the internal connector of the controller to the SAS

connector on the hot-plug drive cage.

o If the drives are not hot-plug capable, connect the internal connector of the controller to the non-

hot-plug hard drives.

4. Close or replace the access panel, and secure it with thumbscrews, if any are present.

CAUTION: Do not operate the server for long periods with the access panel open or removed.

Operating the server in this manner results in improper airflow and improper cooling that can

5. Power up the server.

lead to thermal damage.

Connecting external storage

To connect external storage:

1. Power down the server.

2. Connect an external SAS cable to the external port of the controller: a. Pull back the tab on the mini SAS 4x connector on the cable. b. Insert the cable connector into the external port of the controller. c. Release the tab.

Installing the controller hardware 13

Connect the other end of the cable to the SAS input connector of the external storage enclosure:

o If the enclosure uses a standard SAS 4x connector, insert the cable connector into the enclosure

connector, and then tighten the lock screws on the cable connector.

o If the enclosure uses a mini SAS 4x connector, pull back the tab on the cable connector, insert

the cable connector into the enclosure connector, and then release the tab.

4. Power up the enclosure.

5. Power up the server.

SAS cable part numbers

To order additional cables, use the option kit part number.

Approximate cable length

1 m (3 ft) Mini SAS 4x to standard SAS 4x 419570-B21 408908-002 2 m (6 ft) Mini SAS 4x to mini SAS 4x 407339-B21 407344-003 — Mini SAS 4x to standard SAS 4x 419571-B21 408908-003 4 m (13 ft) Mini SAS 4x to mini SAS 4x 432238-B21 407344-004 — Mini SAS 4x to standard SAS 4x 419572-B21 408908-004 6 m (20 ft) Mini SAS 4x to mini SAS 4x 432239-B21 407344-005 — Mini SAS 4x to standard SAS 4x 419573-B21 408908-005

Type of cable Option kit part

number

Cable assembly number

Installing the controller hardware 14

Updating the firmware

Methods for updating the firmware (Windows or Linux)

To update the firmware on the server, controller, or hard drives, use Smart Components. The most recent version of a particular component is available on the support page of the HP website (http://www.hp.com/support

1. Find the most recent version of the component that you require.

2. Follow the instructions for installing the component on the server. These instructions are provided on

the same Web page as the component.

3. Follow the additional instructions that describe how to use the component to flash the ROM. These

instructions are provided with each component.

). Some components are also available on the Smart Setup media.

Updating the firmware 15

Configuring an array

Utilities available for configuring an array

Two utilities are available for configuring an array on an HP Smart Array controller in an HP Integrity server: ORCA and ACU.

• ORCA is a simple utility that is used mainly to configure the first logical drive in a new server before

the operating system is loaded.

• ACU is an advanced utility that enables you to perform many complex configuration tasks.

For more information about the features of these utilities and for instructions for using the utilities, see the Configuring Arrays on HP Smart Array Controllers Reference Guide. This guide is available on the Documentation CD that is provided in the controller kit.

Whichever utility you use, remember the following factors when you build an array:

• All drives in an array must be of the same type (for example, all SAS or all SATA).

• For the most efficient use of drive space, all drives within an array should have approximately the

same capacity. Each configuration utility treats every physical drive in an array as if it has the same capacity as the smallest drive in the array. Any excess capacity of a particular drive cannot be used in the array and so is unavailable for data storage.

• The more physical drives that an array has, the greater the probability that the array will experience

a drive failure during any given period. To guard against the data loss that occurs when a drive fails, configure all logical drives in an array with a suitable fault-tolerance (RAID) method.

Comparing the utilities

NOTE: A + in the appropriate column indicates that the feature or procedure is supported,

Supported features ACU ORCA

Uses a graphical interface + -Available in languages other than English + -Available on CD + -Uses a wizard to suggest the optimum configuration for an unconfigured controller + -Describes configuration errors + -Suitable for configuration while online + -Suitable for configuration while offline -- +

Supported procedures ACU ORCA

Creation and deletion of arrays and logical drives + +

while -- indicates that the feature or procedure is not supported.

Configuring an array 16

Supported procedures ACU ORCA

Assignment of RAID level + + Sharing of spare drives among several arrays + -Assignment of multiple spare drives per array + -Setting of stripe size + -Migration of RAID level or stripe size + -Configuration of controller settings + -Expansion of an array + -Creation of multiple logical drives per array + --

Using ORCA

1. Power up the server.

POST runs, and any array controllers that are in the server are initialized one at a time. During each controller initialization process, POST halts for several seconds while an ORCA prompt message appears.

2. At the ORCA prompt, do one of the following:

o If you are connected using a headless console, press the Esc+8 key combination. o In all other situations, press the F8 key.

The ORCA main menu appears, enabling you to create, view, or delete a logical drive.

To create a logical drive using ORCA:

1. Select Create Logical Drive.

Configuring an array 17

The screen displays a list of all available (unconfigured) physical drives and the valid RAID options for the system.

2. Use the Arrow keys, Spacebar, and Tab key to navigate the screen and set up the logical drive,

including an online spare drive if one is required.

NOTE: You cannot use ORCA to configure one spare drive to be shared among several

arrays. Only ACU enables you to configure shared spare drives.

3. Press the Enter key to accept the settings.

4. Press the F8 key to confirm the settings and save the new configuration.

After several seconds, the Configuration Saved screen appears.

5. Press the Enter key to continue.

You can now create another logical drive by repeating the previous steps.

NOTE: Newly created logical drives are invisible to the operating system. To make the new

logical drives available for data storage, format them using the instructions given in the operating system documentation.

Using ACU

For detailed information about using ACU, see the Configuring Arrays on HP Smart Array Controllers Reference Guide. This document is available on the Smart Setup media or the Documentation CD that is provided in the controller kit.

Configuring an array 18

Installing device drivers and Management Agents

Systems using Microsoft Windows

You can use the Integrity Support Pack to automatically install the device drivers, Event Notification Service, and Management Agents, or you can install these items manually.

The Integrity Support Pack is located on the Smart Setup media. To install the Integrity Support Pack,

Installing device drivers

launch Express Setup from EBSU and follow the on-screen instructions.

The drivers for the controller are located on the Smart Setup media. Updates are posted to the support page of the HP website (http://www.hp.com/support/itaniumservers

Installation instructions are provided with the drivers.

Installing the Event Notification Service

The HP Smart Array SAS/SATA Event Notification Service provides event notification to the Microsoft® Windows® Server 2003 64-bit system event log and the HP Integrated Management log.

The most recent version of the software component is available on the support page of the HP website (http://www.hp.com/support/itaniumservers

). Installation instructions are provided with the component.

Installing Management Agents

The Management Agents are available on the Smart Setup media. The most recent versions of the agents are available on the support page of the HP website (http://www.hp.com/support/itaniumservers Installation instructions are provided with the agents.

If the new agents do not function correctly, you might also need to update Systems Insight Manager. The latest version of Systems Insight Manager is available for download at the HP website (http://www.hp.com/servers/manage

Systems using Linux

The drivers for the controller are bundled into the supported Red Hat and Novell Linux distributions.

In a system that does not yet have Linux installed:

1. Follow the standard controller installation procedure.

2. Reboot the server.

Installing device drivers and Management Agents 19

Follow the standard procedure for installing Linux. As Linux is installed, it recognizes the controller and automatically loads the correct driver.

In a system that already has Linux installed:

1. Power down the system.

2. Follow the standard controller installation procedure.

3. Power up the system. As Linux boots, it recognizes the controller.

4. Enter one of the following commands as appropriate to ensure that the driver is loaded correctly:

Red Hat: #mkinitrd -f /boot/efi/efi/redhat/initrd-$(uname -r).img $(uname -

Novell (SLES): #mkinitrd -k /boot/vmlinux -i/boot/initrd

5. For Novell, enter the following command to confirm that the driver is active:

#lsmod | grep cciss

If the driver is active, the system responds by displaying cciss.

Installing Management Agents

The most recent versions of the agents are available on the support page of the HP website (http://www.hp.com/support/itaniumservers HP Insight Management Agents for Linux on Integrity Servers provided with the agents.

). For installation instructions, refer to the downloadable file

Installing device drivers and Management Agents 20

Upgrading or replacing controller options

Replacing the E500 cache

CAUTION: Do not use this controller with cache modules designed for other controller models,

because the controller can malfunction and you can lose data. Also, do not transfer this cache

1. Close all applications, and then power down the server. This procedure flushes all data from the

2. Disconnect the server from the AC power source.

3. Remove the controller from the server and place it on a firm, flat, and nonconductive surface.

4. Remove the existing cache from the controller by lifting both ends of the cache module with equal

module to a different controller module, because you can lose data.

cache.

force.

5. Install the new cache on the controller. Press firmly above each connector to ensure good electrical

contact. (If the cache is not connected properly, the controller cannot boot.)

6. Install the controller in the server.

Replacing the P700m cache battery

CAUTION: Electrostatic discharge can damage electronic components. Be sure you are

The method for replacing a battery depends on whether the battery case is mounted on the inner wall of the server chassis by a hook-and-loop strip or located in a hard drive slot.

properly grounded before beginning this procedure.

Upgrading or replacing controller options 21

If the battery case is mounted on the inner wall of the server chassis:

1. Back up all data.

2. Close all applications.

3. Power down the server.

4. Remove the server from the enclosure.

5. Remove the server access panel.

6. Remove the battery case from the chassis wall.

7. Disconnect the cable from the battery.

8. Remove the battery from the battery case.

9. Install the replacement battery in the battery case.

10. Connect the battery cable to the replacement battery.

11. Mount the battery case on the chassis wall.

12. Close the server access panel.

13. Reinstall the server in the enclosure.

After installing a battery pack, you might see a POST message during reboot indicating that the array accelerator (cache) is temporarily disabled. This behavior is normal because the new battery pack is likely to have a low charge. You do not need to take any action because the recharge process begins automatically when the battery pack is installed. The controller operates properly while the battery pack is recharging, although the performance advantage of the array accelerator is absent. When the battery pack has been charged to a predetermined level, the array accelerator is automatically enabled.

If the battery case is located in a hard drive slot:

1. Back up all data.

2. Close all applications.

3. Power down the server.

4. Remove the server from the enclosure.

5. Remove the server access panel.

6. Remove the battery case from the hard drive slot.

7. Disconnect the battery cable.

8. Invert the battery case.

Upgrading or replacing controller options 22

Pull the right hand portion of the battery case away from the battery pack and simultaneously rotate the battery out of the opening.

10. Position the replacement battery pack in the opening in the battery case as shown. The upper left

edge of the battery is under the flanges on the pillars at the left edge of the opening, and the right side of the battery rests on the right pillars.

Upgrading or replacing controller options 23

11.

Pull the right hand portion of the battery case away from the battery, and simultaneously rotate the battery pack into the opening.

12. Connect the battery cable to the battery and the cache. Route the battery cable so that the cache

and battery can be removed together. (If you need to remove the cache to transfer data, the battery must remain connected to it so that the data is preserved.)

13. Insert the battery case into the hard drive slot.

14. Close the server access panel.

15. Reinstall the server in the enclosure.

Replacing a P800 cache battery

CAUTION: Electrostatic discharge can damage electronic components. Be sure you are

1. Close all applications, and then power down the server. This procedure flushes all data from the

2. Observe the BBWC Status LED ("Battery pack LEDs" on page 44).

properly grounded before beginning this procedure.

cache.

o If the LED is blinking every 2 seconds, data is trapped in the cache. Restore system power, and

then repeat the previous steps in this procedure.

o If the LED is not lit, proceed with the next step.

WARNING: There is a risk of explosion, fire, or personal injury if the battery pack is not

properly handled. Refer to "Battery replacement notice (on page 51)" before installing or removing any item that contains a battery pack.

Upgrading or replacing controller options 24

Remove the controller from the server.

4. Pull the flanges on the battery clip outward (1), and then swivel the clip 180 degrees so that it rests

on the batteries (2).

5. Slide the batteries toward the right edge of the controller, away from the bracket.

6. While holding the battery assembly, tilt the clip until it is at about 30 degrees to the batteries, and

then push the clip in line with the clip hinges until the clip detaches from the batteries.

The rest of the procedure depends on whether you are replacing a battery or adding one.

o If you are replacing a battery, continue with the next step. o If you are only adding an optional third battery, go to step 9.

7. Separate the batteries. a. Turn the batteries over. b. Pull the lip on the right battery case away from the edge of the adjacent battery case (1).

Upgrading or replacing controller options 25

Slide the batteries apart (2).

8. Dispose of the exhausted or faulty battery using environmentally approved procedures ("Battery

replacement notice" on page 51).

9. Position the new battery and the remaining good battery as indicated, push them together, and then

slide them until they are aligned. The batteries combine into one unit.

10. Install the battery clip. a. Position the clip so that the hinges on the clip are next to the appropriate hinge pillars on the

batteries.

b. Hold the clip at about 30 degrees to the batteries.

Upgrading or replacing controller options 26

Push the clip at the hinges until the clip clicks into place.

11. Reinstall the batteries. a. Hold the controller board near the DIMM socket and at the top and right edges to minimize

bending of the board.

b. Position the batteries so that the pegs A on the underside of each battery are in the appropriate

holes B on the controller board and pegs C are in slots D.

Upgrading or replacing controller options 27

Slide the batteries toward the board bracket until they are firmly seated against the connectors on the cache module.

12. Secure the battery clip to the controller board: a. Swivel the clip over the cache module (1). b. Push the clip firmly at both ends (2) until it clicks into place under the controller board.

13. Reinstall the controller in the server.

After installing a battery pack, you might see a POST message during reboot indicating that the array accelerator (cache) is temporarily disabled. This behavior is normal because the new battery pack is likely to have a low charge. You do not need to take any action, because the recharge process begins automatically when the battery pack is installed. The controller operates properly while the battery pack recharges, although the performance advantage of the array accelerator is absent. When the battery pack has been charged to a satisfactory level, the array accelerator is automatically enabled.

Upgrading or replacing controller options 28

Replacing the P800 cache module or controller

CAUTION: Electrostatic discharge can damage electronic components. Be sure you are

1. Close all applications, and then power down the server. This procedure flushes all data from the

2. Observe the BBWC Status LED ("Battery pack LEDs" on page 44).

3. Remove the controller from the server.

4. Pull the flanges on the battery clip outward (1), and then swivel the clip 180 degrees so that it rests

properly grounded before beginning this procedure.

cache.

o If the LED is blinking every 2 seconds, data is trapped in the cache. Restore system power, and

repeat the previous steps in this procedure.

o If the LED is not lit, proceed with the next step.

WARNING: There is a risk of explosion, fire, or personal injury if the battery pack is not

properly handled. Refer to "Battery replacement notice (on page 51)" before installing or removing any item that contains a battery pack.

on the batteries (2).

5. Swivel the latches on the DIMM connector outward (1).

Upgrading or replacing controller options 29

Slide the battery assembly and the cache module off the controller board (2).

The procedure at this point depends on whether you are replacing the controller or the cache module.

o If you are replacing the controller, go directly to the next step. o If you are replacing the cache module, pull it out of the battery assembly, install the new cache

module in its place, and then go to the next step.

7. Install the cache module and batteries on the controller board. a. Hold the controller board near the DIMM connector and at the top and right edges to minimize

bending of the board.

b. Position the batteries so that the pegs A on the underside of each battery are in the appropriate

holes B on the controller board, and pegs C are in slots D.

Upgrading or replacing controller options 30

Slide the batteries toward the board bracket until the connectors on the cache module are firmly seated in the DIMM connector. (When the cache module is correctly seated, the gold contacts on the cache module are completely hidden within the DIMM connector.)

8. Secure the battery clip to the controller board. a. Swivel the clip over the cache module (1). b. Push the clip firmly at both ends (2) until it clicks into place under the controller board.

9. Reinstall the controller in the server.

Upgrading or replacing controller options 31

Replacing, moving, or adding hard drives

Identifying the status of a hard drive

When a drive is configured as a part of an array and connected to a powered-up controller, the condition of the drive can be determined from the illumination pattern of the hard drive status lights (LEDs).

Item Description

1 Fault/UID LED (amber/blue) 2 Online LED (green)

Online/activity LED (green)

On, off, or flashing Alternating amber

On, off, or flashing Steadily blue The drive is operating normally, and it has been selected by a

On Amber, flashing

On Off The drive is online, but it is not active currently.

Fault/UID LED (amber/blue)

and blue

regularly (1 Hz)

Interpretation

The drive has failed, or a predictive failure alert has been received for this drive; it also has been selected by a management application.

management application. A predictive failure alert has been received for this drive. Replace the drive as soon as possible.

Replacing, moving, or adding hard drives 32

Online/activity LED (green)

Flashing regularly (1 Hz)

Flashing irregularly Amber, flashing

Flashing irregularly Off The drive is active, and it is operating normally. Off Steadily amber A critical fault condition has been identified for this drive, and

Off Amber, flashing

Off Off The drive is offline, a spare, or not configured as part of an

Fault/UID LED

Interpretation

(amber/blue)

Amber, flashing regularly (1 Hz)

Off Do not remove the drive. Removing a drive may terminate the

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.

current operation and cause data loss. The drive is rebuilding, erasing, or it is part of an array that is

undergoing capacity expansion or stripe migration. The drive is active, but a predictive failure alert has been

received for this drive. Replace the drive as soon as possible.

the controller has placed it offline. Replace the drive as soon as possible.

A predictive failure alert has been received for this drive. Replace the drive as soon as possible.

array.

Recognizing hard drive failure

A steadily glowing Fault LED indicates that that drive has failed. Other indications of hard drive failure include:

• The amber LED on the front of a storage system illuminates if failed drives are inside. This LED also

illuminates when other problems occur, such as when a fan fails, a redundant power supply fails, or the system overheats.

• A POST message lists failed drives when the system is restarted, as long as the controller detects at

least one functional drive.

• ACU represents failed drives with a distinctive icon.

• HP Systems Insight Manager can detect failed drives remotely across a network. For more

information about HP Systems Insight Manager, see the documentation on the Management CD.

• The Event Notification Service posts an event to the Microsoft® Windows® system event log and the

HP Integrity System Event Log.

• ADU lists all failed drives.

For additional information about diagnosing hard drive problems, see the troubleshooting chapter in the server-specific service guide.

Replacing, moving, or adding hard drives 33

CAUTION: Sometimes, a drive that has previously been failed by the controller may seem to

be operational after the system is power-cycled or (for a hot-pluggable drive) after the drive has been removed and reinserted. However, continued use of such marginal drives may eventually result in data loss. Replace the marginal drive as soon as possible.

Effects of a hard drive failure

When a hard drive fails, all logical drives that are in the same array are affected. Each logical drive in an array might be using a different fault-tolerance method, so each logical drive can be affected differently.

• RAID 0 configurations cannot tolerate drive failure. If any physical drive in the array fails, all non-

fault-tolerant (RAID 0) logical drives in the same array will also fail.

• RAID 1+0 configurations can tolerate multiple drive failures as long as no failed drives are mirrored

to one another.

• RAID 5 configurations can tolerate one drive failure.

• RAID 6 (ADG) configurations can tolerate the simultaneous failure of two drives.

Compromised fault tolerance

If more hard drives fail than the fault-tolerance method allows, fault tolerance is compromised, and the logical drive fails. In this case, all requests from the operating system are rejected with unrecoverable errors. You are likely to lose data, although it can sometimes be recovered (refer to "Recovering from

compromised fault tolerance" on page 34).

One example of a situation in which compromised fault tolerance may occur is when a drive in an array fails while another drive in the array is being rebuilt. If the array has no online spare, any logical drives in this array that are configured with RAID 5 fault tolerance will fail.

Compromised fault tolerance can also be caused by non-drive problems, such as a faulty cable or temporary power loss to a storage system. In such cases, you do not need to replace the physical drives. However, you may still have lost data, especially if the system was busy at the time that the problem occurred.

Recovering from compromised fault tolerance

If fault tolerance is compromised, inserting replacement drives does not improve the condition of the logical volume. Instead, if the screen displays unrecoverable error messages, perform the following procedure to recover data:

1. Power down the entire system, and then power it back up. In some cases, a marginal drive will work

again for long enough to enable you to make copies of important files. If a 1779 POST message is displayed, press the F2 key to re-enable the logical volumes. Remember

that data loss has probably occurred and any data on the logical volume is suspect.

2. Make copies of important data, if possible.

3. Replace any failed drives.

4. After you have replaced the failed drives, fault tolerance may again be compromised. If so, cycle the

power again. If the 1779 POST message is displayed:

a. Press the F2 key to re-enable the logical drives.

Replacing, moving, or adding hard drives 34

Recreate the partitions.

c. Restore all data from backup.

To minimize the risk of data loss that is caused by compromised fault tolerance, make frequent backups of all logical volumes.

Replacing hard drives

The most common reason for replacing a hard drive is that it has failed. However, another reason is to gradually increase the storage capacity of the entire system.

If you insert a hot-pluggable drive into a drive bay while the system power is on, all disk activity in the array pauses for a second or two while the new drive is spinning up. When the drive has achieved its normal spin rate, data recovery to the replacement drive begins automatically (as indicated by the blinking Online/Activity LED on the replacement drive) if the array is in a fault-tolerant configuration.

If you replace a drive belonging to a fault-tolerant configuration while the system power is off, a POST message appears when the system is next powered up. This message prompts you to press the F1 key to start automatic data recovery. If you do not enable automatic data recovery, the logical volume remains in a ready-to-recover condition and the same POST message appears whenever the system is restarted.

Factors to consider before replacing hard drives

Before replacing a degraded drive:

• Open Systems Insight Manager, and inspect the Error Counter window for each physical drive in the

same array to confirm that no other drives have any errors. (For details, refer to the Systems Insight Manager documentation on the Management CD.)

• Be sure that the array has a current, valid backup.

• Confirm that the replacement drive is of the same type (SAS or SATA) as the degraded drive.

• Use replacement drives that have a capacity at least as great as that of the smallest drive in the

array. The controller immediately fails drives that have insufficient capacity.

In systems that use external data storage, be sure that the server is the first unit to be powered down and the last to be powered back up. Taking this precaution ensures that the system does not erroneously mark the drives as failed when the server is powered up.

To minimize the likelihood of fatal system errors, take these precautions when removing failed drives:

• Do not remove a degraded drive if any other drive in the array is offline (the Online/Activity LED is

off). In this situation, no other drive in the array can be removed without data loss. The following cases are exceptions:

o When RAID 1+0 is used, drives are mirrored in pairs. Several drives can be in a failed condition

simultaneously (and they can all be replaced simultaneously) without data loss, as long as no two failed drives belong to the same mirrored pair.

o When RAID 6 (ADG) is used, two drives can fail simultaneously (and be replaced simultaneously)

without data loss.

o If the offline drive is a spare, the degraded drive can be replaced.

Replacing, moving, or adding hard drives 35

• Do not remove a second drive from an array until the first failed or missing drive has been replaced

and the rebuild process is complete. (The rebuild is complete when the Online/Activity LED on the front of the drive stops blinking.)

The following cases are exceptions:

o In RAID 6 (ADG) configurations, any two drives in the array can be replaced simultaneously. o In RAID 1+0 configurations, any drives that are not mirrored to other removed or failed drives

can be simultaneously replaced offline without data loss.

Automatic data recovery (rebuild)

When you replace a hard drive in an array, the controller uses the fault-tolerance information on the remaining drives in the array to reconstruct the missing data (the data that was originally on the replaced drive) and write it to the replacement drive. This process is called automatic data recovery, or rebuild. If fault tolerance is compromised, this data cannot be reconstructed and is likely to be permanently lost.

If another drive in the array fails while fault tolerance is unavailable during rebuild, a fatal system error can occur, and all data on the array is then lost. In exceptional cases, however, failure of another drive need not lead to a fatal system error. These exceptions include:

• Failure after activation of a spare drive

• Failure of a drive that is not mirrored to any other failed drives (in a RAID 1+0 configuration)

• Failure of a second drive in a RAID 6 (ADG) configuration

Time required for a rebuild

The time required for a rebuild varies considerably, depending on several factors:

• The priority that the rebuild is given over normal I/O operations (you can change the priority setting

by using ACU)

• The amount of I/O activity during the rebuild operation

• The rotational speed of the hard drives

• The availability of drive cache

• The brand, model, and age of the drives

• The amount of unused capacity on the drives

• For RAID 5 and RAID 6 (ADG), the number of drives in the array

Allow approximately 15 minutes per gigabyte for the rebuild process to be completed. This figure is conservative; the actual time required is usually less than this.

System performance is affected during the rebuild, and the system is unprotected against further drive failure until the rebuild has finished. Therefore, replace drives during periods of low activity when possible.

When automatic data recovery has finished, the Online/Activity LED of the replacement drive stops blinking steadily at 1 Hz and begins to either glow steadily (if the drive is inactive) or flash irregularly (if the drive is active).

Replacing, moving, or adding hard drives 36

CAUTION: If the Online/Activity LED on the replacement drive does not light up while the

corresponding LEDs on other drives in the array are active, the rebuild process has abnormally terminated. The amber Fault LED of one or more drives might also be illuminated. Refer to "Abnormal termination of a rebuild (on page 37)" to determine what action you must take.

Abnormal termination of a rebuild

If the Online/Activity LED on the replacement drive permanently ceases to be illuminated even while other drives in the array are active, the rebuild process has abnormally terminated. The following table indicates the three possible causes of abnormal termination of a rebuild.

Observation Cause of rebuild termination

None of the drives in the array have an illuminated amber Fault LED.

The replacement drive has an illuminated amber Fault LED.

One of the other drives in the array has an illuminated amber Fault LED.

Each of these situations requires a different remedial action.

One of the drives in the array has experienced an uncorrectable read error.

The replacement drive has failed.

The drive with the illuminated Fault LED has now failed.

Case 1: An uncorrectable read error has occurred.

1. Back up as much data as possible from the logical drive.

CAUTION: Do not remove the drive that has the media error. Doing so causes the logical drive

to fail.

2. Restore data from backup. Writing data to the location of the unreadable sector often eliminates the

error.

3. Remove and reinsert the replacement drive. This action restarts the rebuild process.

If the rebuild process still terminates abnormally:

1. Delete and recreate the logical drive.

2. Restore data from backup.

Case 2: The replacement drive has failed.

Verify that the replacement drive is of the correct capacity and is a supported model. If these factors are not the cause of the problem, use a different drive as the replacement.

Case 3: Another drive in the array has failed. A drive that has recently failed can sometimes be made temporarily operational again by cycling the

server power.

1. Power down the server.

2. Remove the replacement physical drive (the one undergoing a rebuild), and reinstall the drive that it

is replacing.

3. Power up the server.

If the newly failed drive seems to be operational again:

1. Back up any unsaved data.

Replacing, moving, or adding hard drives 37

Remove the drive that was originally to be replaced, and reinsert the replacement physical drive. The rebuild process automatically restarts.

3. When the rebuild process has finished, replace the newly failed drive.

However, if the newly failed drive has not recovered:

1. Remove the drive that was originally to be replaced, and reinsert the replacement physical drive.

2. Replace the newly failed drive.

3. Restore data from backup.

Upgrading hard drive capacity

You can increase the storage capacity on a system even if there are no available drive bays by swapping drives one at a time for higher capacity drives. This method is viable as long as a fault-tolerance method is running.

CAUTION: Because it can take up to 15 minutes per gigabyte to rebuild the data in the new

configuration, the system is unprotected against drive failure for many hours while a given drive is upgraded. Perform drive capacity upgrades only during periods of minimal system

To upgrade hard drive capacity:

1. Back up all data.

2. Replace any drive. The data on the new drive is re-created from redundant information on the

activity.

remaining drives.

CAUTION: Do not replace any other drive until data rebuild on this drive is complete.

When data rebuild on the new drive is complete, the Online/Activity LED stops flashing steadily and either flashes irregularly or glows steadily.

3. Repeat the previous step for the other drives in the array, one at a time.

When you have replaced all drives, you can use the extra capacity to either create new logical drives or extend existing logical drives. For more information about these procedures, refer to the HP Array Configuration Utility User Guide.

Moving drives and arrays

You can move drives to other ID positions on the same array controller. You can also move a complete array from one controller to another, even if the controllers are on different servers.

Before you move drives:

• The server must be powered down.

• If moving the drives to a different server, the new server must have enough empty bays to

accommodate all the drives simultaneously.

• The array must not have failed or missing drives.

• No spare drive in the array is acting as a replacement for a failed drive.

Replacing, moving, or adding hard drives 38

• The controller is not running capacity expansion, capacity extension, or RAID or stripe size

migration.

• The controller is using the latest firmware version (recommended).

Before you move an array to another controller:

• If the other controller is already connected to one or more arrays of configured logical drives, the

total number of logical drives on the controller after the drives have been moved must not exceed the number of logical drives that the controller supports. This number depends on the controller model and on the controller firmware version.

• The total number of hard drives on the other controller after the drives have been moved must not

exceed the maximum number of supported hard drives for that controller model and firmware version.

• All drives in the array must be moved at the same time.

When all the conditions have been met:

1. Back up all data before removing any drives or changing configuration. This step is required if you

are moving data-containing drives from a controller that does not have a battery-backed cache module.

2. Power down the system.

3. Move the drives.

4. Power up the system.

o If a 1724 or 1727 POST message appears, drive positions were changed successfully and the

configuration was updated.

o If a 1785 POST message appears:

i. Power down the system immediately to prevent data loss. ii. Return the drives to their original locations. iii. Restore the data from backup, if necessary.

5. Verify the new drive configuration by running ORCA or ACU ("Configuring an array" on page 16).

Adding drives

You can add hard drives to a system at any time, as long as you do not exceed the maximum number of drives that the controller supports. You can then either build a new array from the added drives or use the extra storage capacity to expand the capacity of an existing array.

If the hard drives that you intend to add to the system are already configured into logical drives, certain conditions must be met before you add the hard drives to the system. When you have successfully added the hard drives, reset the server so that the controller can recognize the logical drives.

To perform an array capacity expansion, use ACU. If the system uses hot-pluggable drives and ACU runs in the same environment as the normal server applications, you can expand array capacity without shutting down the operating system. For more information, see the Configuring Arrays on HP Smart Array Controllers Reference Guide.

The expansion process is illustrated in the following figure, in which the original array (containing data) is shown with a dashed border, and the newly added drives (containing no data) are shown unshaded. The array controller adds the new drives to the array and redistributes the original logical drives over the enlarged array one logical drive at a time. This process liberates some storage capacity on each physical

Replacing, moving, or adding hard drives 39

drive in the array. Each logical drive keeps the same fault-tolerance method in the enlarged array that it had in the smaller array.

When the expansion process has finished, you can use the liberated storage capacity on the enlarged array to create new logical drives. Alternatively, you can use ACU to enlarge (extend) one of the original logical drives.

Replacing, moving, or adding hard drives 40

Diagnosing array problems

Controller board runtime LEDs

Immediately after you power up the server, the controller runtime LEDs illuminate briefly in a predetermined pattern as part of the POST sequence. At all other times during server operation, the illumination pattern of the runtime LEDs indicates the status of the controller. To determine the controller

Runtime LEDs for E500 model

status, see the appropriate controller-specific section.

LED ID Color Name Comments

1 Amber CR14: Controller Lockup The controller ASIC has locked up and cannot

process any commands.

2 Amber CR13: Drive Failure To determine which drive has failed, check the

Fault LED of each physical drive connected to the

controller. 3 Green CR3: Activity Port 2E is active. 4 Green CR8: Activity Port 1E is active. 5 Green CR5: Command Outstanding The controller is working on a command from the

host driver. 6 Green CR6: Heartbeat When the controller is in good health, this LED

flashes every two seconds. 7 Green CR4: Gas Pedal This LED, together with the Idle Task LED (next

item), indicates the amount of controller CPU

activity. For details, see the following table.

Diagnosing array problems 41

LED ID Color Name Comments

8 Green CR7: Idle Task This LED, together with the Gas Pedal LED

Gas Pedal LED

Idle Task LED status Controller CPU activity

status

Off Blinking 0–25% Blinking Off 25–50% On steadily Off 50–75% On steadily On steadily 75–100%

Runtime LEDs for P700m model

(previous item), indicates the amount of controller

CPU activity. For details, see the following table.

level

LED ID Color Name Comments

1 Amber CR10: Thermal Alert This LED is not used. 2 Amber CR9: System Error The controller ASIC has locked up and cannot

process any commands.

3 Amber CR1: Diagnostics Error One of the server diagnostics utilities has detected

a controller error.

4 Amber CR2: Drive Failure To determine which drive has failed, check the

Fault LED of each physical drive connected to the

controller. 5 Green CR3: Activity Port 2 is active. 6 Green CR4: Activity Port 1 is active. 7 Green CR5: Command Outstanding The controller is working on a command from the

host driver. 8 Green CR6: Controller Heartbeat When the controller is in good health, this LED

flashes every two seconds.

Diagnosing array problems 42

LED ID Color Name Comments

9 Green CR7: Gas Pedal This LED, together with the Idle Task LED (next

10 Green CR8: Idle Task This LED, together with the Gas Pedal LED (previous

Gas Pedal LED status

Idle Task LED status

Off Blinking 0–25% Blinking Off 25–50% On steadily Off 50–75% On steadily On steadily 75–100%

Runtime LEDs for P800 model

item), indicates the amount of controller CPU

activity. For details, see the following table.

item), indicates the amount of controller CPU

activity. For details, see the following table.

Controller CPU activity level

LED ID Color Name Comments

1 Green CR502: Expander Heartbeat This LED flashes every two seconds during normal

operation. If the LED glows steadily, the expander cannot function due to an internal problem. If the LED flashes twice per second, the expander cannot function because the NVRAM is corrupt.

2 Amber CR510: System Error The controller ASIC has locked up and cannot

process any commands.

3 Amber CR509: Diagnostics Error One of the server diagnostics utilities has detected

a controller error.

4 Amber CR500: Drive Failure To determine which drive has failed, check the

Fault LED of each physical drive connected to the controller.

5 Green CR508: Activity Port 4I is active.

Diagnosing array problems 43

LED ID Color Name Comments

6 Green CR507: Activity Port 3I is active. 7 Green CR506: Command Outstanding The controller is working on a command from the

host driver.

8 Green CR505: Controller Heartbeat When the controller is in good health, this LED

flashes every two seconds.

9 Green CR504: Gas Pedal This LED, together with the Idle Task LED (next

item), indicates the amount of controller CPU activity. For details, see the following table.

10 Green CR503: Idle Task This LED, together with the Gas Pedal LED

(previous item), indicates the amount of controller

Gas pedal LED status

Idle task LED status

Controller CPU activity level

Off Blinking 0–25% Blinking Off 25–50% On steadily Off 50–75% On steadily On steadily 75–100%

CPU activity. For details, see the following table.

Battery pack LEDs

Item ID Color Description

1 Green System Power LED. This LED glows steadily when the

system is powered up and 12 V system power is available. This power supply is used to maintain the battery charge and provide supplementary power to the cache microcontroller.

Diagnosing array problems 44

Item ID Color Description

2 Green Auxiliary Power LED. This LED glows steadily when 3.3V

auxiliary voltage is detected. The auxiliary voltage is used to preserve BBWC data and is available any time that the system power cords are connected to a power supply.

3 Amber Battery Health LED. To interpret the illumination patterns of

this LED, see the following table.

4 Green BBWC Status LED. To interpret the illumination patterns of

this LED, see the following table.

LED3 pattern LED4 pattern Interpretation

— One blink every

two seconds

— Double blink,

then pause

— One blink per

second

— Steady glow The battery pack is fully charged, and posted write data is stored in

— Off The battery pack is fully charged, and there is no posted write data

One blink per second

Steady glow — There is a short circuit across the battery terminals or within the

One blink per

— There is an open circuit across the battery terminals or within the

second

The system is powered down, and the cache contains data that has not yet been written to the drives. Restore system power as soon as possible to prevent data loss.

Data preservation time is extended any time that 3.3 V auxiliary power is available, as indicated by LED 2. In the absence of auxiliary power, battery power alone preserves the data. A fullycharged battery can normally preserve data for at least two days.

The battery lifetime also depends on the cache module size. For further information, refer to the controller QuickSpecs on the HP website (http://www.hp.com

The cache microcontroller is waiting for the host controller to communicate.

The battery pack is below the minimum charge level and is being charged. Features that require a battery (such as write cache, capacity expansion, stripe size migration, and RAID migration) are temporarily unavailable until charging is complete. The recharge process takes between 15 minutes and two hours, depending on the initial capacity of the battery.

the cache.

in the cache. An alternating green and amber blink pattern indicates that the

cache microcontroller is executing from within its boot loader and receiving new flash code from the host controller.

battery pack. BBWC features are disabled until the battery pack is replaced. The life expectancy of a battery pack is typically more than three years.

Diagnostic tools

Several diagnostic tools provide feedback about problems with arrays.

Diagnosing array problems 45

• ADU

This utility is a Windows®-based diagnostic tool that sends an email to HP Support when it detects any problems with the controllers and attached storage in a system.

You can install ADU from the Smart Setup media. When installation is complete, run ADU by clicking Start, and then selecting Programs>HP System Tools>HP Array Diagnostic Utility.

For the meanings of the various ADU error messages, see the troubleshooting chapter in the serverspecific service guide.

• Event Notification Service

This utility reports array events to the Microsoft® Windows® system event log and the HP Integrity System Event Log. You can obtain the utility from the HP website (http://www.hp.com/support

• POST messages

Smart Array controllers produce diagnostic error messages (POST messages) at reboot. Many POST messages are self-explanatory and suggest corrective actions. For more information about POST messages, see the troubleshooting chapter in the server-specific service guide.

Diagnosing array problems 46

Electrostatic discharge

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.

Electrostatic discharge 47

Regulatory compliance notices

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.

Regulatory compliance notices 48

• 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.

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.

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.

Canadian notice (Avis Canadien)

Class A equipment This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment

Regulations. Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel

brouilleur du Canada. Class B equipment

Regulatory compliance notices 49

This Class B digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations.

Cet appareil numérique de la classe B respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada.

European Union regulatory notice

This product complies with the following EU Directives:

• Low Voltage Directive 2006/95/EC

• EMC Directive 2004/108/EC

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)

Hewlett-Packard GmbH, HQ-TRE, Herrenberger Strasse 140, 71034 Boeblingen, Germany

BSMI notice

Chinese notice

Class A equipment

Regulatory compliance notices 50

Japanese notice

Korean notice

Class A equipment

Class B equipment

Battery replacement notice

This component uses a nickel metal hydride (NiMH) battery pack.

WARNING: There is a risk of explosion, fire, or personal injury if a battery pack is

mishandled. To reduce this risk:

• Do not attempt to recharge the batteries if they are disconnected from the controller.

• Do not expose the battery pack to water, or to temperatures higher than 60°C (140°F).

• Do not abuse, disassemble, crush, or puncture the battery pack.

• Do not short the external contacts.

• Replace the battery pack only with the designated HP spare.

• Battery disposal should comply with local regulations.

Regulatory compliance notices 51

Batteries, battery packs, and accumulators should not be disposed of together with the general household waste. To forward them to recycling or proper disposal, 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.

Regulatory compliance notices 52

Acronyms and abbreviations

ACU

Array Configuration Utility

ADG

Advanced Data Guarding (also known as RAID 6)

ADU

Array Diagnostics Utility

BBWC

battery-backed write cache

EBSU

EFI-based setup utility

EFI

extensible firmware interface

OBDR

One Button Disaster Recovery

ORCA

Option ROM Configuration for Arrays

POST

Power-On Self Test

Acronyms and abbreviations 53

Index

ACU (Array Configuration Utility) 16, 18 adding drives 39 ADU (Array Diagnostic Utility) 45 Array Configuration Utility (ACU) 16, 18 array controller installation overview 10 Array Diagnostic Utility (ADU) 45 array expansion 39 array, configuring 16 automatic data recovery (rebuild) 36

batteries, replacing 21, 24 batteries, specifications 7 battery pack LEDs 44 battery replacement notice 51 board components, E500 5 board components, P800 6 BSMI notice 50

cable part numbers 14 cables 49 cache, features 8 cache, replacing 21, 29 Canadian notice 49 Chinese notice 50 compatibility of parallel SCSI drives 13 compromised fault tolerance 34 configuration utilities, comparison of 16 configuring an array 16 controller board, features of 5, 7 controller board, installing 10, 12 controller installation, overview of 10 controller LEDs 41 controller options, replacing 21

diagnostic tools 45 drive failure, detecting 33 drive LEDs 32 drive types supported 7 drivers 19

electrostatic discharge 47 environmental requirements 7 error messages 33, 45 European Union notice 50 Event Notification service 19, 45 expanding an array 39 extending logical drive capacity 39

failure, hard drive 33 fault tolerance, compromised 34 Federal Communications Commission (FCC)

notice 48, 49

firmware, updating 15

grounding methods 47 guidelines, replacing hard drives 35

hard drive capacity, upgrading 38 hard drive failure, detecting 33 hard drive LEDs 32 hard drive, failure of 33, 34 hard drive, replacing 35 hard drives, adding 39 hard drives, determining status of 32 hard drives, maximum number of 8 hard drives, types supported 7

data recovery 34, 36 data transfer rate 7 device drivers, installing 19

installation overview 10 internal drives, installing 13

Index 54

Japanese notice 51

Korean notices 51

LEDs, battery pack 44 LEDs, controller 41 LEDs, E500 41 LEDs, hard drive 32 LEDs, P800 43 logical drive capacity extension 39 logical drive, creating 16 logical drives, maximum number of 7

Management Agents, updating 19, 20 modifications, FCC notice 49 moving drives 38

spares, battery pack, part number 8 spares, cable part numbers 14 specifications, controller 7 static electricity 47 status lights, battery pack 44 status lights, controller 41 status lights, hard drive 32 storage capacity, increasing 38 storage devices, connecting 13 summary of installation procedure 10

Taiwan battery recycling notice 52 temperature requirements 7 troubleshooting 41, 45

updating the firmware 15 upgrading drive capacity 38

Option ROM Configuration for Arrays (ORCA) 16,

17 ORCA (Option ROM Configuration for Arrays) 16 overview of installation process 10

parallel SCSI drives, compatibility of 13 physical drives, maximum number of 8 POST error messages 33, 34, 45 power requirements 8 preparation procedures 12

RAID levels supported 8 rebuild, abnormal termination of 37 rebuild, description of 36 rebuild, time required for 36 regulatory compliance notices 48, 51, 52 replacing hard drives 32 replacing the batteries 21, 24 replacing the cache module 21, 29 replacing the controller 29 ROM, updating 15 runtime LEDs 41

Index 55

HP P800 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

HP Smart Array Controllers for HP Integrity Servers User Guide

Contents

Hardware features

E500 model

P700m model

P800 model

Summary of controller features and capabilities

Features common to all controller models

Model-specific features

HP Smart Array E500 Controller features

HP Smart Array P700m Controller features

HP Smart Array P800 Controller features

Overview of the installation procedure

Quick installation procedure (Windows or Linux)

Installing the controller hardware

Preparing the server

Installing the controller board

Connecting storage devices

Connecting internal storage

Connecting external storage

SAS cable part numbers

Updating the firmware

Methods for updating the firmware (Windows or Linux)

Configuring an array

Utilities available for configuring an array

Comparing the utilities

Using ORCA

Using ACU

Installing device drivers and Management Agents

Systems using Microsoft Windows

Installing device drivers

Installing the Event Notification Service

Installing Management Agents

Systems using Linux

Installing Management Agents

Upgrading or replacing controller options

Replacing the E500 cache

Replacing the P700m cache battery

Replacing a P800 cache battery

Replacing the P800 cache module or controller

Replacing, moving, or adding hard drives

Identifying the status of a hard drive

Recognizing hard drive failure

Effects of a hard drive failure

Compromised fault tolerance

Recovering from compromised fault tolerance

Replacing hard drives

Factors to consider before replacing hard drives

Automatic data recovery (rebuild)

Time required for a rebuild

Abnormal termination of a rebuild

Upgrading hard drive capacity

Moving drives and arrays

Adding drives

Diagnosing array problems

Controller board runtime LEDs

Runtime LEDs for E500 model

Runtime LEDs for P700m model

Runtime LEDs for P800 model

Battery pack LEDs

Diagnostic tools

Electrostatic discharge

Preventing electrostatic discharge

Grounding methods to prevent electrostatic discharge

Regulatory compliance notices

Federal Communications Commission notice

FCC rating label

Class A equipment

Class B equipment

Declaration of conformity for products marked with the FCC logo, United States only

Modifications

Cables

Canadian notice (Avis Canadien)

European Union regulatory notice

BSMI notice

Chinese notice