This firmware for 4000 series storage arrays includes fixes and enhancements as well as issues that have been discovered in testing since the original release.
Microsoft Windows Server 2008 (IA32 and x64, Standard, Enterprise, and Datacenter editions)
Microsoft Windows Server 2008 R2 (x64, Standard, Enterprise, and Datacenter editions)
Red Hat Enterprise Linux 5.6, 5.7, 5.8, 6.1, 6.2 (IA32, x64)
SuSE Linux Enterprise Server 10.4 and 11 SP1 and SP2 (x64 and IA32)
The following enhancements were incorporated in CF205R002:
Degraded Disk Detection for drives that exhibit a trend of degrading quality of service.
Parallel Disk Firmware Update enables loading firmware onto multiple disks in a single operation.
The following fixes were incorporated in CF205R002:
Delete schedule doesn't work and hangs terminal, when the task was already deleted.
Junk characters are observed in the event logs when a scheduled task is initiated.
Disabled the HIO sequencer raw ctr QD debug information.
Resolved a flaw in logic in setting Ethernet parameters during the boot up. It is not properly reading the existing settings so forcefully setting it to 10Mbps Half Duplex.
The Help page was blank when using Internet Explorer 11.
Fix for Drive FW upgrade failure.
Fix for "disk detected error" message when rescan, shutdown, restart, firmware code load is performed on 3TB and 4TB SAS MDL drives.
Added changes to the CLI set led command to properly turn on and turn off the of enclosure, controller A, and controller B LEDs.
When trying to set the start "time range" value in the vdisk performance statistics tab, "start time" wass forwarded to 15 minutes prior to the user-specified value.
Fixed MC NOT TALKING issue after changing the IP Address of the Controllers.
Scheduled task did not start drive shutdown. .
Unable to modify user interfaces from WBI.
Warning/error message is not displayed in the same screen for the password setup field if invalid characters are given.
While collecting logs from FTP, getting invalid/ misleading error messages.
Show the complete information of a drive in a disk detected error event message.
Removed unsupported CHAP commands.
Removed DMS-related commands and help since DMS software features are not supported in this product.
Drive scrub status percentage is updating correctly in CLI.
Fixed problems with using a forward slash in a password.
Removed Independent Cache Mode option.
Prevent RAID1 scrubs from starting until cache has completed destaging data that was previously interrupted by a power failure.
User with Monitor role is able to change system settings.
Modified the code to correctly find the number of partitions associated with a specific container while force-changing the preferred owner of the container.
Unable to create an SNMP V3 user with auth type:none and privacy type:DES.
Log messages erroneously indicating an MC is missing or down.
The following fixes were incorporated in CF100P002:
Removed the OpenSSL CVE-2014-0160 (Heartbleed) vulnerability, and applied a newly issued SSL certificate to the array.
Fixed problem where CLI restore users and restore defaults commands did not work when connected directly to the USB port.
Fixed an MTO issue with PCIE Link Recovery.
The following enhancements were incorporated in CF100R038:
Performance improvements.
Eliminate I/O impact on getting logs.
Changes to support 1024 initiators per port.
Increase the system-wide PGR registration limit from 1024 to 32k.
Added support for the CLI down disk command.
Updated algorithm for Compact Flash diagnostic speed test for Tricor C1 P9 component.
Disable PCIE Error stat checking.
The following fixes were incorporated in CF100R038:
Correct the event reporting mechanism for correctable ECC errors.
Eliminate a page fault caused by a metadata locking conflict during global spare drive allocation.
Improve Compact Flash error handling to prevent a controller crash.
Implement a chip supplier's recommended timing change to prevent a rare SAS chip failure during initialization.
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 reprogramming. | |
CAUTION: Before upgrading firmware, ensure that the system is stable and is not being reconfigured or changed in any way. If changes are in progress, monitor them and wait until they are completed before proceeding with the upgrade. | |
NOTE: To install this firmware, you must download the firmware package from the Dot Hill Customer Resource Center and save the file to your local filesystem. Ensure that FTP and telnet are enabled. | |
As with any firmware upgrade, it is a recommended best practice to ensure that you have a full backup prior to the upgrade.
When planning for a firmware upgrade, schedule an appropriate time to perform an online upgrade.
For dual domain 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.
When planning for a firmware upgrade, allow sufficient time for the update.
During the installation process, monitor the system to determine update status and know when the update is complete.
After the installation process is complete and all controllers have automatically restarted, verify system status in RAIDar or the CLI and confirm that the new firmware version is displayed as running on all controllers.
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 current version of the Event Descriptions Reference Guide.
If you experience issues during the installation process, do the following:
When viewing system version information in the RAIDar 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 web 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 will happen:
Updated system version information is displayed and the new firmware version shows that it was installed.
The Partner Firmware Update process will automatically begin and will install 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.
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 information displayed is correct.
If the show disks command fails to display the disks correctly, communications within the controller have failed. To reestablish 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.
NOTE: It takes approximately 10 minutes for the firmware to load and for the automatic restart to complete. Progress messages are displayed in the FTP interface during that time. Wait for the progress messages to specify that the firmware load has completed. If the system Partner Firmware Update (PFU) option is enabled, allow an additional 20 minutes for the partner controller to be updated. No messages are displayed in the FTP interface during PFU. | |
A controller enclosure can contain one or two controller modules. In a dual-controller system, both controllers should run the same firmware version. Storage systems in a replication set must run the same firmware version. You can update the firmware in each controller module by loading a firmware file obtained from the enclosure vendor.
If you have a dual-controller system and the Partner Firmware Update option is enabled, when you update ne controller the system automatically updates the partner controller. If Partner Firmware Update is disabled, after updating firmware on one controller you must log into the partner controller's IP address and perform this firmware update on that controller also.
For best results, the storage system should be in a healthy state before starting firmware update.
Firmware update is supported from any of the following versions: CF100R003-02, CF100R036.
To update controller-module firmware:
Obtain the appropriate firmware file and download it to your computer or network.
If the storage system has a single controller, stop I/O to the system before you start the firmware update.
Restart the Management Controller (MC) in the controller to be updated; or if PFU is enabled, restart the MCs in both controllers.
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.
If you have a dual-controller system and want firmware to be automatically updated in both controllers, under Partner Firmware Upgrade select the Enabled check box and click Set. (PFU is enabled by default.) Otherwise, if PFU is disabled, after updating firmware on one controller you must log into the partner controller and perform this firmware update on that controller also.
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.
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 or 3 minutes for each EMP in an expansion enclosure.
If the Storage Controller cannot be updated, the update operation is cancelled. 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 10 to 20 minutes for the partner controller to be updated.
Clear your web browser cache, then sign in to RAIDar. 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.
An expansion enclosure can contain one or two expansion modules. Each expansion module contains an enclosure management processor (EMP). All modules of the same model should run the same firmware version.
Expansion-module firmware is updated in either of two ways:
When you update controller-module firmware, all expansion modules are automatically updated to a compatible firmware version.
You can update the firmware in each expansion module by loading a firmware file obtained from the enclosure vendor.
To update expansion module firmware:
Obtain the appropriate firmware file and download it to your computer or network.
If the storage system has a single controller, stop I/O to the system before you start the firmware update.
In the banner click the system panel and select Update Firmware.
In the System topic select Action > Update Firmware.
The Update Firmware panel opens.
Select the Update Expansion Modules tab. This tab shows information about each expansion module in the system.
Click OK. Messages show firmware-update progress.
It typically takes 3 minutes to update each EMP in an expansion enclosure. Wait for a message that the code load has completed.
Verify that each updated expansion module has the new firmware version.
NOTE: It takes approximately 10 minutes for the firmware to load and for the automatic restart to complete. Progress messages are displayed in the FTP interface during that time. Wait for the progress messages to specify that the firmware load has completed. If the system Partner Firmware Update (PFU) option is enabled, allow an additional 20 minutes for the partner controller to be updated. No messages are displayed in the FTP interface during PFU. | |
A controller enclosure can contain one or two controller modules. In a dual-controller system, both controllers should run the same firmware version. Storage systems in a replication set must run the same firmware version. You can update the firmware in each controller module by loading a firmware file obtained from the enclosure vendor.
If you have a dual-controller system and the Partner Firmware Update option is enabled, when you update one controller the system automatically updates the partner controller. If Partner Firmware Update is disabled, after updating firmware on one controller you must log into the partner controller's IP address and perform this firmware update on that controller also.
For best results, the storage system should be in a healthy state before starting firmware update.
Firmware update via FTP is supported from any of the following versions: CF100R003-02, CF100R036.
To update controller-module firmware:
Obtain the appropriate firmware file and download it to your computer or network.
Place the downloaded firmware package in a temporary directory.
In RAIDar, prepare to use FTP:
In single-domain environments, halt I/O to vdisks before starting the firmware update.
Restart the Management Controller (MC) in the controller to be updated; or if PFU is enabled, restart the MCs in both controllers.
Open a command prompt (Windows) or a terminal window (UNIX), and navigate to the directory containing the firmware file to load.
If needed, repeat these steps to load the firmware on additional modules.
If the Storage Controller cannot be updated, the update operation is cancelled. If the FTP prompt does not return, quit the FTP session and log in again. 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, the message Operation Complete is printed, the FTP session returns to the ftp> prompt, and the FTP session to the local MC is closed.
Clear your web browser's cache and then sign in to RAIDar. In the RAIDar display, verify that the proper firmware version appears for each module. If PFU is running on the controller you sign in to, a dialog box shows PFU progress and prevents you from performing other tasks until PFU is complete.
NOTE: If you attempt to load an incompatible firmware version, the message | |
NOTE: If you are using a Windows FTP client, during firmware update a client-side FTP application issue can cause the FTP session to be aborted. If this issue persists, try using Storage Management Console to perform the update, use another client, or use another FTP application. | |
NOTE: After firmware update has completed on both controllers, if the correct version does not appear for a component or 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. | |
Issue: A drive FW updated success message pop-up window occurs continuously. Workaround: Reset the MC. |
Issue: The CLI show redundancy-mode command reports a controller is operational when it is down. |
Issue: When replacing a controller while logged in to the other controller, the CLI session is disconnected with no warning other than a "Killed" message. Workaround: After a brief wait, log back in to the controller. If that session is killed, wait before logging back in. |
Issue: In a VMware environment, if no LUN 0 exists host drivers might be unable to find a LUN to which they should have access. Workaround: Use the CLI set advanced-settings command or RAIDar's Advanced Settings to set Missing LUN Response to illegal (Illegal Request). |
Issue: Cannot use both controller FC ports at the same time when Independent Cache mode is enabled. Workaround: Disable independent cache. |
| Firmware version | Release date |
| CF205R002 | November 2014 |
| CF100P002 | May 2014 |
| CF100R038-02 | October 2013 |
| CF100R036 | July 2013 |
| CF100R003-02 | September 2012 |
Rev. A | Part number: |