HP MSA 1040/2040 Controller GL200P002 Firmware Release Notes


This package delivers firmware for the HP MSA 1040/2040 Controller array and includes enhanced features and fixes to issues found during use and additional qualification testing.

HP Part Number: 764118-008
Published: April 2015
Edition: 6

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.


Microsoft® and Windows® are trademarks of the Microsoft group of companies.


This package delivers firmware for MSA 1040/2040 array controllers and MSA 2040 and P2000 drive enclosures.

IMPORTANT: For a list of supported companion drive enclosure firmware, see “Additional devices”.

Versioning key:


The following letters represent firmware version release information:

Firmware versionDescription

MSA model. (GL=MSA 1040/2040; TS=P2000, M=MSA2000 G2)


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


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


Major release number.


Minor release number.

Update recommendation

Update Recommendation: Recommended

Supersede information

Supersedes: GL200R007

Product models

HP MSA 1040 Controllers

  • HP MSA 1040 FC Controller

  • HP MSA 1040 1G iSCSI Controller

  • HP MSA 1040 10G iSCSI Controller

HP MSA 2040 Controllers

  • HP MSA 2040 SAN Controller

  • HP MSA 2040 SAS Controller

Operating systems

This release is supported on the following operating systems:

  • Microsoft Windows Server 2008

  • Microsoft Windows Server 2008 R2

  • Microsoft Windows Server 2008 Hyper-V

  • Microsoft Windows Server 2012

  • Microsoft Windows Server 2012 R2

  • Microsoft Windows Server 2012 Hyper-V

  • Red Hat Enterprise Linux 5

  • Red Hat Enterprise Linux 6

  • SuSE Linux Enterprise Server 11

  • HP-UX 11.31

  • VMware ESXi 5.0/5.1/5.5


Languages supported for this release:

  • English

  • Spanish

  • French

  • German

  • Italian

  • Korean

  • Japanese

  • Dutch

  • Chinese (traditional)

  • Chinese (simplified)

Additional devices

HP MSA 1040/2040 array controller enclosures support the cascading of drive enclosures. The following table lists supported drive enclosure models and firmware versions.

HP MSA 1040/2040 array controller firmwareCascaded drive enclosure modelRecommended drive enclosure firmware
GL200HP P2000 drive enclosuresS200B31
HP MSA 2040 drive enclosuresS200B31
HP D2700 drive enclosure0149

IMPORTANT: After updating array controller firmware or after connecting new drive enclosures to an existing controller enclosure, verify the firmware compatibility of all devices. If needed, obtain and install the supported controller or drive enclosure firmware. Firmware is available for download from the following websites:

HP MSA security considerations

This firmware contains security updates. After any security update is applied to your array, HP highly recommends that you change user passwords.

This version of firmware disables unsecured web access by default. This setting is applied on new controllers from the factory, or after using the restore defaults CLI command. Use the secured web access (HTTPS) to avoid access issues.


The following features were added or enhanced in controller firmware GL200P002:

A new Sector Format property has been added to support 512-byte native sector size (512n) disks, 512-byte emulated sector size (512e) disks, or a mix of those sector formats. For consistent and predictable performance, HP recommends not mixing drives of different rotational speed or sector size types (512n, 512e).

PFU (Partner Firmware Update) functionality was enhanced to be more robust.

Updated OpenSSL to version v1.0.1l.

The following features were added or enhanced in controller firmware GL200:

Added virtualized storage capabilities including read cache, thin provisioning, automatic tiering, wide striping, and snapshots of snapshots.

Added new SMU (Storage Management Utility) v3 to manage virtualized storage as well as traditional storage which includes topic based navigation, advanced sort and filter capability, and increased ease of use capabilities.


The following issues were fixed in controller firmware GL200P002:

A controller may fault occasionally during Remote Snap.

Controllers may fault occasionally during regular array operation.

In some cases, firmware update from GL105 to GL200 may fail to report unwritable cache.

Missing a few steps in SMU v3 Help for Configuration Wizard.

Unable to make changes to mapping from host port to volume in SMU v2.

Scrub errors seen occasionally with Raid10 disk groups.

Some display texts in non-English locales are displayed in English.

The following issues were fixed in controller firmware GL200:

Changing email notification settings using the CLI command set email-parameters enabled Include Logs unless the include-logs parameter was specifically set to disabled.

Erroneous events sent for USB flash drive.

Erroneously showed PSU status as OK when the PSU fan had failed.

Unable to delete replication snapshot as per retention setting on remote system.

A disk was erroneously reported as unsupported when it failed.

A 314 event did not occur for unknown drive failures.

Changing vdisk ownership did not warn of possible data loss or unavailability if volumes in the vdisk were mapped to hosts.

D2700 FRU Status erroneously shown as Absent.

In a single controller configuration that includes disk enclosures, the IOMs that are not connected to the controller report bad health on their expansion ports

The Usage property in the CLI command show disks is not showing DRSC when a disk is being scrubbed using the background scrub utility.

Current SSH users remain logged in after disabling the SSH protocol.

The Management Controller may reset if the passphrase is not supplied with the CLI command set fde-lock-key.

Setting network parameters for the partner controller may not immediately be reflected on the partner controller.

Changing the IP configuration on the other controller may cause a short disruption of connectivity to the Management Controller that the command was run on.

When Internet Explorer 10 is being used, the Provisioning Wizard may not display the available RAID levels correctly.

During a firmware upgrade, Event 545 may be generated with an unknown error.

The SMU appears to be frozen if volume identifying information contains illegal characters.

Deleting a vdisk may not delete all associated schedules.

Intermittently after setting enclosure parameters, the settings may revert to previous values.

The confirmation response to the CLI command set disk repurpose shows an incorrect disk number.

Resolved the following security issues:

  • CVE-2014-0224 - SSL/TLS MITM vulnerability

  • CVE-2014-3508 - Information leak in pretty printing functions

  • CVE-2014-3511 - OpenSSL TLS protocol downgrade attack

  • CVE-2014-3512 - SRP buffer overrun

  • CVE-2014-3567 - Session Ticket Memory Leak

  • Allowed fallback to SSL 3.0; now blocks the ability for a man-in-the-middle attacker to force a protocol downgrade

Issues and workarounds

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

Issue: English strings are seen in other locales.

Workaround: None

Issue: Failed to set date and time through the SMU v3 system → Configuration → System Settings → Date, Time panel.

