beautypg.com

5 firmware – HP 6Gb SAS Switch for HP BladeSystem c-Class User Manual

Page 21

background image

5 Firmware

As part of a routine system maintenance program, periodically check firmware versions installed
on all devices in your solution, including the SAS BL Switch. Updated firmware may include
additional features and functions, performance enhancements, support for newly released hardware,
or fixes to known issues.

HP SAS BL Switch firmware updates can be performed using the HP Smart Update Firmware DVD
or the HP Virtual SAS Manager (VSM) utility.

Smart Update Firmware DVD ISO and Firmware Release Sets— These tools deliver tested,
compatible sets of firmware for components included in BladeSystem solutions and are designed
to help manage firmware interdependencies between HP BladeSystem Components. These
tools use executable SmartComponent firmware packages. For information about updating
firmware using the Smart Update Firmware DVD or an individual SmartComponent package,
see the HP BladeSystem Firmware Maintenance page

nl

(

http://h18004.www1.hp.com/products/blades/components/c-class.html

).

HP Virtual SAS Manager utility—This utility is embedded in the HP 6Gb SAS BL Switch firmware
and is the software application used to create hardware-based zone groups to control access
to external SAS storage. The VSM uses an image firmware file (.img). For information about
the VSM, see the HP 6G Virtual SAS Manager User Guide.

IMPORTANT:

When two HP 6Gb SAS BL Switches are installed in the same row of an enclosure, make sure
that they are running the same firmware version.

Before updating switch firmware, HP strongly recommends backing up the configuration for
safekeeping. For more information, see the HP Virtual SAS Manager User Guide, available
on the 6Gb SAS BL Switch page of the HP Support Center website (

http://www.hp.com/go/

hpsc

).

Regardless of firmware updating method, HP strongly recommends that firmware updates be
performed during a scheduled maintenance window (single-domain and dual-domain
deployments).

21