3 updating the syncro cs controller firmware – Avago Technologies Syncro 9361-8i User Manual
Page 64
Avago Technologies
- 64 -
Syncro CS 9361-8i and Syncro CS 9380-8e Solution User Guide
October 2014
Chapter 3: System Administration
Updating the Syncro CS Controller Firmware
3.3
Updating the Syncro CS Controller Firmware
Follow these steps to update the firmware on the Syncro CS controller board. You must perform the update only on
the controller node that is not currently accessing the drive groups.
NOTE
Be sure that the version of firmware selected for the update is specified
for Syncro CS controllers. If you updating to a version of controller
firmware that does not support Syncro CS controllers, you will
experience a loss of HA-DAS functionality.
1.
If necessary, perform a planned failover as described in the previous section to transfer control of the drive groups
to the other controller node.
2.
Start the MSM utility on the controller node that does not currently own the cluster.
NOTE
To determine which node currently owns the cluster in Windows
Server 2012, follow the steps in Section
, up to step
, where information about the
cluster disks is displayed in the center panel. The current owner of the
cluster is listed in the Owner Node column.
3.
In the left panel of the MSM window, click the icon of the controller that requires an upgrade.
4.
In the MSM window, select Go To > Controller > Update Controller Firmware.
5.
Click Browse to locate the .rom update file.
You cannot perform controller firmware update until the firmware update process on this node is complete.
6.
After you locate the file, click Ok.
The MSM software displays the version of the existing firmware and the version of the new firmware file.
7.
When you are prompted to indicate whether you want to upgrade the firmware, click Yes.
A pop-up window appears that asks whether you want to perform an Online Firmware Update (OFU, also referred
to as ResetNow).
NOTE
In Syncro CS, if you allow IOs during a firmware update (that has a
cache layout change), then when the new firmware takes over after
reboot, the controller cannot recover the cache that still needs to be
written to the drives (dirty cache). The new local IOs (even though they
are in write-through mode) and the mirror IOs are marked as dirty
cache after the new firmware takes over.
To have the controller recover any dirty cache, select the OFU option
when you update the firmware.
8.
Click Yes or No in the pop-up window.
The controller is updated with the new firmware code contained in the .rom file.
NOTE
If you select OFU, the controller reboots after the new firmware is
flashed, and you do not need to reboot the system.
9.
If you did not select OFU in step
, reboot the controller node after the new firmware is flashed.
The new firmware does not take effect until reboot.
10. If desired, use planned failover to transfer control of the drive groups back to the controller node you just
upgraded.
11. Repeat this process for the other controller.
12. Restore the cluster to its non-failed-over mode.