Workaround: If neither the Enabled or Disabled NTP radio button is selected, select one setting and then set the date and time.

Issue: Unable to change mapping in locales other than English.

Workaround: Choose a new Access type, which will appear in English in the drop-down for all locales. Once an English value is selected, the mapping can occur.

Issue: Replication wizard help not displayed for step 3 of 5 in locales other than English.

Workaround: Read the help in the English locale or reference the SMU Users Guide.

Issue: Configuration wizard help not displayed for step 7 of 9 and 8 of 9 in locales other than English.

Workaround: Reference the SMU Users Guide.

Issue: Creating a new virtual disk-group when existing linear disk-groups exist that are named A, B, a, or b causes the virtual disk-group to be unmanageable.

Workaround: Change the name of existing linear disk-groups to something other than A, B, a, or b, and remove and re-add the virtual disk-group.

Issue: The CLI command set prompt is not allowing & to be set as a prompt.

Workaround: Use another prompt in place of &.

Issue: In Internet Explorer, when Help button is clicked in SMU, it can take a couple minutes for Help window to be populated with content.

Workaround: Eventually the Help window will be populated, it may take a couple minutes or use a different supported browser.

Issue: In SMUv3 the online help for all locales except English does not show that NRAID, RAID-0 and RAID-3 vdisks can only be created using the CLI.

Workaround: None.

Issue: The Replicate volume description pane is displayed as blank for single controller system in the SMU when selecting Replicate Volume from the Volume Provisioning menu.

Workaround: Create replication set through CLI.

Issue: The Create Volume/Volume-set page highlights Access field in red (only once per volume).

Workaround: Click on the access drop-down and select appropriate value.

Issue: On SMU popups, buttons aren't enabled until clicking outside of the data entry fields or selecting Tab.

Workaround: Select the Tab key or click outside of the entry fields in order to enable the buttons.


Issue: When trying to create a virtual disk-group larger than 64 TB an error will be shown and the disk-group will not be created.

Workaround: Create virtual disk-groups of 64 TB or smaller size to add to pools.


Issue: After swapping controllers in the same array enclosure both controllers may show the same management IP.

Workaround: Correct the IP for each management port one at a time.


Issue: When the SNMP community string is left blank in the SMU, the previous value will be used.

Workaround: Do not leave the SNMP community string blank.


Issue: An error occurs disabling Drive Spin Down with a non-zero delay.

Workaround: When disabling the drive spin down feature, you must also set the delay to zero.


Issue: Partner Firmware Update can fail if there is a health issue in the system.

Workaround: Determine array upgrade health by running the CLI command check firmware-upgrade-health. Address the health issue and reload the code on the controller


Issue: If the code load health checker determines that firmware should not be loaded, no event will be logged.

Workaround: Determine code load health by running the CLI command check firmware-upgrade-health.


Issue: Performance statistics may show a value of 0 if one controller is in a shutdown state.

Workaround: Bring the controllers back to active-active operation and accurate statistics will be available after up to 15 minutes.


Issue: There is no option to turn on/off LEDs through SMU v3.

Workaround: Use the CLI or SMU v2 to turn on/off LEDs.


Issue: The description of RAID type is not displayed in the hover tip in IE in SMU v3.

Workaround: Lookup RAID type through help, or use another supported browser.


Issue: There can be a discrepancy between the replication image count in volume and snap-pool properties.

Workaround: Use the snap-pool properties to verify the counts.


Issue: Interface changes may not occur when using the modify user panel in the SMU.

Workaround: Use the CLI to change interface settings.


Issue: SMU v3 Home Page graphical representation on the bottom left side of the page shows the system health as OK for two controllers when there is single controller in the system.

Workaround: Use the system tab to determine health of the installed controller.


Issue: In the SMU a volume with less than 500 GB rounds to 0 TB when snapshots are enabled.

Workaround: Use the CLI if you require snapshots of smaller volumes.


Issue: Some initiator entries may remain when deleting large number of initiators in the SMU v2 interface.

Workaround: Retry deleting the remaining initiators.


Issue: When requesting historical statistics, through the SMU or CLI, if the requested time frame is greater than 8 hours and 15 minutes, the start time will shift forward. The larger the time frame, the more the start time shifts.

Workaround: When requesting historical data, do not request a time frame larger than 8 hours. This will prevent any averaging of data points, and any time shifting.


Issue: The login page displays Warning The system is currently unavailable when partner controller is shutting down.

Workaround: Allow the partner controller to shutdown and failover completely and retry accessing the system.


Issue: After completing the SMU configuration wizard, date and time changed events is generated even though no modification to date and time was done.

Workaround: Recommend enabling NTP on the array.


Issue: When the health is degraded, the information can be truncated when hovering over the system health on the SMU v3 Home Page.

Workaround: Use the System Topic to investigate the health of the components.


Issue: System table view refreshes automatically, going back to first pages after 10-15 seconds.

Workaround: None.


Issue: Transfer rate is not shown in SMU v3 when selecting a disk in the system topic.

Workaround: Transfer rate can be found in the CLI using the detail option to the show disks command, or in SMU v2 under the enclosures.


Issue: Mapping a large set of linear disk-group based volumes may take longer in SMU v3 compared to SMU v2.



Issue: SNMP event strings use the disk-group terminology in place of vdisk.

Workaround: None.


Issue: Attempting to map volumes above the limit of the controller can produce an error of An invalid LUN was specified.

Workaround: None.


Issue: The reset all-statistics command didn't reset the pool and disk statistics.

Workaround: Reset the pool and disk statistics independently.


Issue: The SMU v3 Home page does not display the units in MB when a user’s unit preference is changed to MB.

Workaround: The Home page automatically scales based on the sizes in use.


Issue: Thin provisioning notification may not be sent when a virtual pool is smaller than 500 GB.

Workaround: None.


Issue: The Browse button fails to open the file selection pop up in the license screen.

Workaround: Refresh the browser.


Issue: The error message for setting or creating a host name does not list \ as an unallowed character.

Workaround: Do not use a \ character in the host-name.


Issue: D2700 power supply voltages are displayed as all zeros.

Workaround: None.


Issue: The CLI command show enclosures is missing D2700 enclosure ports in XML.

Workaround: None.


Issue: Remote Snap fails to create remote volume when the locale of the remote system is set to something other than English.

Workaround: Ensure that the remote system is set to English locale.


Issue: The CLI command show sas-link-status is missing D2700 SAS ports.

