Dell EMC PowerVault ME4 Series Storage Controller Firmware GT280R010-01
hi testing
Driver Id : 97G7R
Importance : Recommended
Version : GT280R010-01, A09 Latest version Recommended version Latest and Recommended version
Release Date : 18 Jul 2022
Download Type : Firmware
Category : Storage Controller
Dell EMC PowerVault ME4 Series Storage Array Controller firmware
Download Files
File Name: GT280R010-01-dellemc.zip
File size: 52.9 MB
To ensure the integrity of your download, please verify the checksum value.
MD5: c1a16a9fec866cda68db9d5887a9e159
SHA1: b42a789ae7d8baa78039ce54a63831f2417d63cd
SHA-256: 84ecffb6ded66776a6fde8c9cf154c0c424235c241f93ef1c5dad6637e78e374
Fixes & Enhancements
Fixes:
FMW-43231 MC LAN Power Up CAPI Event(139) not found before 180 seconds
FMW-43572 SC MLIO and cache running on different cores lead to bad concurrent memory access path
FMW-43831 SC Fix for the adapt map corrupt issue seen during critical rebuild to recon target
FMW-44865 SC Fix mappings not read for few containers after RSCU
FMW-45265 MC Corrected missing code section in Checkin Revision
FMW-45527 SC For Restore Defaults Factory wait for first controller to reboot before rebooting second controller
FMW-45639 MC Check for any activity in progress before activating WPA 802.1x certificates
FMW-45946 SC Abort all the unmaps in cache FB phase and adding abort unmap function in BridgeShutdownLun to avoid crach by CAPI hang
FMW-46115 MC Fixed the incorrect status reported in Phone home tasks - Phone home logs and Upgrade Notification
FMW-47364 SC Fix a crash in forwarded commands path when a host io could get added to abort queue again
FMW-47475 SC Fix raid10 controller crashes during drive pull and insertion
FMW-47521 MC Sensitive information include in bundle logs
FMW-47590 SC SC missing SC trace logs when runing mc app "get logs" command
FMW-47617 SC Fix Crash due to Double Deletion of HIO in ATS abort Path
FMW-48174 MC Fix MC event mapping for temperature alert events
FMW-48935 MC Added validation rule for Secondary Volume Name input field to not allow volume name that is longer than max allowed limit
FMW-49122 SC Fix issue where adapt preemptive reconstruct didn't abort background scrub
FMW-49195 MC Fix to move sendmail to TLSv1.2
FMW-49278 MCP Wait for 60 seconds after each check firmware-upgrade-health command if appsv is restarted to free up memory
FMW-49487 MCP DHCP doesn't work with DHCP when last octet of the gateway IP address is greater that 127
FMW-49512 SC Fix controller crash observed when drive is pulled during adapt rebuild
FMW-49620 SC Fix to run only one copyback task on container
FMW-50056 SC Fixed incorrect assignment of SSM by correcting the condition used for search of SSM
FMW-37855 MCP CVE-2016-4485
FMW-45316 SC Fix a Crash in PS when a Write Same IO of Size greater then 4MB was requested in Write Through Mode
FMW-45614 SC During the error handling of protect status, test if the drive is already secured/unlockedstate to determine whether to issue an FDE init secure operation or to retry the command instead.
FMW-47242 SC Before adding SyncIO into wait Queue need to set srb->SrbFlags.bits.mayBeRetrying = TRUE so that OriginalStartTime will not reset while error handler re issue srb.
FMW-50101 SC Mitigate the critical vulnerability of "Hashed Password Stored Locally"
FMW-50108 MCP CVE-2021-3712, CVE-2021-3711
FMW-50201 MCP Upgrade OpenSSH to openssh-8.7p1 version
FMW-50561 SC Extend wait time to allow gem to come up during controller boot
FMW-47500 SC Don't do CAPI rescan if failover, failback is in progress
FMW-49242 MC Disable the unwanted ciphers for TLS1.2
FMW-49427 MC License details are mismatched in "show License" command and "query peer-connection" command output
FMW-50102 MCP Mitigate the vulnerability of "No rate limiting in place"
FMW-50102 MC Mitigate the vulnerability of "No rate limiting in place"
FMW-50104 MCP Apply BusyBox fix patches to mitigate vulnerabilities
FMW-50109 MC Apply fix patches to JQUERY to mitigate vulnerability
FMW-51554 MC Adjusted vertical position of the LED image so that appropriate LED is shown "Flashing" on the front view in WBI
FMW-51767 MC Included label of the input field in which duplicate value is entered in the error message to make the error message more descriptive.
FMW-52704 SC Updated CPU_EOSM_MEMORY_POOL_SIZE
FMW-50101 MC Disabled the MD5 feature
FMW-53216 MC Before displaying option to choose between "Linear" and "Virtual" configuration added a check to see if virtual pools can be provisioned or not on the system
FMW-53261 SC Handle new gem download status 0x10
FMW-53303 SC Fix a macro issue to address sync io
FMW-43231 MC LAN Power Up CAPI Event(139) not found before 180 seconds
FMW-43572 SC MLIO and cache running on different cores lead to bad concurrent memory access path
FMW-43831 SC Fix for the adapt map corrupt issue seen during critical rebuild to recon target
FMW-44865 SC Fix mappings not read for few containers after RSCU
FMW-45265 MC Corrected missing code section in Checkin Revision
FMW-45527 SC For Restore Defaults Factory wait for first controller to reboot before rebooting second controller
FMW-45639 MC Check for any activity in progress before activating WPA 802.1x certificates
FMW-45946 SC Abort all the unmaps in cache FB phase and adding abort unmap function in BridgeShutdownLun to avoid crach by CAPI hang
FMW-46115 MC Fixed the incorrect status reported in Phone home tasks - Phone home logs and Upgrade Notification
FMW-47364 SC Fix a crash in forwarded commands path when a host io could get added to abort queue again
FMW-47475 SC Fix raid10 controller crashes during drive pull and insertion
FMW-47521 MC Sensitive information include in bundle logs
FMW-47590 SC SC missing SC trace logs when runing mc app "get logs" command
FMW-47617 SC Fix Crash due to Double Deletion of HIO in ATS abort Path
FMW-48174 MC Fix MC event mapping for temperature alert events
FMW-48935 MC Added validation rule for Secondary Volume Name input field to not allow volume name that is longer than max allowed limit
FMW-49122 SC Fix issue where adapt preemptive reconstruct didn't abort background scrub
FMW-49195 MC Fix to move sendmail to TLSv1.2
FMW-49278 MCP Wait for 60 seconds after each check firmware-upgrade-health command if appsv is restarted to free up memory
FMW-49487 MCP DHCP doesn't work with DHCP when last octet of the gateway IP address is greater that 127
FMW-49512 SC Fix controller crash observed when drive is pulled during adapt rebuild
FMW-49620 SC Fix to run only one copyback task on container
FMW-50056 SC Fixed incorrect assignment of SSM by correcting the condition used for search of SSM
FMW-37855 MCP CVE-2016-4485
FMW-45316 SC Fix a Crash in PS when a Write Same IO of Size greater then 4MB was requested in Write Through Mode
FMW-45614 SC During the error handling of protect status, test if the drive is already secured/unlockedstate to determine whether to issue an FDE init secure operation or to retry the command instead.
FMW-47242 SC Before adding SyncIO into wait Queue need to set srb->SrbFlags.bits.mayBeRetrying = TRUE so that OriginalStartTime will not reset while error handler re issue srb.
FMW-50101 SC Mitigate the critical vulnerability of "Hashed Password Stored Locally"
FMW-50108 MCP CVE-2021-3712, CVE-2021-3711
FMW-50201 MCP Upgrade OpenSSH to openssh-8.7p1 version
FMW-50561 SC Extend wait time to allow gem to come up during controller boot
FMW-47500 SC Don't do CAPI rescan if failover, failback is in progress
FMW-49242 MC Disable the unwanted ciphers for TLS1.2
FMW-49427 MC License details are mismatched in "show License" command and "query peer-connection" command output
FMW-50102 MCP Mitigate the vulnerability of "No rate limiting in place"
FMW-50102 MC Mitigate the vulnerability of "No rate limiting in place"
FMW-50104 MCP Apply BusyBox fix patches to mitigate vulnerabilities
FMW-50109 MC Apply fix patches to JQUERY to mitigate vulnerability
FMW-51554 MC Adjusted vertical position of the LED image so that appropriate LED is shown "Flashing" on the front view in WBI
FMW-51767 MC Included label of the input field in which duplicate value is entered in the error message to make the error message more descriptive.
FMW-52704 SC Updated CPU_EOSM_MEMORY_POOL_SIZE
FMW-50101 MC Disabled the MD5 feature
FMW-53216 MC Before displaying option to choose between "Linear" and "Virtual" configuration added a check to see if virtual pools can be provisioned or not on the system
FMW-53261 SC Handle new gem download status 0x10
FMW-53303 SC Fix a macro issue to address sync io
Important Information
This update is strongly recommended for all Dell EMC PowerVault ME4 Series Storage Arrays
Compatible Systems
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
SuSE Linux ES 15
Windows Server 2012 R2
Windows Server 2019 LTSC
Windows Server 2022 LTSC
Windows Server 2016
VMware ESXi 6.5
VMware ESXi 6.7
VMware ESXi 7.0
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.
Applies to
ME4012