HP StorageWorks P2000 Instruction Manual

HP MSA2000 3.5-inch Large Form Factor
Drive Enclosure I/O Module Firmware
O320B07 Release Notes
HP Part Number: 536919-005
Published: June 2011
Edition: Fifth

© Copyright 2009, 2011 Hewlett-Packard Development Company, L.P.

Version:
O320B07
Description
Firmware included in this package adds improvements and corrects issues found during use and
additional qualification testing after initial product release.
Firmware can be installed from any computer running a supported operating system with an Ethernet
connection to the storage array system. For a list of supported operating systems, see Operating
systems.
NOTE: This firmware package may not be needed if you are also installing array controller firmware,
because it may be included in the controller firmware bundle. When installing a controller firmware
bundle that includes both controller and I/O module firmware, the process will update firmware on
controllers in the array enclosure and on I/O modules in attached drive enclosures.
Update recommendation
Recommended
Supersedes
O320B02
Product models
HP MSA2000 3.5-inch Large Form Factor Drive Enclosure I/O Module
Operating systems
Operating systems supported for use with the HP MSA2000 disk enclosure and the binary firmware
package:
•Microsoft Windows Server 2008 and 2008 R2 IA32, x64, IA64 (Standard, Enterprise, Datacenter)
•Microsoft Windows Server 2008 x64 Hyper-V
•Microsoft Windows 2003 and 2003 R2 IA32, x64, IA64
•Red Hat Enterprise Linux 4 x86, x64, IA64
•Red Hat Enterprise Linux 5 x86, x64, IA64
•SuSE Linux Enterprise Server 10 x86, x64, IA64
•VMware ESX 3.0.1, 3.0.2, 3.5, 4.0 Editions
•Citrix XenServer HP Enterprise Edition
•Red Hat Virtualization
•HP-UX 11i V3 Integrity, HP9000
•HP-UX 11i V2 Integrity, HP9000
•OpenVMS 8.3. OpenVMS 8.3-1H1
Operating systems supported for use with the Smart Component firmware package:
•Microsoft Windows Server 2003 x86, x64, IA64
•Microsoft Windows Server 2008 x86, x64, IA64
•Red Hat Enterprise Linux 4 x86, x64, IA64
Description 3

•Red Hat Enterprise Linux 5 x86, x64, IA64
•SuSE Linux Enterprise Server 10 x86, x64, IA64
Enhancements and fixes
•A single faulty drive in an array caused both paths in the system to become unresponsive.
•Corrected the LED display on SATA 2.5-inch drives.
•Fixed an issue that caused a controller to crash when a drive was removed.
•If an I/O module was removed from one enclosure and then hot installed in a different, operational
enclosure, the serial number reported for the enclosure was incorrect.
Installation instructions
The following sections discuss installing the firmware:
•“Installation notes and best practices” (page 5)
•“Installing firmware using Smart Components — Windows environments” (page 5)
•“Installing firmware using Smart Components — Linux environments” (page 6)
•“Installing firmware using the Storage Management Utility (SMU) — MSA2000 G1 environments”
(page 7)
•“Installing firmware using the Storage Management Utility (SMU) — MSA2000 G2 and P2000
G3 environments” (page 8)
•“Installing firmware using FTP” (page 9)
4 Enhancements and fixes

Installation notes and best practices
WARNING! Do not cycle power or restart devices during a firmware update. If the update is
interrupted or there is a power failure, the module could become inoperative. If this occurs, contact
technical support. The module may need to be returned to the factory for reprogramming.
CAUTION: Before upgrading firmware, ensure that the system is stable and is not being reconfigured
or changed in any way. If changes are in progress, monitor them and wait until they are completed
before proceeding with the upgrade.
NOTE: To install this firmware, you must download the firmware package from the HP website and
save the file to your local filesystem.
•As with any firmware upgrade, it is a recommended best practice to ensure that you have a full
backup prior to the upgrade.
•When planning for a firmware upgrade, schedule an appropriate time to perform an online
upgrade.
◦For single domain systems, I/O must be halted.
◦For dual domain systems, because the online firmware upgrade is performed while host I/Os
are being processed, I/O load can impact the upgrade process. Select a period of low I/O
activity to ensure the upgrade completes as quickly as possible and avoid disruptions to hosts
and applications due to timeouts.
•When planning for a firmware upgrade, allow sufficient time for the update.
In single-controller systems, it takes approximately 10 minutes for the firmware to load and
for the automatic controller restart to complete.
◦
◦In dual-controller systems, the second controller usually takes an additional 20 minutes to
update, but may take as long as one hour.
Installing firmware using Smart Components — Windows environments
This is a self-extracting executable module. You can execute this module from the Windows graphical
user interface (GUI) or the command line console (CLI).
GUI option
1. Place the downloaded firmware package in a temporary directory.
2. Using Windows Explorer, navigate to the directory containing the download.
3. Double click the executable file.
4. Follow onscreen instructions.
NOTE: When prompted for logon information, enter credentials for an account with management
access rights.
CLI option
Execute the Smart Component by entering the following command: CPxxxxxxx.exe /target
<ip_address> /user <username> /passwd <password> /s
where:
•ip_address is the management IP address of the array controller
•username is the username account with management rights
•password is the password for username
Installation instructions 5

