HP StorageWorks 2000fc - G2 Modular Smart Array Instruction Manual

HP StorageWorks MSA2000 G2
Firmware Release Notes
Part number: 508849–004
Fourth edition: December 2009

Version: M110R25
Description
This smart component provides firmware for MSA2000 G2 Storage Array Controllers. The firmware
update can be performed on any computer running a supported operating system that has an Ethernet
connection to the MSA2000 G2 Storage Array system. For supported operating systems, see Operating
systems.
Update recommendation Optional
Supersedes This firmware is an update for all previously released firmware for the HP StorageWorks
MSA2000 G2 family of products.
Product models
•HP StorageWorks MSA2312fc G2
•HP StorageWorks MSA2312i G2
•HP StorageWorks MSA2312sa G2
•HP StorageWorks MSA2324fc G2
•HP StorageWorks MSA2324i G2
•HP StorageWorks MSA2324sa G2
Operating systems
•Microsoft Windows 2003 x64 Edition
•Microsoft Windows 2003 x64 Edition (Itanium)
•Microsoft Windows 2008
•Microsoft Windows 2008 x64
•Microsoft Windows 2008 Itanium
•Red Hat Enterprise Linux 4
•Red Hat Enterprise Linux 5
•SUSE Linux Enterprise Server 10
Enhancements
•Made general improvements to the logging feature.
•Added disk firmware update support for future versions of 2TB SATA disk drives.
•Added some optimizations for snapshots.
•Improved the integration with Common Information Model (CIM) by adding support for single
ported drive reporting.
•Added an analyze function to the background scrub utility that provides information to help isolate
issues.
•Improved the dynamic sparing feature so that it will use a free disk even when there is metadata
from a previous vdisk on the disk.
HP StorageWorks MSA2000 G2 Firmware Release Notes 3

•Improved ability to communicate with a controller after it has been shut down, to improve restart
behavior.
•Enhanced the SNMP community string to support strings that contain dash and underscore char-
acters.
•Improved the SNMP Notification page in internationalized systems that uses non-ASCI characters,
such as Japanese.
Fixes
•Fixed a problem detecting the number of disk drive bays in an expansion enclosure.
•Fixed the issue that all drives spun up concurrently when a single power supply was in use. If only
a single power supply is functioning, disk drives now spin up in a staggered manner.
•Fixed a situation where a SATA disk drive may be dropped from a vdisk during a firmware up-
grade.
•Fixed a problem where user credentials were reset to default values when controller A was replaced.
•Fixed an issue where the vdisk number was mis-reported.
•Fixed an issue where a firmware upgrade did not error out when an invalid package was used.
•Fixed an issue that allowed a user to set the independent cache mode to an unsupported config-
uration.
•Fixed an issue that a reconstructing vdisk would report as completed when just beginning the re-
build.
•Fixed an issue where a failed disk drive might cause a controller to stall.
•Fixed an issue where correctable ECC errors caused a scrub failure.
•Fixed a problem where a scrub error was reported when, in fact, the background scrub was
manually stopped.
•Fixed an issue where an offline vdisk might not be appropriately quarantined when an array is
powered up.
•Fixed an issue where the array did not correctly report all supported persistent reservation types.
•Fixed an issue where deleting a vdisk failed.
•Fixed an issue that, while deleting a snapshot, could lead to an error and cause the snapshot to
not be deleted.
•Fixed an issue where a quarantine event caused a scrub error.
•Fixed an issue where media errors were not leading to a disk drive being removed from service.
•Fixed a situation where IO requests during a failover would fail out with the following error message:
“Request not supported”.
•Fixed a problem where failover did not occur, even when a component failed.
•Fixed a situation where reconstruction progress stuck at 0%.
•Fixed a rare timing issue that lead to a drive enclosure not being discovered on a reboot.
•Fixed an issue that lead to drive enclosure firmware update failure.
•Fixed a problem where a LUN reset did not clear same sector reads.
•Fixed an issue where a controller failover lead to IP settings being lost.
•Fixed an issue where a Windows OS might see a volume that does not exist at LUN 0.
•Fixed an issue where both storage controllers became unresponsive when a disk issue caused a
general protection fault to be delivered to both controllers.
•Fixed an issue that could cause a storage controller to crash while I/O is being written to a RAID
6 vdisk that is in a critical state.
•Fixed a timing issue that lead to a controller becoming unresponsive.
4