Workaround: None.


Issue: The CLI command show expanders is not reporting D2700 enclosure expanders.

Workaround: None.


Issue: The SMU v3 Create Virtual Volume panel uses Copies terminology instead of Number Of Volumes.

Workaround: Copies should be treated synonymously with Number Of Volumes.


Issue: An incomplete error message is displayed when invalid characters are given in the Sender name for email notifications stating that a space is included.

Workaround: Check the help to find the invalid characters.


Issue: The output of show disks detail command returns Drive Spin Down Count as 1 for SSDs.

Workaround: Ignore the Drive Spin Down Count for SSD's.


Issue: Related Snapshots shown in the Volumes Pane in the SMU v3 does not list all the descendant snapshots of the volume.

Workaround: Select the each descendent snapshot to see the related snapshots.


Issue: The message incorrectly states The specified volume was not found when creating a task to reset a virtual volume snapshot.

Workaround: The message should state that this operation is not supported for virtual volumes.


Issue: The CLI displays invalid pool details for virtual disk groups temporarily.

Workaround: This is a temporary state that will resolve itself.


Issue: Attempting to modify an existing replication schedule shows an error that Start date/time cannot be set to earlier than the current date/time.

Workaround: Enter a data/time in the future for the new Start time for modified schedule.


Issue: The filter of Severity is truncated if there are two events in the event list.

Workaround: If the event list has been filtered down to only one or two events and the filter menu is truncated, close the event list dialog and re-open it.


Issue: The SMU v3 is not rendering several elements properly in IE 10 and IE 11.

Workaround: Disable Compatibility View in IE 10 and IE 11.


Issue: Mapping over 500 volumes at the same time in the SMU v3 may not complete all mappings.

Workaround: If possible, perform large number of volume mappings in chunks to avoid timeout and other errors. When mapping a large number of volumes from the SMU, avoid refreshing the browser while the operation is in progress.


Issue: Thin provisioning information reported in the SMU v3 and the CLI may not be in sync.

Workaround: Use the CLI to track more immediate size data. Allocated and available storage has a 3-5 minute delay in the SMU.


Issue: The SMU v3 create initiator window shows message in red text.

Workaround: The initial validation error message does not affect functionality, proceed with entering the ID and name and the initiator will be created.


Issue: After creating a new volume, the volumes table is not updated for multiple seconds.

Workaround: The table will be updated after a short time.


Issue: The performance statistics request never completes.

Workaround: Do not request more than two weeks of data at a time. If more than two weeks of data is needed, data will need to be requested in two week periods.


Issue: The SMU help does not show internal IP addresses in use by the array.

Workaround: Use the CLI command help set network-parameters to view internal IP addresses in use by the array.


Issue: Using an initiator nickname of all is incorrectly allowed and will delete all initiators if the nickname is used in the delete initiators command.

Workaround: Do not create an initiator with a nickname of all. If a nickname of all has been used, delete the initiator using the unique identifier.


Issue: The profile for an initiator is not shown in the SMU v3.

Workaround: Use the CLI to view the profile of the initiator.


Issue: Initiator profiles can not be set in the SMU v3.

Workaround: Use the CLI to modify initiator information.


Issue: The CLI command show provisioning does not display the correct information if the ports parameter is utilized and the volumes were mapped using symmetric port assignment.

Workaround: Use other CLI commands to show mapping information such as show volume-maps.


Issue: In rare circumstances after creating virtual disk groups one or more of them may appear in the wrong pool in the SMU v3 Pools Topic.

Workaround: Refresh the browser window and SMU should reflect the disk groups in their proper pools.


Issue: If an error occurs during virtual disk group creation it may not be possible to remove it through the SMU v3.

Workaround: Use the CLI to remove a disk group that cannot be removed through the SMU v3.


Issue: The SMU v3 host group mapping is very slow when mapping more than 192 initiators.

Workaround: Use less than 192 initiators when doing host group mapping.


Issue: The SMU Install License Panel refers to temporary license functionality, but this functionality is not available.

Workaround: Request temporary licensing from your representative.


Issue: After adding disk-groups the performance charts displayed in the SMU v3 show incorrect data.

Workaround: Gather disk statistics using the CLI or reset the performance statistics.


Issue: Unable to create snapshot using Now or Scheduled option after creating a schedule on another volume when using IE 11.

Workaround: Use a different browser than IE 11, or refresh the browser session.


Issue: Unable to change the End Schedule details when modifying a snapshot schedule when using IE 11.

Workaround: Use a different browser than IE 11, or refresh the browser session.


Issue: In the Performance tab, the sample period is referred to in seconds but the data is shown in milliseconds.

Workaround: None.


Issue: Unable to select SNMPv3 Privacy Type in locales other than English in the SMU v3.

Workaround: Use the CLI to set the SNMPv3 Privacy Type.


Issue: Strings are truncated in some cases in the SMU v3 when locales other than English are used.

Workaround: Use the CLI for the functionality or the English locale in the SMU v3.


Issue: In non English locales the SMU v3 does not refelect the NTP enabled state when it has been enabled in CLI.

Workaround: Utilize the CLI for the accurate state of whether NTP is enabled.


Issue: Some panes and drop down menus may not display correctly in locales other than English.

Workaround: Use the CLI to complete operations or use the English locale.

Issue: Remote Snap schedule fails to create if the system time minutes is greater than the scheduled start time minutes.

Workaround: Create the schedule when the system time minutes is less than the scheduled start minutes.

Issue: In the SMU v2, events are not sorted in either ascending or descending order when the code column is clicked in the system events.

Workaround: The codes are sorted alphabetically, so 100 will appear before 2 in the list. Manually search for the desired code.

Issue: In the SMU v2 the turn on LEDs  option is disabled in Vdisk Overview → Disks panel.

Workaround: Perform the function in the Enclosure view.

Issue: Removing a controller from the remote system can cause a condition where the remote system object cannot be deleted.

Workaround: Add back the missing controller, so that it is a dual controller system again. If using a replacement controller, ensure that both controllers have the same software version. Wait up to 3 minutes and retry the delete remote-system. In the rare case that it does not work, restart both systems and retry.

Issue: When creating a second replication set the Apply button is not working on IE11 browser.

Workaround: Refresh the browser.

Issue: Unable to enable or disable encrytped SMI-S using the configuration wizard in the SMU v3.

Workaround: Use the CLI, SMU v2, or SMU v3 system services panel to enable or disable encrypted SMI-S.

