'hpsa' - A SCSI-based Linux device driver for HP Smart Array Controllers

12
Deploying the hpsa driver
Ideally, you should begin the transition to the hpsa driver during an OS installation. You also can make the change later
in certain cases, such as when changing Smart Array controller hardware.
Deploying hpsa during a new OS installation
The optimum time for deploying hpsa occurs during the installation of a new operating system. This avoids nearly all
issues with device name changes.
Preparing for the installation
Smart Array devices may appear as /dev/sd*.
Installation is simpler if you limit the configuration to storage devices necessary for the install.
RHEL 6
RHEL 6 installations are the simplest case for hpsa deployment. If you install an hpsa-supported controller in the server,
the controller will automatically begin using the hpsa driver during the installation. If you need the cciss driver instead,
select and install one of the cciss-supported controllers as shown in Table 1.
SLES 11 SP1
ProLiant Gen8 servers and controllers require the use of and updated hpsa driver, available in a Bootable Driver Kit (BDK)
package from SUSE
4
. Use the BDK to replace the older, experimental hpsa driver (version 2.0.2-1) shipped with SLES 11
SP1, which should not be used for any controllers.
For ProLiant servers before Gen8, use the cciss driver for all supported Smart Array controllers.
Transitioning to hpsa after the OS installation
HP recommends deploying hpsa only during OS installations.
In some environments, a post-installation transition from cciss to hpsa can be complicated. But you can still transition to
the hpsa driver if you mount the affected devices using the persistent naming method and if you do not use any of the
devices as the boot device.
4
See link at end of paper.