•Fixed an issue where SAS port values were reported incorrectly.
•Fixed issues with cold temperature monitoring.
•Fixed an issue where a drive that reports a SMART error may not be downed appropriately.
•Fixed a problem where a drive failure during initialization could cause a controller to crash.
•Fixed a problem where a controller was brought down by a disk reset from the partner controller.
•Fixed the licensing engine to prevent an invalid license from loading.
•Fixed an issue where an uncorrectable ECC error caused a controller to crash.
•Fixed an issue where a controller would stop responding when disks with media errors are in the
system.
•Fixed an issue that lead to a vdisk faulting when controller A was replaced.
•Fixed an issue where a vdisk using mirroring would fail to initialize when the maximum size was
requested.
•Fixed a problem where a controller crash could be triggered by switching the owning controller
of a vdisk when snapshot volumes were resident on the vdisk.
•Fixed an issue where the controller would stop responding when a snapshot with a duplicate name
was requested.
•Fixed an issue where a RAID 10 vdisk in quarantine had a utility would fix a parity error even
though there was a missing member of the vdisk.
•Fixed a problem where an erroneous SuperCap failure was reported.
•Fixed a rare issue where controller temperature was displayed incorrectly .
•Fixed an issue where the default LUN was not released for reuse when the owning volume was
deleted in a single controller array.
•Fixed an issue of inconsistent behavior when moving drives from one drive enclosure to another
drive enclosure.
•Fixed an issue on RAID 10 and RAID 50 vdisks that kept spares from being deleted.
•Fixed an issue that lead the enclosure health status to be reported incorrectly.
•Improved the initialization time for RAID 1 and RAID 10 vdisks.
•Fixed an error on the iSCSI controller where a controller pair would lose connection and force
one of the controllers to shut the other down.
•Fixed an issue where LUNs were presented in both PDA (Peripheral Device Addressing) and VSA
(Volume Set Addressing) modes.
•Fixed an issue with SNMP incorrectly reporting certain traps.
•Fixed a problem where the loop IDs of the controllers were not properly displayed.
•Fixed an issue where part and serial number were not displayed correctly.
•Fixed a problem where online help was formatting incorrectly (CLI).
•Added a function to allow SNMP test traps to be sent (CLI).
•Fixed a problem that caused enabling NTP to fail because of an improper condition (CLI).
•Fixed an issue where set disk-parameters was not accepting valid input (CLI). (Example:
set disk-parameters smart off)
•Fixed an issue where a set job-parameters utility-priority command returned an
error of "Error: Invalid FC topology" (CLI).
•Fixed an issue that lead to inconsistent vdisk status reporting (CLI).
•Fixed various cosmetic issues (GUI).
•Fixed an issue where changing volume names allowed the user to change the name to a volume
that is already in use (GUI).
•Fixed Help to provide the correct location for Save Logs feature (GUI).
HP StorageWorks MSA2000 G2 Firmware Release Notes 5

