The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise 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. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from Hewlett Packard Enterprise 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.

Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website.


This package delivers firmware for the HPE MSA 1060, 2060, and 2062 storage systems.

Update information

Update recommendation: Recommended

Supersede information

Supersedes: Firmware version IN100R003

Product models

  • MSA 1060 Storage System

  • MSA 2060 Storage System

  • MSA 2062 Storage System

Additional devices supported


A valid HPE Passport connected to the MSA hardware will be required to download the firmware. See for the HPE Passport for MSA arrays.

HPE MSA 1060, MSA 2060, and MSA 2062

The MSA 1060, 2060, and 2062 array controller enclosures support the cascading of disk enclosures. The following table lists supported disk enclosure models and firmware versions.

Cascaded disk enclosure model Recommended disk enclosure firmware

MSA 1060/2060/2062



After updating array controller firmware or connecting new disk enclosures to an existing controller enclosure, verify the firmware compatibility of all devices. If needed, obtain and install the enclosure firmware. Firmware is available for download from the MSA Firmware website at

HPE MSA notification best practices

To effectively monitor the health of the MSA array, it is a best practice to:

  • Enable notifications through SNMP, email, or syslog settings in the user interfaces.

  • Set the alert notification level to All and the notification level to Warning to ensure that you are monitoring your system for possible failures.

  • Perform validation of notification settings periodically after firmware load or component replacement to guard against changes in infrastructure or configuration settings.

MSA Health Check Tool

Maintaining the health of an MSA ensures that maximal performance is continuously available. Any component of the array that is signaling poor health status can degrade the health of the array and affect array performance.

To obtain a complete diagnostic profile of an MSA storage configuration, obtain array logs from the MSA and submit them at Hewlett Packard Enterprise recommends resolving any issues that are found prior to reassessing array performance.

Important firmware notes

  • Windows Server management integration:

    • Hewlett Packard Enterprise 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 afterward by using the cmdlet, Update-StorageProviderCache -DiscoveryLevel Full -Name <storageProviderName>.

  • System Center VMM integration:

    • Running operations concurrently is supported, up to the limit of four concurrent operations. Operations include creating objects (for example, LUNs, clones, snapshots) and registering objects to hosts or four node clusters.

  • Windows Server management and System Center VMM integration:

    • If SCVMM or Windows Server manages only MSAs and not any other arrays, Hewlett Packard Enterprise recommends that you disable Windows Indication subscription. To disable the Indication subscription, modify the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Current Version\Storage Management\EnableIndications value from 1 to 0 and restart Windows Standards Based Storage Management Service.

    • If you want to enable the Indication subscription at Windows Server, Hewlett Packard Enterprise recommends that you configure the Indication based on the instructions provided at

  • The MSA Storage System contains an embedded SMI-S provider for use by SMI-S client applications. The embedded provider is designed to support MSA Storage System configurations with up to 250 mapping paths. A mapping path is defined as an MSA Storage System volume presented through an MSA Storage System 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 Integrations.

  • 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

  • Controller 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 controller failover and failback to complete.
  • The open-source bundle for this firmware release can be found by going to, entering the product name in the search bar, and looking in the Drivers and Software list.

Operating systems

For information about operating systems supported by the HPE MSA arrays, see the HPE Storage Single Point Of Connectivity Knowledge (SPOCK) website at


Languages support for this release:

  • English

  • Spanish

  • French

  • German

  • Italian

  • Korean

  • Japanese

  • Dutch

  • Chinese (traditional)

  • Chinese (simplified)




The following issues have been resolved in the IN100P001 release:

Vendor and Model Description show incorrect values for Small Form Factor (SFF) enclosures in the Command Line Interface (CLI) and Storage Management Utility (SMU).

Issues and workarounds

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

Issue: After firmware upgrade, the system may return ‘unknown’ for enclosure EMP <controller-ID> CH:ID when running the show enclosures command or in the EMP <controller-ID> Revision, EMP <controller-ID> Bus, and EMP <Controller-ID> Target ID fields in the SMU Maintenance > Hardware pane.

Workaround: Run a manual rescan either by running the rescan CLI command or by navigating in the SMU to Maintenance > Hardware > Actions, selecting Rescan All Disks, and refreshing the SMU.

Issue: Pool performance graphs are not available in the Storage Management Utility (SMU).

Workaround: Use show pool-statistics in the Command Line Interface (CLI) to retrieve pool performance information.

