HP 2000 Modular Smart Array Controller Firmware J202P01, J212P01, and J302P01 Release Notes HP Part Number: 537811-008 Published: December 2012 Edition: 8
© Copyright 2009, 2012 Hewlett-Packard Development Company, L.P.
Version: • J202P01 (Fibre Channel) • J212P01 (iSCSI) • J302P01 (SAS) Description This package delivers firmware for HP MSA2000 array controllers. and may include enhanced features or fixes to issues found during use and additional qualification testing. NOTE: Approved companion versions of drive enclosure firmware may also be included in this firmware package.
Product models • HP 2012fc Modular Smart Array (HP MSA2012fc) • HP 2212fc Modular Smart Array (HP MSA2212fc) • HP 2012i Modular Smart Array (HP MSA2012i) • HP 2012sa Modular Smart Array (HP MSA2012sa) Operating systems Operating systems supported for use with HP MSA2000 G1 Controllers (and when installing the binary firmware package): • Microsoft Windows Server 2008 x64 - All Editions • Microsoft Windows Server 2008 W32 - All Editions • Microsoft Windows Server 2003 x64 Edition (Including R2 &
• In the SMU, the enclosure status displayed a false red alert status following a firmware update when the status was actually OK. • In the CLI, for the set advanced-settings command, the single-controller on parameter was added to set Single Controller redundancy mode for a single installed controller. The following enhancements and fixes were incorporated in J202R10, J212R10, and J302R10: • Scrub caused controllers to halt.
• Scrub log entries did not properly display the parity error count after a failover event. • In both the SMU and CLI, metadata was not cleared from all of the selected drives when commanded to do so. • The controller stalled when a vdisk with snapshot and replication volumes was deleted. • A duplicate vdisk was reported after a halted controller recovered. • LUNs were not properly re-mapped after changing vdisk ownership. • The wrong drive was marked as “down”.
• set vdisk command: When changing the vdisk name, the name was rejected as being invalid. • set debug log parameters command: command returned an error message and would not perform the requested action. • expand snap-pool size max command and variable: returned an error message. • clear events command: Improved online help. • set host-wwn-name command: Setting the host-wwn-name did not work as expected. • set iscsi-host host command: Was unable to enter an IQN alias name.
Installation instructions The following sections discuss installing the firmware: • “Installation notes and best practices” (page 8) • “Installing firmware using Smart Components—Windows environments” (page 11) • “Installing firmware using Smart Components—Linux environments” (page 12) • “Installing firmware using the Storage Management Utility (SMU)” (page 13) • “Installing firmware using FTP” (page 14) Installation notes and best practices WARNING! Do not power cycle or restart devices during a
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. • Before installing this firmware: ◦ If updating using a Smart Component, ensure that FTP and telnet are enabled on the arrays being updated. ◦ Create a full backup of system data. (Strongly recommended.
• 10 ◦ Updating array controller firmware may result in new event messages that are not described in earlier versions of documentation. For comprehensive event message documentation, see the most current version of the HP 2000 Modular Smart Array Reference Guide. ◦ The Smart Component update process logs messages to \CPQSYSTEM\Log\cpqsetup.log on the system drive in Windows and /var/cpq/Component.log in Linux.
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 interface (CLI). GUI update method 1. 2. 3. 4. Obtain the firmware package and save it to a temporary directory. Firmware for all HP products is available from the HP Business Support Center website at http://www.hp.com/support/ downloads.
Installing firmware using Smart Components—Linux environments 1. 2. 3. Obtain the firmware package and save it to a temporary directory. Firmware for all HP products is available from the HP Business Support Center website at http://www.hp.com/support/ downloads. Open a Linux command console. 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 Smart Component filename. 4.
Installing firmware using the Storage Management Utility (SMU) 1. 2. Obtain the firmware package and save it to a temporary directory. Firmware for all HP products is available from the HP Business Support Center website at http://www.hp.com/support/ downloads. If using a Smart Component, extract the contents of the Smart Component using one of the following methods: • In Windows—Click Extract on the first screen of the Smart Component. • In Linux—Enter a command using the following syntax: ./CPxxxxxx.
Installing firmware using FTP 1. 2. Obtain the firmware package and save it to a temporary directory. Firmware for all HP products is available from the HP Business Support Center website at http://www.hp.com/support/ downloads. If using a Smart Component, extract the contents of the Smart Component using one of the following methods: • In Windows—Click Extract on the first screen of the Smart Component. • In Linux—Enter a command using the following syntax: ./CPxxxxxx.
Installation troubleshooting If you experience issues during the installation process, do the following: 1. When viewing system version information in the SMU System Overview panel, if an hour has elapsed and the components do not show that they were updated to the new firmware version, refresh the web browser. If version information is still incorrect, proceed to the next troubleshooting step. 2.
Known issues and workarounds This is a cumulative list of known issues and workarounds since the initial firmware release. • How to get out of failure mode: 1. Pull host cables. 2. Power cycle raid-head enclosure. 3. After reboot, wait for disk lights to stop flashing as this indicates de-stage is complete. 4. Plug host cables back in and reconfigure the host to do I/O. • SSH access to the MSA2000 CLI may fail on repetitive attempts to open and close the connection.
At the multipath application level, multipath maps are not getting updated. To update the maps at application level, run the command multipath -v0. This command may take a few minutes with heavy I/O running on the system. • Windows Server 2003 host may hang after failure of a vdisk. The start menu bar goes away, applications may become slow to close, and the system does not reboot (shuts down all programs and closes network connections but hangs at gray screen with mouse cursor still active).
• Issuing the CLI command set cache-parameters read-ahead maximum does not change the setting although the message indicates success. Some cases, where the number of volumes is large or for some reason the available read cache is small, may result in the setting of "maximum" to display a smaller value than expected. The maximum read-ahead cache is calculated by dividing the available read cache by the number of volumes presented.
NOTE: For multipath/dual HBA configurations connected to the same array, run the same command for both HBAs. For example: nl echo “- - –” > /sys/class/scsi_host/host1/scan echo “- - –” > /sys/class/scsi_host/host2/scan For HPDM Multipath configuration, after running the scan command, run the following commands to update the multipath maps in the kernel: /etc/init.d/multipathd restart /sbin/multipath —v3 • There is an issue with DMS where I/O can time out.