•Fixed some issues in the Japanese version of the GUI.
•Fixed an issue where the SMU page was not updating after creating volumes (GUI).
•Fixed an issue where the user inactivity timeout was not working properly (GUI).
Important notes
WARNING!
Do not power cycle or restart during the firmware update. This can result in loss of capabilities for
the unit.
CAUTION:
Updating Array controller firmware with only one Array controller requires the MSA2000 system to
be offline. In a single-controller system, updating firmware causes all disks to be temporarily
inaccessible. Stop I/O to vdisks before updating the firmware.
IMPORTANT:
Reverting the firmware version back to M100R18-05 from the M110 code branch requires HP technical
support.
NOTE:
•Smart Components are available for this firmware. These are located on the Windows and Linux
software deliverables page for this storage product.
•It takes approximately 10 minutes for the firmware to load and for the automatic restart to complete
with the first controller. With a second controller, the full process time is approximately 25 minutes.
•All firmware flash progress messages are logged to \CPQSYSTEM\Log\cpqsetup.log on
the system drive in Windows and /var/cpq/Component.log in Linux.
•The Smart Component manages the FTP & Partner Firmware Update (PFU) enable / disable settings.
•Updating array controller firmware may result in receiving new event messages that are not de-
scribed in earlier versions of documentation. For comprehensive event message documentation,
see the most current version of the HP StorageWorks 2000 G2 Modular Smart Array Reference
Guide .
Installation instructions
When planning for a firmware upgrade, select and schedule an appropriate time to perform an online
upgrade. For redundant controller systems, to ensure the success of an online upgrade, selecting the
appropriate time is essential. Because the online firmware upgrade is performed while host I/Os are
being serviced, the I/O load can impact the upgrade process. Selecting a period of low I/O activity
will ensure the upgrade completes as quickly as possible, and will avoid disruptions to hosts and
applications due to timeouts.
6

CAUTION:
Before upgrading controller firmware, ensure that the storage system configuration is stable and is
not being reconfigured or changed in any way. If configurations changes are in progress, monitor
them and wait until they are completed before proceeding with the upgrade.
IMPORTANT:
As with any firmware upgrade, it is a recommended best practice to ensure that you have a full
backup prior to the upgrade.
NOTE:
To download this module from the HP website, right-click the link and save the file to your local
filesystem. You cannot double-click the link.
Smart Component installation instructions for 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 Smart Component package in a temporary directory.
2. Using Windows Explorer, navigate to the directory containing the download.
3. Double click the executeable file.
4. Follow onscreen instructions.
NOTE:
When prompted for logon information, enter credentials for an account with management
access rights.
CLI option
The following syntax can be used to invoke at the command line:
cpxxxxxxx.exe /target <MSA2300_IP> /user <USER_NAME> /passwd <PASSWORD>
/s
where:
•MSA2000_IP is the management IP address of the MSA2300 controller
•USER_NAME is the username account with manage rights
•PASSWORD is the password for username
Instead of command line parameters you can use the following DOS environment variables:
HP StorageWorks MSA2000 G2 Firmware Release Notes 7

•OA_ADDRESS: set this variable for the IP address of MSA2300 controller
•OA_USERNAME : set this variable for the username of MSA2300 controller
•OA_PASSWORD : set this variable for the password of MSA2300 controller
NOTE:
When prompted for logon information, enter credentials for an account with management access
rights.
Smart Component installation instructions for Linux environments
1. Place the Smart Component 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 typing
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 <manage_username> --passwd
<password>
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.
Smart Component installation instructions using Storage Management Utility
(SMU)
WARNING!
Do not cycle power or restart the controller 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.
1. Extract the contents of the smart component.
In Windows —Select the Extract button on the first screen of the smart component.
In Linux —./CPXXXXXX.scexe --unpack=<folder name> extracts the contents of the smart
component to <folder name> folder. For example,./CP001123.scexe –unpack=extract_here
2. Locate the firmware file in the extracted folder. The firmware filename is in the following format:
mercurysw-M110R25-01.bin
3. If the system has a single controller, stop I/O to vdisks before starting the firmware update.
8

