Notices
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.
Acknowledgments
Description
This package delivers firmware for MSA 1040, MSA 2040, and MSA 2042 Storage systems.
For a list of supported companion drive enclosure firmware, see Additional devices.
Versioning key:
AxxxByyy-zz
The following letters represent firmware version release information:
Firmware version |
Description |
---|---|
A
|
MSA model. (GL=MSA 1040/2040; TS=P2000, M=MSA2000 G2) |
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) |
yyy
|
Major release number. |
-zz
|
Minor release number. |
Update recommendation
Update Recommendation: Critical - HPE requires users to update to this version immediately.
Supersede information
Supersedes: GL210R004, GL220R005, and GL220P009
Product models
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
-
Microsoft Windows Server 2016
-
Red Hat Enterprise Linux 5
-
Red Hat Enterprise Linux 6
-
Red Hat Enterprise Linux 7
-
SuSE Linux Enterprise Server 11
-
SuSE Linux Enterprise Server 12
-
HP-UX 11.31
-
VMware ESXi 5.0/5.1/5.5/6.0/6.5
Languages
English
Spanish
French
German
Italian
Korean
Japanese
Dutch
Chinese (traditional)
Chinese (simplified)
Arabic
Portuguese
Russian
Additional devices
MSA 1040/2040 array controller enclosures support the cascading of drive enclosures. The following table lists supported drive enclosure models and firmware versions.
MSA 1040/2040 array controller firmware | Cascaded drive enclosure model | Recommended drive enclosure firmware |
GL220 |
HPE P2000 drive enclosures |
S200B38 |
MSA 2040 drive enclosures |
S200B38 |
|
D2700 drive enclosure |
0149 or higher |
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:
-
Hewlett Packard Enterprise Business Support Center at http://www.hpe.com/support/downloads
-
MSA 1040 downloads at http://www.hpe.com/support/msa1040-downloads
-
MSA 2040 downloads at http://www.hpe.com/support/msa2040-downloads
MSA security considerations
This firmware contains security updates. After any security update is applied to your array, Hewlett Packard Enterprise 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.
MSA notification best practices
To effectively monitor the health of the MSA array it is a best practice to enable notifications via SNMP, email, or syslog settings in the user interfaces. Periodic validation of notification settings should be performed after firmware load or component replacement to guard against changes in infrastructure or configuration settings.
Enhancements
The following features were added or enhanced in controller firmware GL210R004: |
---|
Improved event criticality for certain events. |
Enabled dynamic spare feature by default. |
User is encouraged to change community strings for SNMP. |
Creating an SNMP v3 user disables SNMP v1 and SNMP v2. |
Disabled SSH v1. |
Reporting the Compact flash as a Field Replaceable Unit (FRU). |
Recommend replacing the Compact flash as a FRU in Compact flash failure events. |
Regenerate SSL certificates on demand. |
Enhanced total drive usage information to include drives not currently in use. |
Added warning prompts for configuration changes using the CLI that may result in data unavailability or data loss. |
Added additional information when reporting SCSI reservations. |
Display the licensing serial number for the CLI command show license
. |
Updated OpenSSL updated to 1.0.1m. |
Disabled SSL 3.0 to mitigate CVE-2014-3566. |
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, Hewlett Packard Enterprise 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. |
Fixes
The following features were fixed in controller firmware GL220P010: |
---|
Disk groups remain offline or quarantined after missing drives return to an online state. |
Rare data integrity issue found in lab testing environment under heavy load when system is running replications and controller failback occurs. |
Compact Flash flush failure error incorrectly invalidates cache data. |
The following features were fixed in controller firmware GL220P008: |
---|
The controller ceases operation when connected to a VMware host after a volume copy or replication operation on a virtual volume completed. |
Deploying VMs in a VMware environment resulted in VMware reporting an error and not powering on the VM successfully. |
The controller ceases operation when large virtual volumes are allocated and snapshots or remote snap replication are being utilized. |
Failback operations take longer than 60 seconds when the array was connected to SmartArray or SmartHBA SAS adapter in a VMware environment. |
The controller ceases operation when large number of virtual volume snapshots are utilized. |
Replacement of a controller may cause some management settings to be reset to factory defaults. |
The controller ceases operation if virtual remote snap replication is in use and the volumes are being accessed by the hosts. |
Creating new virtual remote snap replication sets may cause an I/O timeout on the connected hosts. |
The controller ceases operation during the creation of a snapshot of a virtual volume. |
The SMU interface, CLI interface, and host I/O may become unresponsive after repeated failover and failback operations. |
The controller ceases operation due to a heartbeat loss. |
Virtual remote snap replications may stall after multiple failover and failback operations. |
Virtual remote snap replication schedules may be removed after multiple failover and failback operations. |
Host I/O and the controllers may become unresponsive when linear remote snap was configured in GL210R004 firmware. |
The following features were fixed in controller firmware GL220R005: |
---|
The Install License menu item, and other features such as Create Snapshot, might not appear in the SMU. |
Unable to create a weekend suspend task on a weekend day in the SMU. |
In the SMU v2, the turn on LEDs option is disabled in . |
After the firmware is updated on the array, the SMU might freeze or become nonresponsive. |
In locales other than English, the Date, Time panel might not reflect the correct NTP settings. |
In Internet Explorer, when Help button is clicked in SMU, it can take a couple minutes for Help window to be populated with content. |
The Create Volume/Volume-set page highlights Access field in red (only once per volume). |
On SMU popups, buttons are not enabled until clicking outside of the data entry fields or selecting Tab. |
Partner Firmware Update can fail if there is a health issue in the system. If the code load health checker determines that firmware should not be loaded, no event will be logged. |
The CLI command
|
The CLI command
|
The CLI command
|
The SMU v3 Create Virtual Volume panel uses Copies terminology instead of Number Of Volumes. |
Related Snapshots shown in the Volumes Pane in the SMU v3 do not list all the descendant snapshots of the volume. |
The message incorrectly states
|
The CLI displays invalid pool details for virtual disk groups temporarily. |
The filter of Severity is truncated if there are two events in the event list. |
The SMU v3 is not rendering several elements properly in IE 10 and IE 11. |
Thin provisioning information reported in the SMU v3 and the CLI may not be in sync. |
The SMU Help does not show internal IP addresses in use by the array. |
The profile for an initiator is not shown in the SMU v3. |
Initiator profiles cannot be set in the SMU v3. |
Unable to select SNMPv3 Privacy Type in locales other than English in the SMU v3. |
Strings are truncated in some cases in the SMU v3 when locales other than English are used. |
In non English locales the SMU v3 does not reflect the NTP enabled state when it has been enabled in CLI. |
Snapshot schedules did not begin until an MC restart or schedules that had no associated tasks were deleted. |
D2700 IO Module Ports are not shown in the CLI command
|
The SMU may incorrectly display volume creation sizes with base 10 instead of base 2. |
The snap pool name cannot be changed in the SMU if the snap pool was created or modified in the CLI with an > in its name. |
In SMU v2, saving disk performance statistics may fail. |
In SNMP, if the notification level is set to None, then no test event is sent. |
In SMU v3, the forward > button does not work to navigate help topics online help. |
In the CLI, the
|
Creating and scheduling a replication set command fails if a volume name contains a space. |
Global Spares count may be incorrect in Korean locale on the Home page. |
SCVMM R2 may not accurately display available virtual pool capacity. |
In SMU v3, SSD spares may not be displayed in global spares information panel. |
Filter options are missing in the Event log viewer when a single event is listed in the viewer. |
Changes to email settings would show
|
Event logs show status of USB Drive that is not being used. |
Power Supply status shows
|
Unable to set the partner controller IP address due to communication issue. |
Single controller configuration always indicates chassis right ear faults LED on. |
Power Supply SMI-S 314 Indication has WARNING severity. |
Controller crashed with NMI: NOCP Errors. |
HTTPs web browser may not function correctly without a valid certificate. Certificate status is unknown. |
Controller crashed due to Critical Error OSMEnterDebugger CThr: mioL. |
Virtual disk-group drain stuck and will not complete. |
Invalid vdisks allowed for selection when creating replication set in SMU v2 RemoteSnap. |
The
|
Disk failure can cause data unavailability until a power cycle. |
Data is not draining from CRITICAL performance tier. |
D2700 Power Supply has no information. |
Controller crash due to resources being exhausted. |
Host Port information popup does not show entire iSCSI initiator iqn. |
Virtual pool is read-only due to multiple failures and rare race condition. |
Rare management controller crashes. |
MTU packet size not correctly documented. |
Controller crash due to PCI Link Recovery Stuck in a Loop. |
The array is not working correctly in single controller mode. |
IE 11 browser can cause replication to fail when changing the scheduled replication. |
Cannot highlight or get hover tip for RAID-50 in SMU v3. |
Text displayed for Hosts information is not clear in SMU v3 Homepage. |
User session timeout is not displaying in SMU v3. |
Event 8 Unknown Reason Drive failure does not create 314 event. |
Not sending an event and SNMP trap when available size is 0 MB. |
Drives that have failed previously due to SMART event should not be added to a Vdisk or Disk Group. |
SMU v2 volume cache settings still contain
|
Creation of performance tier disk group without a performance license generates
|
Hard (nonmedia) errors reported during disk scrub due to illegal request command to disk. |
CompactFlash product ID does not include part number in notifications. |
An HTML tag in search text box on Event Log Viewer. |
Delete Volumes option is disabled for a snap of a snap. |
In the SMU Full Disk Encryption Settings panel, the action buttons might not become active immediately after you enter required information on the page. |
Issues and workarounds
The following is a cumulative list of known issues and workarounds:
Important firmware notes
Windows Server 2012 management integration:
Hewlett Packard Enterprise 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.
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 by using the cmdlet,
Update-StorageProviderCache -DiscoveryLevel Full -Name <storageProviderName>
.
System Center VMM integration:
Windows Server 2012 management and System Center VMM integration:
Hewlett Packard Enterprise recommends that you disable Windows Indication subscription, if SCVMM or Windows Server 2012 manages only MSAs and not any other arrays. 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 2012, Hewlett Packard Enterprise recommends that you configure the Indication based on the instructions provided at http://blogs.technet.com/b/filecab/archive/2013/05/22/using-indications-with-the-windows-standards-based-storage-management-service-smi-s.aspx
.
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, Hewlett Packard Enterprise 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 diskson 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
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.
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.
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:
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
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 Updateoption. 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
Procedure
- Obtain the firmware package, and save it to a temporary directory. Firmware for all HPE products is available from the Hewlett Packard Enterprise Business Support Center Website at http://www.hpe.com/support/downloads.
- In single-controller environments, stop all I/O to vdisks in the enclosure before starting the firmware update.
- Using Windows Explorer, navigate to the directory containing the download.
- Double-click the executable file.
- Follow the on-screen instructions. After you are prompted for logon information, enter credentials for an account with management access rights.
- Wait for the installation to complete. During installation, each updated module automatically restarts. Upon completion, a confirmation message is displayed.
Command line update method
Obtain the firmware package, and save it to a temporary directory. Firmware for all products is available from the Hewlett Packard Enterprise Business Support Center Website at http://www.hpe.com/support/downloads.
In single-controller environments, stop all I/O to vdisks in the enclosure before starting the firmware update.
In a Windows command prompt, navigate to the directory containing the download.
Execute the Smart Component by entering the following command:
CPxxxxxxx.exe /target <ip_address> /user <username> /passwd <password> /s
If you are prompted for logon information, enter credentials for an account with management access rights.
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
Installing firmware using the Storage Management Utility (SMU)
Procedure
- Obtain the firmware package, and save it to a temporary directory. Firmware for all products is available from the Hewlett Packard Enterprise Business Support Center Website at http://www.hpe.com/support/downloads.
- If using a Smart Component, extract the contents of the Smart Component by using one of the following methods:
- Locate the firmware file
in the downloaded/extracted folder. The firmware filename is in the
following format:
GLxxxRyyy-zz.bin
. - In single-controller environments, stop all I/O to vdisks in the enclosure before starting the firmware update.
- 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.
- Click Browse, and select the firmware file to install.
- Click Install Controller-Module Firmware File.
- Wait for the installation to complete. During installation, each updated module automatically restarts.
- In the SMU display, verify that the expected firmware version is installed on each module.
Installing firmware using FTP
Procedure
- Obtain the firmware package, and save it to a temporary directory. Firmware for all products is available from the Hewlett Packard Enterprise Business Support Center Website at http://www.hpe.com/support/downloads.
- If you are using a Smart Component, extract the contents of the Smart Component by using one of the following methods:
- Locate the firmware file
in the downloaded/extracted folder. The firmware filename is in the
following format:
GLxxxRyyy-zz.bin
. - Using the SMU, prepare to use the FTP:
- In single-controller environments, stop I/O to vdisks in the enclosure before starting the firmware update.
- Open a command prompt (Windows)
or a terminal window (UNIX), and navigate to the directory containing
the firmware file to load.
- Enter a command with the
following syntax:
ftp <controller-network-address>
. (For example:ftp 10.1.0.9
) - Log in as a user with the manage role. The default settings include the FTP user with a manage role. .
- Enter a command by using
the following syntax:
put <firmware-file> flash
where
<firmware-file>
represents the binary firmware filename
- Enter a command with the
following syntax:
- Wait for the installation to complete. During installation, each updated module automatically restarts.
- If needed, repeat these steps to load the firmware on additional modules.
- Quit the FTP session.
- Verify that the expected firmware version is installed on each module.
Installation troubleshooting
If you experience issues during the installation process, do the following:
Procedure
- 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.
- 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.
- Updated system version
information is displayed, and the new firmware version shows that
it was installed.
- 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.
- If the
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 (docsfeedback@hpe.com). 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.