Instead of command line parameters you can use the following DOS environment variables:
•oa_address: set this variable for the IP address of array controller
•oa_username : set this variable for the username of array controller
•oa_password : set this variable for the password of array controller
NOTE: When prompted for logon information, enter credentials for an account with management
access rights.
Installing firmware using Smart Components — Linux environments
1. Place the downloaded firmware package in a temporary directory.
2. Open a Linux command console.
3. From the directory containing the downloaded file, enable execute access to this model by entering
chmod +x CPxxxxxx.scexe, where CPxxxxxx.scexe represents the downloaded file.
4. Execute the Smart Component by entering a command similar to the following:
./CPxxxxxx.scexe --target <ip_address> --user <username> --passwd
<password>
NOTE:
•Use the -e or -f option when flashing a device, even if it is up to date.
•Use the -g option when downgrading.
•For details on supported command options, see the online help by executing the command
./CPxxxxxx.scexe or ./CPxxxxxx.scexe -h.
•If the user name or password contains an exclamation mark (!), enclose the string in single
quotes or enter a backslash (\) before the exclamation point. For example, '!manage' or
\!manage.
5. Follow onscreen instructions.
NOTE: When prompted for logon information, enter credentials for an account with management
access rights.
6 Installation instructions

Installing firmware using the Storage Management Utility (SMU) — MSA2000 G1
environments
1. Place the downloaded firmware package in a temporary directory.
2. If using a Smart Component, extract the contents of the Smart Component.
In Windows — Click Extract on the first screen of the Smart Component.
In Linux — Enter ./CPxxxxxx.scexe --unpack=<folder name> to extract the contents of
the Smart Component to the <folder name> folder. (For example,./CP123456.scexe
–unpack=extract_here)
3. Locate the firmware file in the extracted folder. The firmware filename is in the following format:
O3xxBxx-01.bin
4. In single-domain environments, stop all I/O to the vdisks before starting the firmware update.
5. Login to the SMU and select Manage > Update Software > Enclosure Firmware > Update Firmware.
6. Select the type of expansion modules to update. Expansion modules that have the same
manufacturer, model, and firmware revision are considered the same type. For example, two
identical expansion modules with different firmware revisions are considered to be different types.
7. Click Select Type And Continue.
Enclosure processors of the selected type are listed, with the following information displayed for
each enclosure:
•Device WWN : The drive enclosure's node World Wide Name.
•Address : The channel and loop ID of the expansion module.
•Manufacturer : The expansion module manufacturer.
•Model : The expansion module model number.
•Rev : The revision code for the firmware currently in the expansion module.
If more than two enclosure modules are listed, a Select All check box is displayed.
8. Select the enclosure modules to update.
NOTE: All enclosures in an array configuration must use the same firmware version.
9. Click Continue.
10. Click Browse and select the firmware file to install.
11. Click Load Device Firmware File.
12. In the SMU display, verify that the proper firmware version appears for each updated module.
Installation instructions 7

Installing firmware using the Storage Management Utility (SMU) — MSA2000 G2 and
P2000 G3 environments
1. Place the downloaded firmware package in a temporary directory.
2. If using a Smart Component, extract the contents of the Smart Component.
In Windows — Click Extract on the first screen of the Smart Component.
In Linux — Enter ./CPxxxxxx.scexe --unpack=<folder name> to extract the contents of
the Smart Component to the <folder name> folder. (For example,./CP123456.scexe
–unpack=extract_here)
3. Locate the firmware file in the extracted folder. The firmware filename is in the following format:
O3xxBxx-01.bin
4. In single-domain environments, stop all I/O to the vdisks before starting the firmware update.
5. Login to the SMU and, in the Configuration View panel, right-click the system and select Tools >
Update Firmware.
A table displays currently installed firmware versions.
6. Select the enclosure modules to update.
NOTE: All enclosures in an array configuration must use the same firmware version.
7. Click Browse and select the firmware file to install.
8. Click Install Expansion-Module Firmware File.
Wait for progress messages to specify that the update is complete.
9. In the SMU display, verify that the proper firmware version appears for each module.
8 Installation instructions

Installing firmware using FTP
1. Place the downloaded firmware package in a temporary directory.
2. If using a Smart Component, extract the contents of the Smart Component.
In Windows — Click Extract on the first screen of the Smart Component.
In Linux — Enter ./CPxxxxxx.scexe --unpack=<folder name> to extract the contents of
the Smart Component to the <folder name> folder. For example,./CP123456.scexe
–unpack=extract_here
3. Locate the firmware file in the extracted folder. The firmware filename is in the following format:
O3xxBxx-01.bin
4. Do one of the following:
•To update all modules, proceed to step 5.
•To update specific modules, do the following to determine the address of each module to
update:
In the CLI, display the addresses by entering the show enclosures command. The needed
data is displayed in the columns labeled EMP A CH:ID Rev and EMP B CH:ID Rev.
5. In the SMU, prepare to use FTP:
a. Determine the network-port IP addresses of the system controllers.
b. Verify that the system FTP service is enabled.
c. Verify that the user you will log in as has permission to use the FTP interface and has
management access rights.
6. In single-domain environments, stop al I/O to the vdisks before starting the firmware update.
7. Open a command prompt (Windows) or a terminal window (UNIX), and navigate to the directory
containing the firmware file to load.
a. Enter ftp <controller-network-address>. (For example: ftp 10.1.0.9)
b. Log in as an FTP user (user = ftp, password = flash).
c. Enter one of the following commands:
•To update all detected modules, enter: put <firmware-file> encl flash. For
example: put O3xxBxx.bin encl flash
•To update a specific module, enter: put <firmware-file>
encl:<channel-ID>:<EMP-number> flash. For example: put O3xxBxx.bin
encl:0:15 flash
8. If needed, repeat these steps to load the firmware on additional modules.
9. Quit the FTP session.
10. In the SMU display, verify that the proper firmware version appears for each module.
Supersedes history
Release dateFirmware version
June 2011O320B07
June 2010O320B02
February 2010O300B28
Effective date
June 2011
Supersedes history 9