Issue: The SMU does not send managed log email when the gateway is

Workaround: Set an appropriate gateway address.

Issue: Help is not available for step 8 of 9 of configuration wizard.

Workaround: The help for Host Ports is available from System → Host Ports Settings.

Issue: Unable to finish the configuration wizard in SMU v3 if an invalid iSNS address is supplied in step 8 of the wizard even if the value is corrected.

Workaround: To get out of the configuration wizard, click Cancel or uncheck the Enable iSNS option, then apply the correct iSNS.

Issue: Error message is not displayed when an incorrect date/time is entered through configuration wizard step 2 of 9.

Workaround: If the Next button is not enabled on step 2 of the configuration wizard, check that the date/time is correct.

Issue: When the UID LED button on a D2700 disk enclosure has been physically pressed (enabled) attempting to turn off the LED in the user interface will result in an error message stating the LED is already in the requested state.

Workaround: Physically press (disable) the UID LED button on the D2700.

Issue: Snapshot schedules didn't begin until an MC restart or schedules that had no associated tasks were deleted.

Workaround: Remove the schedules that had no associated tasks or restart the MC.

Issue: D2700 IO Module Ports are not shown in the CLI command show expander-status.

Workaround: None.

Issue: D2700 Standby Power State is not clearly reported.

Workaround: None.

Issue: Array firmware SmartComponents may not upgrade the partner controller after successfully upgrading the accessible controller when only one management controller is available.

Workaround: Retry the SmartComponent. If that still fails, verify the array health by running the command check firmware-upgrade-health and correct the health issues.


Issue: When adding large number of hosts to a host group the command may fail.

Workaround: Add hosts to the host group in smaller increments.


Issue: The CLI, SMU, or SMI-S interfaces become slow or unresponsive.

Workaround: Restart the Management Controller from either the CLI or SMU on an operating controller.


Issue: Prior to the successful completion of a volume-related task, such as creating a snapshot, a volume copy, or replicating a volume, one or two ERROR events might be displayed.

Workaround: Examine the events. If the task action subsequently occurs, ignore the Scheduler: The specified volume was not found event.


Issue: When several vdisks are deleted, a "ghost" vdisk with a serial number of all zeroes briefly appears.

Workaround: Wait a few minutes for the "ghost" vdisk to disappear on its own.


Issue: Event logs do not reflect the successful upgrade of disk enclosure firmware on the other controller even though the upgrade was successful.

Workaround: Use the CLI command show enclosures to ensure that the EMP versions are correct. In the SMU, refresh the browser session and check the EMP versions.


Issue: A phantom FC host briefly appears after hosts are renamed on iSCSI ports.

Workaround: None. The phantom FC host with an id of all zeroes will disappear shortly.


Issue: The CLI command show enclosures reports health is OK when it should be DEGRADED due to leftover drives.

Workaround: Use the CLI command show system to observe the correct health.


Issue: Deleting a replication set might affect other schedules related to the primary volume.

Workaround: When you delete a replication set, ensure that any other schedules or tasks related to the same primary volume are not adversely affected. If they are affected, re-configure the affected schedule or task to the intended configuration.


Issue: In the Create Volume screen in the SMU, if the Volume size slider is moved all the way to the right, the Enable Snapshots checkbox is checked, and the Standard Policy button is selected, the maximum value in the size field might be greater than possible and the action will fail.

Workaround: Ensure that the size specified in the Create Volume screen does not exceed 80% of the vdisk available space.


Issue: After the firmware is updated on the array, the SMU might freeze or become nonresponsive.

Workaround: Restart the browser session.


Issue: SMI-S Indication subscription to the array fails.

Workaround: Run the CLI command reset smis-configuration both and then retry the operation. After running this command, any hosts registered via SMI-S need to be registered again.


Issue: SMI-S does not support default mapping.

Workaround: Use explicit mapping.


Issue: Saving disk performance statistics with a specific time range fails when you use the FTP interface.

Workaround: Use the Reset or Save Disk Performance Statistics panel of the SMU to collect statistics, or do not restrict the log to a specific time range.


Issue: After explicitly mapping a LUN, other hosts that are not mapped to the LUN report seeing the Reported LUN Data Has Changed unit attention.

Workaround: No workaround is required. This will not affect data access on the other hosts.


Issue: A Vdisk going offline is reported as an Error-level event.

Workaround: To ensure that the event is sent to any software that is monitoring the array, configure the notifications to a minimum notification level of Error.


Issue: You are unable to delete users who have manage-level capabilities but do not have CLI access.

Workaround: From another manage-level user, enable CLI access for the user to be deleted and then delete the user.


Issue: If servers are connected to the array running SLES 11 SP3 and using Emulex FC HBAs, these servers might not correctly reinstate paths into the correct multipath device.

Workaround: Change the following in the multipath.conf file:

  1. Remove the uid_attribute ID_SERIAL entry in the defaults section if it exists.

  2. Add the following to the defaults section:

    getuid_callout /lib/udev/scsi_id --whitelisted --device=/dev/%n

  3. Restart the multipath service.


Issue: In locales other than English, the Date, Time panel might not reflect the correct NTP settings.

Workaround: In the SMU, ensure that the NTP is set to the desired setting (enabled or disabled) each time any changes are made in the Date, Time panel. Otherwise, use the following CLI commands to correctly verify and set the NTP settings:

  • show controller-date

  • set controller-date

  • set ntp-parameters


Issue: Event messages might include erroneous characters appended to the end of schedule or task names.

Workaround: Derive the real task or schedule name by ignoring the erroneous characters at the end of the string.


Issue: When Number of volumes to create is changed in the Provisioning Wizard, the corresponding Volume size slider value is updated but the text box is not updated.

Workaround: The volumes are created based on the calculation used to update the Volume size slider value. If you need a different Volume size than the slider calculation, move the slider to the appropriate size or manually update the text box with the size.


Issue: Windows 2008 R2 SP1 Clustered Hyper-V VMs might experience loss of paths due to high load with a high number of LUNs assigned to the Cluster and VMs.

Workaround: Where possible, reduce the number of LUNs used on each cluster node or exposed VM. After any path loss situations, verify that the correct number of paths exist.


Issue: Attempts to enable the identification LED on a D2700 enclosure do not work.

Workaround: None.


Issue: In the SMU, mapping a volume to a LUN results in a generic Error: Command failed response.

