You can downgrade HA pairs within a Data ONTAP release family while maintaining storage system availability. This nondisruptive downgrade method has several steps: initiating a failover operation on one system, updating the "failed" system (and if necessary, its firmware), initiating giveback, and repeating the process on the other system.
Preparatory prerequisites must be satisfied.
If the HA pair is enabled, the cf status command output should be similar to the following:
Cluster enabled, systemA is up.
If you... | Then... |
---|---|
Have already installed system files | At the console of each system, enter the following command to activate the new code on the storage system's boot device: download The download command provides an acknowledgment similar to the following: Tue Jun 19 10:03:22 GMT [download.request:notice]: Operator requested download initiated download: Downloading boot device ...................... download: Downloading boot device (Service Area) Then a message similar to the following appears: Tues Jun 19 10:11:51 GMT [download.requestDone:notice]: Operator requested download completed Note: The storage system console is unavailable until the
download procedure is complete.
|
Are installing and downloading system files in the same operation | At the console of each system, enter the following command:
software update
url|file When you use the software update command without the -d option, the download command is executed by default. |
nn is a notification period (in minutes) appropriate for your clients after which CIFS services are terminated. After that period of time, proceed to the next step.
This command causes system A to shut down gracefully and leaves system B in takeover mode.
The recovery time is client-specific and may take longer than 8 minutes depending on the characteristics of the client applications.
If giveback is not initiated, complete the following steps:
For more information about the -f option, see the cf(1) man page.
System A reboots with the new system configuration—a Data ONTAP version or other system firmware and hardware changes—and resumes normal operation as an HA pair partner.
System B is brought down and updated while partner A is in takeover mode.