4. In the MANAGE section, under UPDATE SOFTWARE > controller software. The tables titled Load
Software to RAID Controller A show the currently installed versions.
5. Click Browse and then select the firmware file to install.
6. Click Load Software Package File. It takes approximately 10 minutes for the firmware to load
and for the automatic restart to complete on the controller you are connected to. Wait for the
progress messages to specify that the update has completed. If Partner Firmware Update
is enabled, allow an additional 20 minutes for the partner controller to be updated.
7. Verify that the proper firmware version appears for each controller module.
Smart Component installation instructions using FTP
NOTE:
It takes approximately 10 minutes for the firmware to load and for the automatic restart to complete.
Progress messages are displayed in the FTP interface during that time. Wait for the progress messages
to specify that the firmware load has completed. If the system Partner Firmware Update (PFU)
option is enabled, allow an additional 20 minutes for the partner controller to be updated. No
messages are displayed in the FTP interface during PFU.
1. Extract the contents of the smart component.
In Windows —Select the Extract button on the first screen of the smart component.
In Linux —./CPXXXXXX.scexe --unpack=<folder name> extracts the contents of the smart
component to <folder name> folder. For example,./CP001123.scexe –unpack=extract_here
2. Locate the firmware file in the extracted folder. The firmware file name is as follows:
: mercurysw-M110R25-01.bin
3. Using the MSA2000 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 manage
access rights.
4. 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 put <firmware-file> flashFor example: put J210P19-02.bin flash
Binary file installation instructions using Storage Management Utility (SMU)
WARNING!
Do not perform a power cycle or controller restart during a firmware update. If the update is interrupted
or there is a power failure, the module might become inoperative. If this occurs, contact technical
support. The module might need to be returned to the factory for reprogramming.
HP StorageWorks MSA2000 G2 Firmware Release Notes 9

1. Obtain the appropriate firmware file and download it to your computer or network.
2. If the system has a single controller, stop I/O to vdisks before starting the firmware update.
3. In the Configuration View panel, right-click the system and select Tools > Update Firmware. The
tables titled Current Versions of Controller Module A and Current Versions of Controller Module
B show the currently installed versions.
4. Click Browse and select the firmware file to install.
5. Click Install Controller-Module Firmware File. It takes approximately 10 minutes for the firmware
to load and for the automatic restart to complete on the controller you are connected to. Wait
for the progress messages to specify that the update has completed. If Partner Firmware Update
is enabled, allow an additional 20 minutes for the partner controller to be updated.
6. Verify that the proper firmware version appears for each controller module.
Binary file installation instructions using FTP
NOTE:
It takes approximately 10 minutes for the firmware to load and for the automatic restart to complete.
Progress messages are displayed in the FTP interface during that time. Wait for the progress messages
to specify that the firmware load has completed. If the system Partner Firmware Update (PFU) option
is enabled, allow an additional 20 minutes for the partner controller to be updated. No messages
are displayed in the FTP interface during PFU.
1. Download the firmware file to your computer or network.
2. Using the MSA2000 G2 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 manage
access rights.
3. 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 put <firmware-file> flash. For example: put M110R25–01.bin flash
Known issues and workarounds
This is a cumulative list of known issues and workarounds for this release.
•Issue: Installing a firmware image that is not supported for the array in the Storage Management Utility
(SMU) Update Firmware page may cause issues in the SMU.
•Workaround: Ensure that the correct array firmware image is used when upgrading firmware. If an incorrect
firmware image is loaded, the SMU may display a status of loading firmware or updating firmware for a
long period, and then display a status of the controller is unresponsive, which is normal during rebooting.
If the SMU stays in this cycle, restart the controller. The SMU may report that the firmware as been updated
successfully, but it has not been updated because the firmware is not actually supported.
10