Workaround: Verify that the LUN number is not already in use for that host, or in the case of default mapping, that the LUN number is not already in use on that port.


Issue: When using Internet Explorer, if you attempt to upload a firmware image where the path contains a dot (.), the upload fails with an error that the file is the wrong type.

Workaround: Ensure that the file path does not contain a dot (.), or use another supported browser.


Issue: In the SMU, the Full Disk Encryption (FDE) passphrase does not accept a phrase that contains spaces.

Workaround: If spaces are required in the passphrase, use the CLI commands to set the passphrase.


Issue: In the SMU Full Disk Encryption Settings panel, the action buttons might not become active immediately after you enter required information on the page.

Workaround: Use the Tab key on the keyboard, or click any white space on the screen to change the focus, which enables the buttons.


Issue: After repurposing a drive in the SMU, the Repurpose Disk List might take a longer time than expected to refresh the information.

Workaround: Refresh the browser, or log out and log back into the browser.


Issue: Using Internet Explorer 9, you are unable to apply setting changes in Configuration > Advanced Settings > Disk, because the EMP Polling Rate is blank.

Workaround: Select a valid value from the EMP Polling Rate drop-down rather than leaving it blank, and click Apply. The system default EMP Polling Rate is 5 seconds.


Issue: The HP Integrity Smart Array P411 SAS Controller only brings up one PHY when connected to the array, which causes the array to show the port as degraded.

Workaround: None.


Issue: The SMU might not allow a snap-pool to be deleted if master volumes associated with that snap-pool are deleted while the vdisk containing the snap-pool is offline, such as after a multi-disk raid failure.

Workaround: Use the CLI delete snap-pool command to delete the snap-pool.


Issue: The Install License menu item, and other features such as Create Snapshot, might not appear in the SMU.

Workaround: Refresh the web browser. If the problem persists, clear the browser cache and restart the browser.


Issue: The values of the SNMP Notification page are not updated correctly in the SMU after clicking Apply.

Workaround: Refresh the browser.


Issue: Modifying the start time of an existing one-time schedule to earlier than the current time causes the schedule not to run at the scheduled time.

Workaround: When modifying a schedule, do not set the start time of a one-time schedule to earlier than the current time.


Issue: The CLI command show frus might show an OK status for a RAID controller that is not installed.

Workaround: None.


Issue: Single-controller systems converted from dual-controller systems might show unhealthy components from the missing controller.

Workaround: Restart the management controller.


Issue: The user session is not terminated when the user is deleted.

Workaround: After deleting the user, immediately restart both management controllers.


Issue: Some of the mapping panels in the SMU might default the access mode to no-access while others default to read-write.

Workaround: Always ensure that the access mode for mapping is set as desired before clicking Apply.


Issue: Unable to create a weekend suspend task on a weekend day in the SMU.

Workaround: Use the CLI to schedule a suspend task.


Issue: After a firmware upgrade, the bundle version might not reflect all component versions of the bundle correctly.

Workaround: Reload the firmware bundle.


Issue: When the system has an unwriteable cache, components of a firmware upgrade fail.

Workaround: Ensure that there is no unwriteable cache, and reload the firmware bundle.


Issue: Online help text for a replication volume status of Offline indicates that the volume can be accessed.

Workaround: Online help should read, Offline: the volume cannot be accessed and is unusable due to an error.


Issue: When you are logged in to SMU with Japanese locale, the Table of Contents for help text is not valid.

Workaround: None.


Issue: When a system is configured as single-controller, controller B ports are also displayed in the output of CLI command show ports.

Workaround: None.


Issue: Online LUN addition is not seen by clients using the P711m, P712m, or P721m controllers and the HP cciss driver in RHEL 5 operating systems.

Workaround: Use the rescan volumes command on the /proc subsystem of the cciss driver to force a rescan of the cciss driver, and then update multipath. For example:

echo "rescan volumes" > /proc/driver/cciss/cciss1

multipath -v 0


Issue: Online LUN addition is not seen by clients using the P711m, P712m, or P721m controllers and the HP cciss driver in SLES 11 SP2 and SP3 operating systems.

Workaround: Use the hpacucli or hpssacli utility to force the SmartArray to rescan for LUNs. Do this by issuing a command for the utility to list the logical drives from the SmartArray that is connected to the MSA storage.

NOTE: There will be no logical drives found in the utility, but the LUNs will now be discovered in the operating system. Use the following commands in the utility: ctrl slot=X ld all show, where X is the slot number for the SmartArray connected to the MSA. Then force multipath to create to devices by running multipath -v 0.


Issue: When you use explicit LUN mapping, long IQN names for the iSCSI Initiator can cause the array to map the LUN incorrectly. A predefined area is used to store explicit LUN mapping information per LUN; with longer IQN names, this area can be exhausted. This issue is not dependent on the number of paths to the LUN.

Workaround: Shorten the IQN name on the nodes.

The following formula is used to calculate the maximum IQN name length, based on the number of hosts being explicitly mapped to a LUN on the array:

 Maximum IQN Character Length = (4083 / n) – 7 (Where n = number of hosts nodes explicitly mapped to a LUN on the array.)

NOTE: By specification, 223 is the maximum IQN length allowed.

The following table provides the calculated values based on the number of hosts being explicitly mapped to a LUN on the array:

Number of hosts explicitly mapped to a LUN and the maximum IQN character length Number of hosts explicitly mapped to a LUN and the maximum IQN character length Number of hosts explicitly mapped to a LUN and the maximum IQN character length
1–17223 33116 4976
1821934113 5074
1920735109 5173
2019736106 5271
2118737103 5370
2217838100 5468
231703997 5567
241634095  5665
251564192 5764
261504290 5863
271444387 5962
281384485 6061
291334583 6159
301294681 6258
311244779 6357
321204878 6456

Issue: RedHat Enterprise Linux Server 5 that uses the P711m, P712m, and P721m SmartArray adapters connected to a MSA 2040 SAS array might not create all multipath (mpath) partitions correctly, after rebooting the client when the array is under heavy load and there are a large number of multipath devices.

Workaround: After booting the server, scan for new multipath partitions by running the command, multipath -v 0. If the partitions are still not created, try flushing the multipath devices and recreating the devices by issuing the command multipath -F followed by multipath -v 0.


