HP 2000 G2 Modular Smart Array Controller Firmware M114P01 Release Notes
HP Part Number: 508849-016
Published: October 2013
Edition: 16

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

Version:  

M114P01

Description

This package delivers firmware for HP MSA2000 G2 array controllers and includes enhanced features or fixes to issues found during use and additional qualification testing.

NOTE: Companion drive enclosure firmware is not included in this controller firmware package. When updating controller firmware, verify that firmware installed on all attached drive enclosures is up-to-date. If needed, upgrade the firmware on the drive enclosures.

Supersedes:  

M114R01

Update recommendation:  

Critical

An issue exists on HP MSA2000 G2 controllers running firmware versions M110R25 or M110R28 that will eventually cause controller configuration information to be lost, with subsequent loss of management capability from that controller. Array management, event messaging, and logging will cease functioning, but host I/O will continue to operate normally. This issue affects the ability to manage the array from the affected controller only; if a partner controller is available, the array can be managed through the partner controller. Because configuration information is stored in non-volatile memory, resetting or powering off the controller will not clear this error. If the issue occurs, the controller must be replaced. This failure mode is time sensitive and HP recommends immediately upgrading firmware on all HP MSA2000 G2 controllers to a version more recent than M110. This is not a hardware issue and proactive replacement of a controller is not a solution. To avoid this condition, you must upgrade your controller to the latest version of firmware. Versions of firmware that resolve this issue are in the following table.

ProductCorrected firmwareAffected firmware
MSA2000 G2 M114P01, M114R01, M113R11, M112R14-03, M112R14-02, M111R06-07, M111R06-04, M111R06M110R25, M110R28

Versioning key: 

AxxxByy-zz

Where the following letters represent release information about the firmware version:

A

MSA model. (TS=P2000 G3, M=MSA2000 G2, J=MSA2000)

xxx

Firmware version. This value changes for major, scheduled releases. Depending on the MSA model, this number may also indicate model protocol.

B

Type of release. (R=Regular release, P=Planned update to a regular release, S=Special release)

yy

Major release number.

-zz

Minor release number.

Product models

HP MSA2000 G2 controllers:

  • HP 2312fc G2 Modular Smart Array (MSA2312fc G2)

  • HP 2312i G2 Modular Smart Array (HP MSA2312i G2)

  • HP 2312sa G2 Modular Smart Array (HP MSA2312sa G2)

  • HP 2324fc G2 Modular Smart Array (HP MSA2324fc G2)

  • HP 2324i G2 Modular Smart Array (HP MSA2324i G2)

  • HP 2324sa G2 Modular Smart Array (HP MSA2324sa G2)

Operating systems

Operating systems supported for use with the HP MSA2000 G2 family of products and when installing the binary firmware package:

  • Citrix XenServer HP Enterprise Editions

  • HP-UX 11i V2 Integrity, HP9000

  • HP-UX 11i V3 Integrity, HP9000

  • Microsoft Windows 2003 and 2003 R2 IA32, x64, IA64

  • Microsoft Windows Server 2008 and 2008 R2 IA32, x64, IA64 (Standard, Enterprise, Datacenter)

  • Microsoft Windows Server 2008 x64 Hyper-V

  • OpenVMS 8.3. OpenVMS 8.3-1H1

  • Red Hat Enterprise Linux 6 x86, x64, IA64

  • Red Hat Enterprise Linux 5 x86, x64, IA64

  • Red Hat Virtualization

  • SuSE Linux Enterprise Server 9, 10, and 11 x86, x64, IA64

  • VMware ESX 3.0.1, 3.0.2, 3.5, 4.0, 5.0 Edition

Operating systems supported for use when installing the Smart Component firmware package:

  • Microsoft Windows Server 2003 x86, x64, IA64

  • Microsoft Windows Server 2008 x86, x64, IA64

  • Microsoft Windows 2008 R2

  • Microsoft Windows 2012

  • Red Hat Enterprise Linux 4 x86, x64, IA64

  • Red Hat Enterprise Linux 5 x86, x64, IA64

  • Red Hat Enterprise Linux 6 x64

  • SuSE Linux Enterprise Server 10 x86, x64, IA64

  • SuSE Linux Enterprise Server 11 x86, x64, IA64

Enhancements and fixes

The following enhancements and fixes were incorporated in M114P01:

  • Disk drives in an MSA70 expansion chassis are not correctly displayed in the SMU.