Issue: The CLI command show firmware-bundles only displays the health of components connected to the controller where the command is run.

Workaround: Run the CLI command show firmware-bundles from both controllers.

Issue: When adding a static IPv6 address with a duplicate address-label the error message incorrectly states "Error: The specified IP address matches one currently configured on the system." The error message should indicate that the label is already configured on the system.

Workaround: Create unique labels for IPv6 addresses.

Issue: The Redfish API may return a "204 - No Content" on successful creation of a disk-group.

Workaround: Validate disk-group was created successfully.

Issue: A localized SMU may include English content.

Workaround: None.

Issue: Volume groups created in the CLI are deleted when any of the volumes in the group are used in setting up a replication in the SMU.

Workaround: Use the CLI to set up the replication or select all the volumes in the volume group when creating the replication set and allow the SMU to create a new volume group.

Issue: Keyboard navigation in the SMU may not work as desired.

Workaround: Utilize the mouse to navigate in the SMU.

Issue: If the replication from the secondary to the primary is aborted during the failback restore operation, the user cannot initiate a replication on that replication set in the SMU.

Workaround: Initiate the replication from the CLI.

Issue: SMI-S responses may append a "_psc" string to element names.

Workaround: Trim the "_psc" string from the element name.

Issue: While navigating the SMU, the help window may appear if it was previously minimized.

Workaround: Close the help window when it is not needed.

Issue: SMI-S clients will not receive any SMI-S indication about firmware update events.

Workaround: None.

Issue: Disk or disk-group scrub tasks will not show in the scheduled activity list in the SMU.

Workaround: In progress and recently completed scrubs are shown.

Issue: A replication set that was suspended then the suspended replication aborted indicates that the replication status is suspended rather than aborted or canceled.

Workaround: None.

Issue: Snapshot volumes to are unable to be added to a performance metric graph in the SMU.

Workaround: None.

Issue: Not able to suspend or abort a replication set from the secondary system.

Workaround: Use the primary system and perform suspend or abort actions.

Issue: Attempting to map a volume with ServerEndpointGroups - AllTargetPorts in the Redfish API will result with an error message "An invalid port was specified."

Workaround: Specify each target port in the command.

Issue: When using the XML API, very slow or no response will be seen when issuing help commands.

Workaround: Do not use help commands with XML interface.

Issue: Attempting to select unnamed initiators in the All Initiators tab of the Hosts panel may not work as expected.

Workaround: Use the initiator slide over to name the initiator.

Issue: Replication failback and reverse operations will not work with replication peers that are MSA 1050/2050 systems.

Workaround: None.

Issue: During a volume copy operation, the SMU may incorrectly display the secondary replication volume icon and associated tooltip for that icon.

Workaround: None.

Issue: IPv6 information in the CLI commands show controller and show configuration does not show correct IPv6 addresses when autoconfig was disabled only on one controller.

Workaround: Keep the IPv6 autoconfig setting the same for both controllers.

Issue: In the SMU, the snapshot history cannot be disabled after the creation of a replication set.

Workaround: To disable snapshot history for the replication set, use the CLI.

Issue: The SMU will only display "Never-Delete" for Snapshot Retention in non-English locales.

Workaround: Use the CLI to verify Snapshot Retention settings.

Issue: The SMU does not show the IPv6 SLAAC network address.

Workaround: Use the CLI to display the IPv6 SLAAC address.

Issue: The Redfish API may return an "internal server error" when modifying or updating a volume using the volume name.

Workaround: Use the volume serial number in the request.

Issue: In a non-English CLI session, confirmation prompts may be localized, but valid responses are English (y/n).

Workaround: None.

Issue: The Redfish API may return additional subcomponents in the system.

Workaround: None.

Issue: The Redfish API only lists the IPv4 addresses.

Workaround: Use the standard CLI or SMU to view the IPv6 information.

Issue: Invalid characters used in modifying a replication set name will return an incorrect error.

Workaround: None.

Issue: Downloading of logs from the SMU will fail if comments in the comments field contain line breaks.

Workaround: Do not use line breaks in the comments field.

Issue: IPv6 SLAAC addresses may be accessible if autoconfig is disabled.

Workaround: Disable router advertisements on your network.

Issue: Login may be slow if the management controller cannot resolve the partner management controller name through DNS.

Workaround: Configure DNS on both controllers to use the same set of DNS servers that can resolve both controller names.