•Issue: The default password for the ftp user is incorrectly documented in the MSA2000 G2 documentation
as !flash.
•Workaround: The correct default password for the ftp user is flash.
•Issue: When the temporary license agreement checkbox is clicked, the confirmation pop-up is displayed.
If the cancel button is clicked on the confirmation pop-up, the checkbox is not cleared.
•Workaround: To clear the checkbox, click the checkbox again to remove the check and click the cancel
button on the confirmation pop-up.
•Issue: HP MSA70 enclosure single port drives connected to the MSA2000 G2 present a single point of
failure.
•Workaround: If your configuration requires full data redundancy, HP highly recommends that you do NOT
connect MSA70 2.5“single port drives to MSA2000 G2 configurations. If there is a MSA70 controller
failure in this configuration, all data on the MSA70 single port drives is lost.
•Issue: Changes to default Fibre Channel HBA driver parameters are required for proper controller failover.
•Workaround: The Fibre Channel HBA parameters were omitted from the MSA2000 G2 documentation.
For controller failover to function properly, change the default driver parameters as follows:
•QLogic —Port Down Retry Count = 60, Link Down Timeout = 60
•Emulex —LinkTimeOut = 60, NodeTimeOut = 60
•Issue: Storage Management Utility is slow or reports success when no action was taken.
•Workaround: When there are many volumes, vdisks, and disks in a configuration, the performance of the
initial load of the SMU can be slower than expected. You can navigate the interface for any information
currently loaded. The “barber pole”above the main information pane will be moving if the data is being
updated. Additionally, there have been instances in which the front and rear graphics do not fill in com-
pletely. If you use the tabular view in this scenario, all tasks can be completed. If the SMU reports that an
illegal action succeeds (for example, extending a vdisk with a disk which is smaller than the smallest disk
in the current vdisk), the action did not actually succeed. Be sure to verify that all actions are completed
as expected.
•Issue: RHEL 5.x failback issue after controller restart.
•Workaround: If a RHEL 5.x server is processing heavy I/O it might be possible for the I/O to not failback
correctly when an array controller is restarted. To avoid this situation, HP recommends performing tasks
such as replacing failed controllers or updating firmware during periods with light I/O profiles.
•Issue: The Storage Management Utility Restore System Defaults function is not available.
•Workaround: The Restore System Defaults function is listed in the User Guide as an available feature. This
function has been removed from the SMU and is only available as an advanced option in the Command
Line Interface (CLI).
•Issue: Controller might need to be manually restarted after a firmware update.
•Workaround: During a firmware update, the controller will sometimes need to be manually restarted.
•Issue: Linux Boot from Storage (BFS) configurations can become unresponsive on a controller failure due
to incorrect multipathing setup.
•Workaround: When configuring a Linux BFS setup, be sure to explicitly follow the documentation for the
Linux release and Device Mapper. The configuration should be tested for path and controller failure prior
to being placed in a production environment. A functioning operating system while all controllers/paths
are up is not indicative of a fully functional multipathed operating system drive.
•Issue: I/O timeouts reported by HP-UX 11.23 and PVLinks.
•Workaround: On HP-UX 11.23 with PVLinks, the operating system might report many I/O timeouts under
heavy load. These do not affect data integrity. The issue is being investigated.
HP StorageWorks MSA2000 G2 Firmware Release Notes 11