The following enhancements and fixes were incorporated in M114R01:

  • Improved SMU expander status display in single-controller mode.

  • Improved enclosure renumbering when rescan is performed in single-controller mode.

  • Added event notification when a new path is chosen in best path routing algorithm.

  • Improved handling of drives following vdisk quarantine.

  • Enhanced drive error algorithm to generate an event when a drive drops out of a vdisk.

  • Improved drive LED behavior.

  • Improved identifing the cause for vdisk quarantine scenerios.

  • In the CLI, the Trust command now indicates disks that are out-of-sync, the age of the disk to indicate how far out of sync it is, and disks that were used for reconstruction but where reconstruction did not complete. The user is given the choice to include the out-of-sync or partially reconstructed disks, to exclude them, or to abort. If no out-of-sync or partially reconstructed disks are present, the command continues without a prompt.

  • Improved reporting of SuperCap (SCAP) end of life.

  • Enhanced event reporting of incorrect drive enclosure SAS cabling.

  • Corrected an issue where both controllers could crash due to insufficient resources.

  • Enhanced event messaging from Warning to Critical if a vdisk goes critical and there is no spare configured.

  • Enhanced SMU messaging when clearing drive metadata.

  • Possible data vunerability when booting controller kills surviving controller.

  • Event incorrectly reports the access type as Read/Write instead of No Access.

  • After replacing the controller, all Vdisks go to quarantined (QTOF).

  • Vdisks come up quarantined (QTOF) when controllers are interchanged within the enclosure after a graceful shutdown.

  • Disk failure causing all vdisks to be shown as QTOF.

  • VSS errors and Capi-proxy hangs.

  • Controller hang when scrub is not terminated immediately after a drive failure.

  • Clustering issue with Windows 2008.

  • Creating a vdisk on a controller with Compact Flash Removed results in failure.

  • During reconstruction, if a bad LBA is found, reconstruct will mark the bad LBA with a 0 data bit and complete successfully without any error/event messages passed to the user.

  • Issue with MPIO losing paths due to a SATA drive timeout.

  • Excessive host I/O aborts seen in rare conditions.

  • Both controllers failing with stack overflow.

  • Drive path failed during reboot.

  • French language SMU volume access status displays incorrectly.

  • Array branding is incorrect due to not reading the product ID correctly.

  • Japanese language scrub status displays incorrectly.

  • Boot error due to controller signature mismatch.

  • Fan and PSU data is not shown in logs for MSA70 and D2700.

  • Controller crash when nested topology change occurs.

  • SAS map needs manual intervention to update.

  • Using the same static IP on both management ports.

  • Lost host access due to vdisk ownership change following controller replacement.

  • Host locking issue due to reaching an internal threshold of commands in array.

  • MSA generated incorrect event codes (480). 

  • Drive spinup causing drive PHYs to be lost.

  • Unable to schedule a snapshot in the SMU.

  • Scrub fails to report medium errors to MC Events.

  • SCSI-3 Persistence Reservations can fail in cluster validation tests.

  • Set controller-date command to setup NTP without time zone value.

  • Modified the events 485 and 486 to make consistent with P2000 G3 platform.

  • Bad LBAs are not reported correctly after a vdisk scrub was completed.

  • Single controller crash with page fault.

Installation instructions

The following sections discuss installing firmware:

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 the following best practices:

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.)

  • Schedule an appropriate time to install the firmware:

    • 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.

  • Allocate sufficient time for the update:

    • In single domain systems, approximately 30–60 minutes are required for the firmware to load, plus an additional 15–30 minutes for the system to automatically restart.

    • In dual domain systems, an additional 30–60 minutes is required for the second update, plus an additional 15–30 minutes for the second module to automatically restart.

  • Set the Partner Firmware Update option so that, in dual-controller systems, both controllers are updated. (For SMU and FTP updates only; Smart Components automatically enable/disable the PFU settings as needed.) When the Partner Firmware Update option is enabled, after the installation process completes and restarts the first controller, the system automatically installs the firmware and restarts the second controller. If Partner Firmware Update is disabled, after updating software on one controller, you must manually update the second controller.

During the installation:

  • Monitor the system display to determine update status and know when the update is complete.

After the installation is complete and all systems have automatically restarted:

  • Verify system status in the system's management utility and confirm that the new firmware version is listed as installed.

  • Review system event logs.

  • 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 G2 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.

When reverting to a previous version of firmware, note the following:

  • Ensure that both Ethernet connections are accessible before downgrading the firmware.

  • When using a Smart Component firmware package, the process automatically disables Partner Firmware Update (PFU) and thens downgrade the firmware on each controller separately (one after the other) through the Ethernet ports.

  • When using a Binary firmware package, you must manually disable the Partner Firmware Update (PFU) and then downgrade the firmware on each controller separately (one after the other).

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. 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.

  2. Using Windows Explorer, navigate to the directory containing the download.

  3. Double-click the executable file.

  4. Follow the onscreen instructions.

    When prompted for logon information, enter credentials for an account with management access rights.

CLI update method

Execute the Smart Component by entering the following command:

CPxxxxxxx.exe /target <ip_address> /user <username> /passwd <password> /s

where

CPxxxxxxx.exe

is the downloaded Smart Component filename

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

When prompted for logon information, enter credentials for an account with management access rights.

NOTE: 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.

Installing firmware using Smart Components—Linux environments

  1. 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.

  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 Smart Component filename.

  4. Execute the Smart Component by entering a command similar to the following:

    ./CPxxxxxx.scexe -e --target <ip_address> --user <manage_username> --passwd <manage_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.

    • Use the -h option to see online help for the command.

    • 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.

    When prompted for logon information, enter credentials for an account with management access rights.