Issue: A warning icon may show in the SMU for a component during firmware load.

Workaround: The icon may be due to the component not having to be updated. Verify update status in the CLI.

Issue: Attached Hosts column will be blank when expanding the Volumes For Pool <pool-id> element in the expanded Capacity panel accessed from the Dashboard.

Workaround: Use the Volumes panel under Provisioning in the SMU to get the details about hosts attached to a specific volume.

Issue: System metrics may not start when one of the controllers is down.

Workaround: Restore system to fault tolerant condition before attempting to start metrics.

Issue: In the SMU when there are no hosts created, but there are discovered initiators, the Attach to Hosts action from the volume's Select Volume action menu will be disabled.

Workaround: Go to the Hosts panel, create a host, and come back to the volumes menu to perform the action.

Issue: Replication activity is not displayed in performance graphs.

Workaround: None.

Issue: The test syslog operation may not generate a test notification.

Workaround: Set the syslog notification level to info to validate connectivity.

Issue: In help for set email-parameters the notification-level parameter description includes an unsupported alerts-only option.

Workaround: Do not use the alerts-only option.

Issue: Attempting to access the "initiators-url" in the REST interface may return a "Resource Not Found" message.

Workaround: None.

Issue: The CLI may show additional snapshots in the TreeSnaps column when the snapshot is of a volume that is part of a replication. The CLI is showing additional internal-only replication snapshots.

Workaround: None.

Issue: The Continue button may become disabled when creating a replication set in the SMU by checking and clearing the Secondary Volume Snapshot History option.

Workaround: Exit the replication set creation and start over, or check the Secondary Volume Snapshot History option, provide a Snapshot Base Name, then clear the Secondary Volume Snapshot History option.

Issue: MSA 1060 SAS systems may report an alert on an unavailable port due to changing the fan-out mode on the system.

Workaround: From the CLI clear all alerts.

Issue: "StorageServices" is not reported in the Odata results when querying the Service-Container in Redfish.

Workaround: None.

Issue: The Queue Policy setting of "Discard" may not be persist while creating a replication set in the SMU.

Workaround: Modify the Queue Policy after the replication set has been created.

Issue: A blank square box may appear between the Start Replication and Remove Replication buttons in the SMU.

Workaround: Ignore the blank box.

Issue: Audit log entries show serial number instead of the name of the component for set/delete configuration operations attempted from SMU.

Workaround: None.

Issue: The array responds to secure SMI-S port queries when secure SMI-S is disabled and unsecure SMI-S is enabled..

Workaround: None.

Issue: An HPUX system using VxVM may hang when booting from a direct connected MSA system.

Workaround: None.

Issue: The SMU viewed in a non-English locale may show misaligned or overflowing text.

Workaround: None.

Issue: If a snapshot scheduler is created with a start time in the past, the system will incorrectly create the schedule task even though the output shows a failure. Attempts to create the schedule again will produce an error that the task already exists.

Workaround: Use the CLI to delete the task that was created and then recreate the schedule.

Issue: The IO Workload graph in the SMU will not display any data if the pool consists of only SSDs.

Workaround: None.

Issue: IP address fields in the SMU may not accept abbreviated IPv6 addresses.

Workaround: Use the long form of the IPv6 address or use the CLI commands for setting these IPv6 addresses.

Issue: Performance graphs in the SMU may repeat colors if many different objects are graphed at the same time.

Workaround: Reduce the number of objects being graphed.

Issue: The CLI command set Ipv6-network-parameters may produce a warning "Command is taking longer to complete than anticipated." The command does complete without user intervention.

Workaround: None.

Issue: "Other MC status" is shown as 'Not Operational' in show shutdown-status CLI command when the other storage controller is shut down.

Workaround: None.

Issue: Managed logs email messages will be sent from a sender that will contain serial number, controller information, and IP address.

Workaround: None.

Issue: The error produced when creating a volume larger than the allowable size incorrectly indicates that the size exceeds the space available in the pool.

Workaround: None.

Issue: The audit log is shown in English only.

Workaround: None.



Hewlett Packard Enterprise Information Library

Single Point of Connectivity Knowledge (SPOCK) Storage compatibility matrix

HPE Support

Storage white papers and analyst reports


MSA QuickSpecs

MSA Manuals

MSA Firmware

HPE MSA Support Material Access

MSA Health Check

Documentation feedback

Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback ( When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.