Issue: All paths might not be reinstated correctly after a failback condition occurs, when a c-Class BladeSystem is connected via the SmartArray P711m, P712m, or P721m to a MSA 2040 SAS array in an ESX 5.x environment. A failback condition can occur due to cable replacement, SAS switch zoning changes, controller replacement, controller shutdown and reboot, or firmware upgrades.

Workaround: Force a rescan of all paths in the vSphere client, CLI, or PowerShell utilities. Consult VMWare documentation on the correct procedure.


Issue: If the auto-write-back setting is disabled using the set auto-write-through-trigger CLI command, the controller reboots into write-through mode.

Workaround: Manually set the cache parameters to write-back and re-enable auto-write-back setting as applicable.


Issue: When the controller is in write-through mode, snap-pool space is not freed for some time after snapshots are deleted.

Workaround: Set the cache parameters to write-back on the controller to allow space to free more quickly.


Issue: Storage controller restart (for example, the CLI command restart sc both) causes the management controller to restart.

Workaround: None.


Issue: Replications scheduled with time constraints might not occur within the scheduled time, and the scheduler might expire before it reaches the desired number of replications.

Workaround: Do not use the scheduler with time or date constraints.


Issue: If you remove controllers from a chassis that is running manual IP configuration, and if you install those controllers in a chassis that is configured for DHCP and then return them to the original chassis, the controllers retain the DHCP configuration instead of the Manual IP configuration saved in the chassis midplane.

Workaround: If you move controllers between chassis, verify the IP configuration.


Issue: When direct-attached to an Emulex FC HBA, a link might not be established.

Workaround: Ensure that all affected array and HBA ports are using auto or loop topology. For the array, this must be accomplished using the CLI.


Issue: Controller temperature Event 307 occurs without a sensor location.

Workaround: None.


Issue: FTP code load is unsuccessful.

Workaround: Restart the management controller.


Issue: When a background media scrub is run on the spares, vdisk spares are displayed as vdisk members in the SMU.

Workaround: None.


Issue: In the SMU in the Enclosure Overview screen, a spare disk that is performing disk scrub displays DRSC appended to How Used in the properties table, causing an undescribed value of VDISK SPDRSC.

Workaround: None.


Issue: An SNMP log-in is created that uses privacy type but no authentication type.

Workaround: If either the privacy type or authentication type is supplied, provide both parameters.


Issue: SMU erroneously reports successful deletion of a host with volume maps.

Workaround: Remove the host mappings and verify that the host was deleted.


Issue: After you attempt a firmware update, controllers revert to the old version.

Workaround: Do not make configuration changes during firmware updates.


Issue: When using IE9 in compatibility mode to access the SMU, a message appears on the login page that states the browser is unsupported.

Workaround: Disable IE9 compatibility mode.


Issue: A newly installed drive reports errors.

Workaround: Replace the drive.


Issue: A warning about the coin battery was not displayed in the Storage Management Utility (SMU) events log.

Workaround: Reset the controller date and time to be current, and restart the management controller.


Issue: D2700 I/O module port status is not included in the SMU display.

Workaround: None.


Issue: D2700 power supply information is incomplete in the SMU display.

Workaround: None.


Issue: SMU reports an error of input too long when you try to map a volume that is part of a replication image.

Workaround: Shorten the length of the Snapshot Name. Selecting defaults in the SMU adds four characters to an image name if the replication occurs when the set is created. If replications are scheduled when the set is created, four characters are added as a prefix, and six characters are added for the unique snapshot name. In either case, five characters are added for the exported snapshot name.


Issue: During the drive firmware update, a message is returned stating that the disk is unsupported.

Workaround: The message is incorrect. Use the Hard Disk Drive (HDD) firmware (FW) Smart Component to update FW, if available.


Issue: When creating a volume in the SMU, if you change the units from GB to MB but do not change the volume size, the volume will be created in GB rather than MB.

Workaround: Validate the volume size after creating a new volume. If the volume was created with the wrong units, delete and re-create the volume.


Issue: The SMI-S modify volume name appears as non-supported in Windows Server Manager 2012.

Workaround: Use the SMU or CLI to modify the volume name.


Issue: When you select Configuration > Remove User in the SMU, the User Name field is not enabled, even though the asterisk indicates that it is required.

Workaround: Use the radio buttons to select the user from the list. The User Name field will be automatically completed.


Issue: The SMU might incorrectly display a warning status for a healthy power supply in a cascaded HP D2700 disk enclosure.

Workaround: Use the CLI show power-supplies command to verify the power supply status.


Issue: Vdisk Data Transferred and Data Throughput numbers appear to be much higher when using the CLI historical show vdisk-statistics [vdisk] historical command, compared to the CLI live output show vdisk-statistics command. This issue is caused by the way that the historical and live values are calculated.

  • Live values are calculated based on the vdisk as viewed from the controller cache perspective. In the live statistics, performance numbers are obtained by accounting when data is written from cache to disk or data is read from disk to cache.

  • Historical data is obtained by using the summation of disk statistics for disks in the vdisk. The historical vdisk data shows transfers to and from the disks in the vdisk that include the overhead of any RAID transfers, as well as any host activity.

Because I/Os from the RAID engine are included, numbers for the historical data appear higher than the numbers for the live data.

Workaround: None.


Issue: If a previously used drive is inserted in the enclosure, it might retain information about vdisks, volumes, and volume mappings from its previous use. However, the LUN numbers of these volume mappings might conflict with LUN numbers currently in use in volume mappings on the system. If this occurs, the system resolves those conflicts by removing the mappings.

Workaround: Remap the volumes, as necessary.


Issue: When you modify a vdisk name in the SMU, / (slash) is replaced by a space.

Workaround: None.


Issue: In the CLI, the show sensor-status command does not show warning levels or indicate fan status.

Workaround: None.


Issue: Power supply voltage readings for cascaded HP D2700 drive enclosures are not reported in the SMU.

Workaround: None.


Issue: If a vdisk becomes critical, the array might generate multiple events.

Workaround: None.


Issue: In event messages, power supplies are referred to by different terminology. Sometimes power supply 1 is reported as left and sometimes reported as 1. Likewise, power supply 2 is sometimes reported as right and sometimes reported as 2.

Workaround: None.


Issue: A serial number was not generated for SMART drive Event 55.

Workaround: Identify the drive by using the enclosure and slot number.


Issue: In the CLI, the show master-volumes command includes a volume that has been converted to a standard volume.

Workaround: Log out, and log in again to the CLI.


Issue: Global spares have a status of Up in the SMU, even if they are spun down using the drive spin-down feature.