Installing firmware using the Storage Management Utility (SMU)

  1. 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.

  2. 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.scexe --unpack=<folder name>

      where

      ./CPxxxxxx.scexe

      represents the Smart Component filename

      <folder name>

      represents the filename of the destination folder for the extracted binary file

  3. Locate the firmware file in the downloaded/extracted folder. The firmware filename is in the following format: mercurysw-MxxxRyy-zz.bin

  4. In single-domain environments, stop all I/O to vdisks in the enclosure before starting the firmware update.

  5. Log in to the SMU and, in the Configuration View panel, right-click the system and then select Tools > Update Firmware.

    A table displays currently installed firmware versions.

  6. Click Browse and select the firmware file to install.

  7. Click Install Controller-Module Firmware File.

    Allow approximately 30–60 minutes for the firmware to load, plus an additional 15–30 minutes 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.

    In dual-controller systems with Partner Firmware Update enabled, allow an additional 30–60 minutes for the second update, plus an additional 15–30 minutes for the second module to automatically restart.

  8. In the SMU display, verify that the expected firmware version is installed on each module.

Installing firmware using FTP

  1. 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.

  2. 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.scexe --unpack=<folder name>

      where

      ./CPxxxxxx.scexe

      represents the Smart Component filename

      <folder name>

      represents the filename of the destination folder for the extracted binary file

  3. Locate the firmware file in the downloaded/extracted folder. The firmware file name is in the following format: mercurysw-MxxxRyy-zz.bin

  4. Using the SMU, prepare to use FTP:

    1. Determine the network-port IP addresses of the system controllers.

    2. Verify that the system FTP service is enabled.

    3. Verify that the user you will log in as has permission to use the FTP interface and has manage access rights.

  5. In single-domain environments, stop I/O to vdisks in the enclosure before starting the firmware update.

  6. Open a command prompt (Windows) or a terminal window (UNIX), and navigate to the directory containing the firmware file to load.

    1. Enter a command using the following syntax:

      ftp <controller-network-address>. (For example: ftp 10.1.0.9)

    2. Log in as an FTP user (user = ftp, password = flash).

    3. Enter a command using the following syntax:

      put <firmware-file> flash

      where <firmware-file> represents the binary firmware filename.

    Allow approximately 30–60 minutes for the firmware to load, plus an additional 15–30 minutes 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.

    In dual-controller systems with Partner Firmware Update enabled, allow an additional 30–60 minutes for the second update, plus an additional 15–30 minutes for the second module to automatically restart.

  7. If needed, repeat these steps to load the firmware on additional modules.

  8. Quit the FTP session.

  9. In the SMU (or CLI) display, verify that the proper firmware version is displayed for each module.

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. If version information does not show that the new firmware has been installed, even after refreshing the browser, restart all system controllers. For example, in the CLI, enter the restart mc both command. After the controllers have restarted, one of three things happens:

    • Updated system version information is displayed and the new firmware version shows that it was installed.

    • The Partner Firmware Update process automatically begins and installs the firmware on the second controller. When complete, the versions should be correct.

    • System version information is still incorrect. If system version information is still incorrect, proceed to the next troubleshooting step.

  3. Verify that all system controllers are operating properly. For example, in the CLI, enter the show disks command and read the display to confirm that the displayed information is correct.

    • If the show disks command fails to display the disks correctly, communications within the controller have failed. To reestablish communication, cycle power on the system and repeat the show disks command. (Do not restart the controllers; cycle power on the controller enclosure.)

    • If the show disks command from all controllers is successful, perform the firmware update process again.

Known issues and workarounds

The following is a cumulative list of known issues and workarounds.

  • Issue: DHCP address is not being set on the array.

  • Workaround: Verify that there is a valid gateway being given by the DHCP server or set a manual IP address and gateway.

  • Issue: Citrix XenServer paths do not automatically appear after reinserting a SAS cable.

  • Workaround: Do the following:

    1. Login to the Citrix XenServer host, dom0.

    2. Change directories to /etc/udev/rules.d/.

    3. Open an editing tool and open the 40-multipath.rules file.

    4. Append the following line to the end of the 40-multipath.rules file: 

      SUBSYSTEM=="block", ACTION=="add", RUN+="/bin/bash -c 'if [[ -h /dev/disk/mpInuse/
$env{ID_SERIAL} && -b /dev/mapper/$env{ID_SERIAL} ]]; then echo add path %k | 
/sbin/multipathd -k > /dev /null; fi'"

    5. Save the 40-multipath.rules file.

    6. Restart the host.

  • 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 completely. 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: 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.

  • 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: 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 customer 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.

  • 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: 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 immediately.

  • 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.

  • 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: 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 an HP c-Class BladeSystem 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: 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.

  • 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 configuration.

Supersedes history

Firmware VersionRelease date
M114R01July 2013
M113R11February 2012
M112R14-03August 2011
M112R14-02May 2011
M111R06-07October 2010
M111R06-04August 2010
M111R06August 2010
M110R28-02April 2010
M110R28March 2010
M110R25December 2009

Effective date

October 2013