•Issue: VMWare reports a retry (unit attn) in the log.
•Workaround: VMWare reports a retry (unit attn) whether I/O is running or not. This issue does not affect
data integrity, is being investigated, and is expected to be corrected in a future firmware update.
•Issue: Disk channel errors reported by drives on an MSA70.
•Workaround: When an MSA2000 G2 array is using MSA70s as expansion JBODs, disk channel errors
might be reported. These errors do not affect data integrity and are being investigated for correction in a
future update.
•Issue: Inconsistent or unexpected behavior when the system is exposed to more than 64 host ports.
•Workaround: When an MSA2000 G2 array is exposed to more than 64 hosts, the first discovered host
on the list is removed without warning. This host can be added back in manually. There are a maximum
of 64 hosts allowed in the host list at any time. You can also use fibre channel zoning to limit the number
of exposed host ports to 64 or fewer.
•Issue: In larger configurations the Windows DSM can have a slow failback time.
•Workaround: Under very heavy load or large configurations the DSM can take many minutes to failback
returning paths. This issue is being investigated by Microsoft for enhancement.
•Issue: HP-UX possible path loss.
•Workaround: Under very heavy load a path might unexpectedly disappear from the operating system.
This is being investigated and will be mitigated in a future release. To avoid this situation, configure multiple
paths to all volumes when possible.
•Issue: Windows operating system performance can be negatively impacted if the recommended array
configuration is not followed for BFS configurations.
•Workaround: When designing a Windows BFS configuration, it is a best practice to have the operating
system partitions on a separate vdisk than the data partitions. This helps spread the load to different disks
and allows faster access to both data and operating system partitions concurrently.
•Issue: Windows Clusters with Emulex HBAs have cluster failover issues.
•Workaround: On Windows clusters with Emulex HBAs there have been instances in which a cluster resource
was not moved to another node when an array controller was shut down. This issue is being investigated
by all vendors involved and a resolution will be available as soon as possible. Qlogic cards have not ex-
hibited this issue. Path loss does not trigger this issue.
•Issue: Integrity Server ia64 Windows BFS must use Smart Setup 6.2 or later.
•Workaround: Integrity BFS for Windows ia64 will install but then will not find the boot LUN on a reboot.
To correct this issue, use Smart Setup 6.2. If this is not available from the support Web site, a call to cus-
tomer support is required.
•Issue: Command Line Interface cannot display locale-specific output correctly.
•Workaround: Ensure that the telnet client is UTF8–compliant in order to display non-English character sets
correctly.
•Issue: Unable to set UDID on SCC device at LUN 0 on Open VMS.
•Workaround: It is currently not possible to set the UDID on an SCC device at LUN 0. This is different than
other HP products and is not currently supported. Avoid this issue by not using a LUN 0 for Open VMS.
12

•Issue: Windows and Linux are limited to discovering fewer than the maximum number of LUN IDs that are
presentable from an MSA2000 G2 (512 LUNs)
•Workaround: Windows and Linux operating systems do not support enumerating all of the LUN IDs
presented from an MSA2000 G2 array. Windows supports the discovery of LUN IDs 0 - 254; Linux supports
the discovery of LUN IDs 0 –255. Note that SAS arrays do not support presenting a LUN on ID 0.
To allow a single Windows or Linux host to discover more LUNs than the LUN ID limitation of 255 on
Windows and 256 on Linux, the array must be configured to present two different LUNs using the same
LUN ID. The array supports this configuration only if the LUN is presented on a subset of the host ports.
For example, present Volume Vol-001 as LUN ID 1 on ports A1 and B1 and present Volume Vol-300 as
LUN ID 1 on ports A2 and B2.
•Issue: Changing both IP addresses causes problems accessing Storage Management Utility.
•Workaround: Changing the IP address for both controllers concurrently can cause the controllers to become
unavailable. First, change the IP address on the controller that you are not logged into. Then, log in to that
controller to verify connectivity. After verifying connectivity, change the IP address on the original controller.
•Issue: Windows DiskPart utility clean command may hang.
•Workaround: When the VDS/VSS provider is loaded on a host, the clean function in DiskPart sometimes
hangs. Microsoft hotfix KB 968736 resolves this issue.
•Issue: The set network-parameters CLI command silently fails if the controller parameter is absent.
•Workaround: This parameter is not optional and must be specified to correctly set networking parameters.
The online help incorrectly states that this parameter is optional.
•Issue: Volumecopy operations can fail if a dual controller system is in a degraded state.
•Workaround: Resolve the degraded state issue.
•Issue: SunCluster using SCSI3 reservations are not supported with iSCSI and SAS environments.
•Workaround: This issue currently being investigated by HP. An alternative is to use 2–node clusters with
SCSI2 reservations in the MSA2000 G2 SAS and iSCSI protocol controllers. The Fibre Channel MSA2000
G2 has full SunCluster capabilities.
•Issue: In the SMU, recurring scheduled events may not occur.
•Workaround: Verify that the end schedule date and time are correct and later than the start schedule date
and time.
•Issue: Unable to create new schedule due to the error The schedule is expired.
•Workaround: Verify that the start time for a scheduled event is a valid time when submitting it.
•Issue: During rollback with modified data, snapshot volumes are inaccessible.
•Workaround: Plan rollback operations when access to snapshots are not required or unmount the snapshot
prior to rollback.
•Issue: After flashing firmware from the SMU, some fields may not display the updated information immedi-
ately.
•Workaround: Close all browser interfaces to the SMU after the firmware update has completed and then
re-establish the connections.
•Issue: While updating the firmware using the SMU, the browser may lose the connection.
•Workaround: Close all browser interfaces to the SMU and then re-establish the connections. If the problem
persists, restart the Management Controller from the CLI.
HP StorageWorks MSA2000 G2 Firmware Release Notes 13