Workaround: None.


Issue: On the Configuration > Advanced Settings > Microsoft Windows Server 2008 R2 > System Utilities page, changing the Vdisk Scrub and Managed Logs settings at the same time might result in an error.

Workaround: Make these changes one at a time.


Issue: When you create a volume set with the volumes mapped to LUNs, if there is a LUN conflict, the array stops mapping volumes to LUNs but creates the volumes as requested.

Workaround: Ensure that there are no LUN conflicts before creating the volume set with mapping, or map the remaining volumes to LUNs after the conflict.


Issue: SLES 11 might require multiple minutes (15+/-) to create all multipath devices during boot. This typically involves a system with a large number of LUNs and multiple LUN paths.

Workaround: None. Wait for the system to complete LUN and path discovery.


Issue: Under rare circumstances, some events from one controller are not seen on the other controller.

Workaround: Review the events from both controllers.


Issue: The USB CLI becomes unusable after a Management Controller reboot in Windows environments.


  1. Close down the terminal application (e.g., HyperTerminal).

  2. Open Device Manager, and disable the Disk Array USB Port under Ports (COM and LPT).

  3. Re-enable the Disk Array USB Port. If the problem persists, reboot the host.


Issue: The mini-USB CLI port on the array controller does not work.

Workaround: Install a device driver for the mini-USB CLI port. This driver is packaged as a Smart Component and is available for download on the MSA 2040 support page.


Issue: There is no indication that a LUN has failed-over to the other controller.

Workaround: Using the Storage Manage Utility (SMU), open system events and scan for failover events. When using the CLI, use the show events command.


Issue: A replication is initiated, but only a snapshot on the primary volume occurs, or the replication is queued.

Workaround: Ensure that all systems involved have valid replication licenses installed. Ensure that all volumes and vdisks involved in the replication have started, are attached, and are in good health, including vdisks that contain the snap pools for the volumes involved. A replication normally queues when a previous replication involving the same volumes is active.


Issue: A replication set was deleted but is later shown with the primary volume status of Offline and the status-reason is record-missing.

Workaround: This generally occurs when you detach the secondary volume, delete the replication set (which stops the vdisk), and restart the vdisk of the secondary volume. To correct this issue, reattach the secondary volume, set it as the primary volume, and delete the replication set.


Issue: A Controller Busy error message occurs while you create a replication set.

Workaround: Creating replication sets immediately one after the other might result in Controller Busy. This is expected behavior. Wait and try the operation again at a later time.


Issue: In the SMU, the Vdisk > Provisioning > Create Multiple Snapshots task allows a secondary volume to be selected but fails the operation.

Workaround: User-initiated snapshots are not allowed on secondary volumes. Do not select a secondary volume.


Issue: A scheduled replication is missing, or replications are queued but do not complete.

Workaround: A best practice is to schedule no more than four volumes to start replicating at the same time and for those replications to recur no less than 30 minutes apart. If you schedule more replications to start at the same time or schedule replications to start more frequently, some scheduled replications might not have time to complete.


Issue: You are unable to perform a local replication (a replication where the primary volume and the secondary volume reside on the same system) with a single vdisk.

Workaround: Create a second vdisk for the secondary volume.


Issue: Deleting the replication set from the destination system fails.

Workaround: Delete the replication set from the source system (the system where the primary volume resides.)


Issue: A replication set is missing the primary volume, and the replication set cannot be deleted.

Workaround: Set the remaining volume in the set to be the primary volume. You should then be able to delete the replication set.


Issue: On rare occasions, deleting a vdisk when volumes are in the process of rolling back might cause communications issues between the management controller and the storage controller.

Workaround: Cycle the power on the array to resolve the issue. To avoid this situation, allow the rollbacks to complete, or delete the volumes before deleting the vdisk.


Issue: Scheduled tasks are not occurring, and there is no indication of a problem in the schedules or the tasks.

Workaround: Restart both management controllers of the arrays involved in the tasks.


Issue: In a dual-controller system, the login to one of the controllers fails, but the login to the other controller succeeds.

Workaround: Log in to the other controller and restart the inaccessible management controller using the CLI restart mc command or the SMU Tools > Shut Down or Restart Controller page.


Issue: IOPs and Bytes per second might be lower or higher than expected for the workload.

Workaround: This is a reporting issue and not a performance issue. Calculate the correct values by using the change in the Number of Reads and Number of Writes over time to determine IOPs, and the change in Data Read and Data Written over time to determine Bytes per second.


Issue: The array controller might interpret a switch login as a host bus adapter (HBA) login and erroneously present the switch port as a discovered host. This does not affect storage functionality.

Workaround: Either identify the erroneous host and do not attempt to use it, or use Disable Device Scan on switch ports connected to the array controller and restart the array controller.


Issue: SMI-S Alert Indication for Power Supplies and Disks returns an invalid device ID in the AlertingManagedElement attribute.

Workaround: Use the show events CLI command to identify the failed device.


Important firmware notes

  • Windows Server 2012 management integration:

    • HP recommends that you update the Windows cache by using the cmdlet, Update-StorageProviderCache -DiscoveryLevel Full -Name <storageProviderName> manually, after attempting any storage provision operations that use the MSA management interface.

    • HP recommends that you use the MSA management interface (Storage Management Utility or Command Line Interface) to modify volume mappings, delete volumes, or modify volume names. Manually update Windows cache by using the cmdlet, Update-StorageProviderCache -DiscoveryLevel Full -Name <storageProviderName>.

  • System Center VMM integration:

    • Running operations concurrently is supported, except for Windows 2008 R2, up to the limit of four concurrent operations. This includes creating objects (e.g., LUNs, clones, snapshots) and registering objects to hosts or four node clusters.

  • Windows Server 2012 management and System Center VMM integration:

  • The MSA 2040 contains an embedded SMI-S provider for use by SMI-S client applications. The embedded provider is designed to support MSA 2040 configurations with up to 24 hard drives and up to 250 mapping paths. A mapping path is defined as an MSA 2040 volume presented through an MSA 2040 target port to a host initiator.

  • Smart Array SAS HBAs are not supported with SMI-S based applications that include System Center VMM and Windows Server 2012 Integrations.

  • Some older drive firmware Smart Components may not be compatible with the MSA 2040 and cause the Smart Component to stall. If this occurs, HP recommends extracting the Smart Component and using the .FLA or .LOD file with the SMU to update the drive firmware.

  • When changing a replication set (e.g., adding or removing a replication volume or deleting the replication set), do so from the source system; when aborting, suspending, or resuming a replication, do so from the destination system.

  • When changing the primary volume of a replication set, do so from the destination system first, then, perform the change on the source system.

  • When using Windows Dynamic Disk (software RAID) on top of a hardware RAID, cautions must be considered. For more information, see the section Real World: Dynamic versus Basic Disks on the topic at http://technet.microsoft.com/en-us/library/dd163558.aspx.

  • Failover and failback times are affected by the number of system volumes; the more volumes there are on the system, the more time is required for failover and failback to complete.

