Dell EMC PowerVault ME4 Series Storage Controller Firmware GT280R009-02
Installed This file was automatically installed as part of a recent update. If you are experiencing any issues, you can manually download and reinstall.Dell EMC PowerVault ME4 Series Storage Array Controller firmware
Recommended
Check compatibility
Enter your Dell Service Tag or model
Want to look up your product? Enter a product identifier. Show me how
This driver is not compatible
This driver is not applicable for the selected product. Choose another product to re-enter your product details for this driver or visit the Product Support page to view all drivers for a different product.
Sign in to Windows as an admin to use automatic scan. If your're already signed in as an admin and seeing this message, please reboot. Your system is managed by your IT admin and features might be limited.
Find more updates. Use SupportAssist to find all the latest driver updates for your device.
Fixes & Enhancements
Fixes:
FMW-36644 The volume and pool statistics in CloudIQ are incorrect when data is sampled while a user is not logged into
PowerVault Manager.
FMW-38568 The severity of the alert that is generated when a CloudIQ upload failure event occurs has been changed
from Error to Informational.
FMW-39192 Disabled the weak cipher DHE-RSA-AES256-SHA.
FMW-39193 Disabled weak MAC algorithms.
FMW-39287 Added patch for CVE-2004-0230.
FMW-40010 Upgraded OpenSSH to 8.4p1 for CVE-2020-14145.
FMW-42419 Added a fix for CVE-2019-5747 and CVE-2018-20679.
FMW-42430 Added Pure-FTPd patches to fix CVE-2011-1575 and CVE-2011-0418.
FMW-42433 Added a zlib patch to fix CVE-2016-9840.
FMW-38398 A virtual pool might go offline because of inconsistent metadata (BLPT error).
FMW-38736 A controller panic might occur because of no-mirror cache policy on volumes.
FMW-39564 Unable to delete an invalid IQN through the Coherent Accelerator Processor Interface (CAPI) when an
invalid IQN has already logged in.
FMW-39926 An unreliable disk read path detected error might occur after a controller reset caused by a SEAVE code
error.
FMW-40705 SNMP cannot collect the correct Power On Time for controllers.
FMW-40864 A replication snapshot might fail to be created because of a retention policy error that occurs when the
suffix number crosses 9999.
FMW-41352 OpenManage Enterprise cannot categorize alerts to ME4 systems because the SNMP Traps have an
internal IP address in the agent-addr field.
FMW-41496 Multiple disks might be in a leftover state after a system restart.
FMW-34488 If a system is set up using a serial connection, pressing Q to quit does not work on the EULA screen.
FMW-41265 Unable to specify an SMTP Server name on the Notifications tab of the System Settings dialog box when
the domain suffix is longer than six characters.
FMW-40009 MCP FMW-40009 - Security CVE-2020-14416
FMW-33614 MC TT51974: Dell Unable to easily change security from TLS to None
FMW-36759 SC Fixed issue for reading incorrect enclosure config page and swapping of incorrect enclosure configurations in m sep array, when system is busy in SCSI rescanning.
FMW-36776 SC Port FMW-34941 to G280, Clear any stale errors in the cached parity buffer pointerdata structure. The stale error can erroneous behaviors, like failing a drive incorrectly.
FMW-36979 SC Fixed issue for incorrect Historical Performance StatsFixed bugs in mem cpy statements for Historical Performance Statistics.
FMW-37469 SC Breaking a loop of ps idle page generation if system does not have BLPT and it is waiting for BLPT
FMW-40013 SC Port FMW-39238 to G280MR2 - Handle queries for pool historical performance ranges beyond current time
FMW-40540 MC Code changes are as follows: 1 View certificate details for WPA certificates. 2 List and View details of Web Certificates. 3 Adding Validations to the Add Certificate Path since the OpenSSL error is fixed in FMW-42073
Enhancements:
FMW-36573 SC Enhancement to add recovery features for DU/DL in case of PAM corruption and BLPT corruption in FW instead of providing recovery FW.
FMW-38636 MCP Add capability to support DHD logs in MC
FMW-39136 MCP Change the ftp help text for DHD drive logs in.
FMW-40539 MC Code changes for upload WPA certificate, Key and WPA CA certificate & View list of all uploaded WPA certificates
Read MoreFMW-36644 The volume and pool statistics in CloudIQ are incorrect when data is sampled while a user is not logged into
PowerVault Manager.
FMW-38568 The severity of the alert that is generated when a CloudIQ upload failure event occurs has been changed
from Error to Informational.
FMW-39192 Disabled the weak cipher DHE-RSA-AES256-SHA.
FMW-39193 Disabled weak MAC algorithms.
FMW-39287 Added patch for CVE-2004-0230.
FMW-40010 Upgraded OpenSSH to 8.4p1 for CVE-2020-14145.
FMW-42419 Added a fix for CVE-2019-5747 and CVE-2018-20679.
FMW-42430 Added Pure-FTPd patches to fix CVE-2011-1575 and CVE-2011-0418.
FMW-42433 Added a zlib patch to fix CVE-2016-9840.
FMW-38398 A virtual pool might go offline because of inconsistent metadata (BLPT error).
FMW-38736 A controller panic might occur because of no-mirror cache policy on volumes.
FMW-39564 Unable to delete an invalid IQN through the Coherent Accelerator Processor Interface (CAPI) when an
invalid IQN has already logged in.
FMW-39926 An unreliable disk read path detected error might occur after a controller reset caused by a SEAVE code
error.
FMW-40705 SNMP cannot collect the correct Power On Time for controllers.
FMW-40864 A replication snapshot might fail to be created because of a retention policy error that occurs when the
suffix number crosses 9999.
FMW-41352 OpenManage Enterprise cannot categorize alerts to ME4 systems because the SNMP Traps have an
internal IP address in the agent-addr field.
FMW-41496 Multiple disks might be in a leftover state after a system restart.
FMW-34488 If a system is set up using a serial connection, pressing Q to quit does not work on the EULA screen.
FMW-41265 Unable to specify an SMTP Server name on the Notifications tab of the System Settings dialog box when
the domain suffix is longer than six characters.
FMW-40009 MCP FMW-40009 - Security CVE-2020-14416
FMW-33614 MC TT51974: Dell Unable to easily change security from TLS to None
FMW-36759 SC Fixed issue for reading incorrect enclosure config page and swapping of incorrect enclosure configurations in m sep array, when system is busy in SCSI rescanning.
FMW-36776 SC Port FMW-34941 to G280, Clear any stale errors in the cached parity buffer pointerdata structure. The stale error can erroneous behaviors, like failing a drive incorrectly.
FMW-36979 SC Fixed issue for incorrect Historical Performance StatsFixed bugs in mem cpy statements for Historical Performance Statistics.
FMW-37469 SC Breaking a loop of ps idle page generation if system does not have BLPT and it is waiting for BLPT
FMW-40013 SC Port FMW-39238 to G280MR2 - Handle queries for pool historical performance ranges beyond current time
FMW-40540 MC Code changes are as follows: 1 View certificate details for WPA certificates. 2 List and View details of Web Certificates. 3 Adding Validations to the Add Certificate Path since the OpenSSL error is fixed in FMW-42073
Enhancements:
FMW-36573 SC Enhancement to add recovery features for DU/DL in case of PAM corruption and BLPT corruption in FW instead of providing recovery FW.
FMW-38636 MCP Add capability to support DHD logs in MC
FMW-39136 MCP Change the ftp help text for DHD drive logs in.
FMW-40539 MC Code changes for upload WPA certificate, Key and WPA CA certificate & View list of all uploaded WPA certificates
Version
GT280R009-02, A08
Release date
10 Dec 2021
Download Type
Firmware
Category
Storage Controller
Importance
RecommendedDell Technologies recommends applying this update during your next scheduled update cycle. The update contains changes to maintain overall system health. It ensures that the system software remains current and compatible with other system modules (firmware, BIOS, drivers, and software) and may include other new features.
Available formats View Important Information
File Format: Firmware Images
File Name: GT280R009-02-dellemc.zip
File Size: 60.98 MB
This is a large file. Depending on your connection speed, it may take some time to download.
Format Description:
To ensure the integrity of your download, please verify the checksum value.
MD5:
bbd5aaae81e9443bdc77aecde29f6a9d
SHA1:
25a8af9e2f1ae35cc9e14adb5186d1b551b47af6
SHA-256:
8f66189511dbfdc945081f68febcd67daebfbd48eb9c93bc3741894c44a9218b
By downloading, you accept the terms of the Dell Software License Agreement.
Important Information
This update is strongly recommended for all Dell EMC PowerVault ME4 Series Storage Arrays
Supported Operating Systems
Citrix XenServer 7.1
Red Hat® Enterprise Linux 6
Red Hat® Enterprise Linux 7
Red Hat® Enterprise Linux 8
Windows Storage Server 2012 R2
SUSE Linux ES 12
Windows Server 2012 R2
Windows Server 2019 LTSC
Windows Server 2016
VMware ESXi 6.0
VMware ESXi 6.5
VMware ESXi 6.7
VMware ESXi 7.0
Applies to
ME4012
Installation instructions
1. Perform one of the following:
In the banner, click the system panel and select Update Firmware.
In the System topic, select Action > Update Firmware.
The Update Firmware panel opens. The Update Controller Modules tab shows versions of firmware components that are currently installed in each controller.
2. Click the Bundle or Controller Firmware File button to select the firmware file to install.
3. Optionally, select (enable) or clear (disable) the PFU check box and confirm the action.
NOTE: For information about which controller module will update the other when a controller module is replaced, see About firmware update.
4. Click OK. A panel shows firmware-update progress.
The process starts by validating the firmware file:
If the file is invalid, verify that you specified the correct firmware file. If you did, try downloading it again from the source location.
If the file is valid, the process continues.
CAUTION: Do not perform a power cycle or controller restart during a firmware update. If the update is interrupted or there is a power failure, the module might become inoperative. If this occurs, contact technical support. The module
might need to be returned to the factory for reprogramming.
Firmware update typically takes 10 minutes for a controller with current CPLD firmware, or 20 minutes for a controller with downlevel CPLD firmware. If the controller enclosure has connected enclosures, allow additional time for each expansion module's enclosure management processor (EMP) to be updated. This typically takes 2.5 minutes for each EMP in a drive enclosure.
If the Storage Controller cannot be updated, the update operation is canceled. Verify that you specified the correct firmware file and repeat the update. If this problem persists, contact technical support.
When firmware update on the local controller is complete, users are automatically signed out and the MC restarts. Until the restart is complete, sign-in pages say that the system is currently unavailable. When this message is cleared, you may sign in again.
If PFU is enabled, allow from 10 through 20 minutes for the partner controller to be updated.
5. Clear your web browser cache, then sign in to the MESM. If PFU is running on the controller you sign in to, a panel shows PFU progress and prevents you from performing other tasks until PFU is complete.
NOTE: If PFU is enabled for the system, after firmware update has completed on both controllers, check the system health. If the system health is Degraded and the health reason indicates that the firmware version is incorrect, verify that you specified the correct firmware file and repeat the update. If this problem persists, contact technical support.
In the banner, click the system panel and select Update Firmware.
In the System topic, select Action > Update Firmware.
The Update Firmware panel opens. The Update Controller Modules tab shows versions of firmware components that are currently installed in each controller.
2. Click the Bundle or Controller Firmware File button to select the firmware file to install.
3. Optionally, select (enable) or clear (disable) the PFU check box and confirm the action.
NOTE: For information about which controller module will update the other when a controller module is replaced, see About firmware update.
4. Click OK. A panel shows firmware-update progress.
The process starts by validating the firmware file:
If the file is invalid, verify that you specified the correct firmware file. If you did, try downloading it again from the source location.
If the file is valid, the process continues.
CAUTION: Do not perform a power cycle or controller restart during a firmware update. If the update is interrupted or there is a power failure, the module might become inoperative. If this occurs, contact technical support. The module
might need to be returned to the factory for reprogramming.
Firmware update typically takes 10 minutes for a controller with current CPLD firmware, or 20 minutes for a controller with downlevel CPLD firmware. If the controller enclosure has connected enclosures, allow additional time for each expansion module's enclosure management processor (EMP) to be updated. This typically takes 2.5 minutes for each EMP in a drive enclosure.
If the Storage Controller cannot be updated, the update operation is canceled. Verify that you specified the correct firmware file and repeat the update. If this problem persists, contact technical support.
When firmware update on the local controller is complete, users are automatically signed out and the MC restarts. Until the restart is complete, sign-in pages say that the system is currently unavailable. When this message is cleared, you may sign in again.
If PFU is enabled, allow from 10 through 20 minutes for the partner controller to be updated.
5. Clear your web browser cache, then sign in to the MESM. If PFU is running on the controller you sign in to, a panel shows PFU progress and prevents you from performing other tasks until PFU is complete.
NOTE: If PFU is enabled for the system, after firmware update has completed on both controllers, check the system health. If the system health is Degraded and the health reason indicates that the firmware version is incorrect, verify that you specified the correct firmware file and repeat the update. If this problem persists, contact technical support.
Drivers help and tutorials
For more downloads go to the Drivers and downloads. For help on using the information on this page, please visit Driver Help and Tutorials.