•Issue: When an enclosure has a status of OK, the enclosure health reason is displayed as “The enclosure
health is not known”.
•Workaround: The health reason field is only populated when the enclosure is in a degraded or fault status.
•Issue: Following a reboot, the device mapper multipath may not detect all MPATH devices correctly.
•Workaround: Issue the command multipath —v3 to recover missing devices.
•Issue: In a Solaris iSCSI environment, path failover and failback functionality may not work correctly.
•Workaround: Refer to SUN CR numbers 6764779 and 6844558.
•Issue: Some entries in the SMU and CLI are not localized properly for all languages.
•Workaround: HP is continually updating localized content.
•Issue: Some configuration changes under heavy I/O may return a communication error.
•Workaround: Retry configuration changes during a period of lower I/O.
•Issue: Some cached data in the browser may not be updated while navigating through the SMU.
•Workaround: Press CTR + F5 to refresh or log out and back into the SMU.
•Issue: The tree view for a vdisk in SMU may not function properly.
•Workaround: Click the ++ symbol at the top of the tree view. This refreshes the screen and enables the
tree view.
•Issue: In single controller mode, some event log descriptions can indicate a second controller.
•Workaround: These messages can be safely ignored.
•Issue: During drive firmware upgrade, all volumes are taken offline to preserve data integrity.
•Workaround: Plan drive firmware updates during a maintenance window.
•Issue: In a c-Class blade environment, VMWare may fail I/O during failover operations.
•Workaround: The VMWare kernel parameter ResetOnFailover must be set to 0 in order for array
failover to work properly.
•Issue: SMU may display a flashing background or other display issues if left open for an extended amount
of time.
•Workaround: Do not maintain an open SMU session for more than 24 hours. Log out of the SMU when
SMU tasks are complete.
•Issue: SMU may lose authentication if the browser refresh button is clicked.
•Workaround: Log back in to re-establish authentication.
•Issue: In the SMU Enclosure Overview page, the column Serial Number is mislabeled; it should be labeled
WWID.
•Workaround: This will be resolved in a future release.
•Issue: The serial number for a volume returned by the SMU and CLI does not match the serial number returned
by VPD data.
•Workaround: Serial numbers are shown in different formats. The last 16 digits of the serial number are
unique for each volume and match between the CLI, SMU, and VPD data.
•Issue: You can not create volumes for OpenVMS using the Provisioning Wizard or Create Volume Set pages
of the SMU.
•Workaround: Volumes for OpenVMS may only be created using the Create Volume page of the SMU.
14

•Issue: If an error occurs before the provisioning wizard is complete then partial commits of configuration
changes will be made. The provisioning wizard cannot be used to complete the configuration changes.
•Workaround: Use the Create Volume Set and Default Mapping pages of the SMU to complete the config-
uration.
•Issue: Flash operation on an MSA2000IOM connected behind an MSA2000 G2 Storage Array running
M110R21-01 firmware fails
•Workaround: N/A
Effective date
December 2009
HP StorageWorks MSA2000 G2 Firmware Release Notes 15

16