Installation instructions

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

CAUTION: Before upgrading firmware, ensure that the system is stable and is not being re-configured or changed in any way. If changes are in progress, monitor them and wait until they are completed before proceeding with the upgrade.

IMPORTANT: In dual-module enclosures, both controllers or both I/O modules must have the same firmware version installed. Running different firmware versions on installed modules may cause unexpected results.

Before installing this firmware:

  • If using a Smart Component, ensure that FTP and telnet are enabled on the arrays being updated.

  • Create a full backup of system data. (A full backup is strongly recommended.)

  • Schedule an appropriate time to install the firmware:

    • For single-controller systems, I/O operations must be halted.

    • For dual-controller 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:

    It takes approximately 45 minutes for the firmware to load and for the automatic restart to complete on the first controller module. When dual modules are installed, the full process time is approximately 90 minutes. If cascaded drive enclosures are also being updated, the total process time may be as long as 180 minutes.

  • For dual-controller systems, the Smart Component automatically enables/disables the Partner Firmware Update (PFU) settings as necessary to update both controllers. However, if you use the SMU or FTP instead of the Smart Component, follow the actions below based on the PFU setting to ensure that both controllers are updated:

    • If the PFU is enabled: after the installation process completes and then restarts the first controller, the system automatically installs the firmware and restarts the second controller.

    • If the PFU is disabled: after updating firmware on one controller, you must manually update the second controller.

During the installation process:

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

After the installation process 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 MSA Event Descriptions 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:

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

  • Note that when using a Smart Component firmware package, the process automatically disables the PFU and then downgrades the firmware on each controller separately (one after the other) through the Ethernet ports.

  • If you are using a binary firmware package, manually disable the Partner Firmware Update option. Then, downgrade the firmware on each controller separately (one after the other).

Installing firmware using Smart Components in Windows environments

This is a self-extracting executable module. You can execute this module from the Windows graphical user interface (GUI) or the Windows command prompt.

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. In single-controller environments, stop all I/O to vdisks in the enclosure before starting the firmware update.

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

  4. Double-click the executable file.

  5. Follow the on-screen instructions. After you are prompted for logon information, enter credentials for an account with management access rights.

  6. Wait for the installation to complete. During installation, each updated module automatically restarts. Upon completion, a confirmation message is displayed.

Command line 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. In single-controller environments, stop all I/O to vdisks in the enclosure before starting the firmware update.

  3. In a Windows command prompt, navigate to the directory containing the download.

  4. Execute the Smart Component by entering the following command:

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



    is the downloaded Smart Component filename


    is the management IP address of the array controller


    is the username account with management rights


    is the password for username


    indicates that the installation is silent and does not prompt or display any output. To see results, see the file \CPQSYSTEM\Log\cpqsetup.log on the system drive.

    NOTE: Instead of command line parameters, you can use the following DOS environment variables:

    • oa_address: Set this variable for the IP address of the array controller.

    • oa_username : Set this variable for the username of the array controller.

    • oa_password : Set this variable for the password of the array controller.

  5. If you are prompted for logon information, enter credentials for an account with management access rights.

  6. Wait for the installation to complete. During installation, each updated module automatically restarts. Upon completion, a confirmation message appears if this is not a silent installation.

Installing firmware using Smart Components in 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. In single-controller environments, stop all I/O to vdisks in the enclosure before starting the firmware update.

  3. Open a Linux command console.

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

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

    ./CPxxxxxx.scexe -e --target <ip_address> --user <manage_username> --passwd <manage_password>


    • To force output from the command when flashing a device:

      • Use -e (reflash): flash even if the device is already up to date.

      • Use -f (force): always flash applicable devices.

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

  6. Follow the on-screen instructions. If prompted for logon information, enter credentials for an account with management access rights.

  7. Wait for the installation to complete. During installation, each updated module automatically restarts. Upon completion, a confirmation message appears if this is not a silent installation.

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 by using one of the following methods:

    • In Windows—Click Extract on the first screen of the Smart Component.

    • In Linux—Enter a command by using the following syntax:

      ./CPxxxxxx.scexe --unpack=<folder name>



      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: GLxxxRyyy-zz.bin.

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

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

    A table is displayed that shows currently installed firmware versions.

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

  7. Click Install Controller-Module Firmware File.

  8. Wait for the installation to complete. During installation, each updated module automatically restarts.

  9. 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 you are using a Smart Component, extract the contents of the Smart Component by using one of the following methods:

    • In Windows—Click Extract on the first screen of the Smart Component.

    • In Linux—Enter a command by using the following syntax:

      ./CPxxxxxx.scexe --unpack=<folder name>



      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: GLxxxRyyy-zz.bin.

  4. Using the SMU, prepare to use the FTP:

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

    2. Verify that the system FTP service is enabled.

    3. Verify that the user login has permission to use the FTP interface and has manage access rights.

  5. In single-controller 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 with the following syntax:

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

    2. Log in as a user with the manage role. The default settings include the FTP user with a manage role. .

    3. Enter a command by using the following syntax:

      put <firmware-file> flash

      where <firmware-file> represents the binary firmware filename

  7. Wait for the installation to complete. During installation, each updated module automatically restarts.

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

  9. Quit the FTP session.

  10. Verify that the expected firmware version is installed on each module.

    • In the SMU, right-click the system in the Configuration View panel, and then select Tools > Update Firmware.

    • In the Command Line Interface (CLI), execute the show version or the show enclosures command.

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

Related information

The latest documentation for the HP MSA 1040 Controller is available at http://www.hp.com/support/msa1040/manuals.

The latest documentation for the HP MSA 2040 Controller is available at http://www.hp.com/support/msa2040/manuals.

Documentation feedback

HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (). Include the document title and part number, version number, or the URL when submitting your feedback.