Nondisruptive upgrades within release families

At the console of each storage system, enter the following command to copy the executables to the boot blocks of the storage system's hard disks:

download

Result

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 disks: opening Data ONTAP 7.1 

.......................done

download: boot blocks successfully copied to disk(s)

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.

At the console of each storage system, enter the following command to verify that clustering is enabled:

cf status

Result

The cf status command output should be similar to the following:

Cluster enabled, filerA is up.

VIA Interconnect is up (link 0 up, link 1 down).

If the output says that clustering is not enabled, enter the following command to enable clustering:

cf enable

At the console of each storage system, enter the following commands to compare the installed version of system firmware with the version on the CompactFlash card:

sysconfig -a

version -b

Result

The sysconfig command output contains an entry similar to the following:

Firmware release:   4.3_i1

The version command output contains an entry similar to the following:

1:/x86/firmware/xfiler/firmware.img: Firmware 4.3.1_i2

If the version of the newly loaded firmware displayed by the version command is

• The same as the installed firmware version displayed by sysconfig, your storage system does not need a system firmware update
• Later than the installed firmware displayed by sysconfig, your storage system needs a system firmware update
• Earlier than the installed firmware displayed by sysconfig, do not update system firmware with the update-flash command

If...

Then...

CIFS is not in use in system A

Go to Step 5.

CIFS is in use in system A

Enter the following command:

cifs terminate -t nn

where nn is a notification period (in minutes) appropriate for your clients. After that period of time, proceed to Step 5.

At the console of system B, enter the following command:

cf takeover

Result

This command causes system A to shut down gracefully and leaves system B in takeover mode.

Note
When system A displays the Waiting for giveback message, you can also halt system A to perform other upgrade and maintenance procedures. For more information, see About nondisruptive cluster upgrades.

If...

Then...

You do not need to upgrade system firmware

Go to Step 13.

If you need to update system firmware

Go to Step 7.

To display the boot prompt (CFE or ok, depending on your storage system) at the system A console, complete one of the following procedures:

• Press Del at the system A console when instructed after the boot sequence starts.
• When the Waiting for giveback message appears on the console of system A, press Ctrl-C at the system A console. When the Continue with boot? message appears, enter no.

At the boot prompt, enter the following command:

bye

During the memory test, press Del to interrupt the boot process.

Note
If you have a terminal emulation package and it does not support Del, use Ctrl-Bksp instead.

Result

The console displays the following messages:

Skipping auto-boot 

Complete

Startup aborted

Then the console displays the boot prompt (CFE or ok).

Enter the following command:

update-flash

Result

The system prompts you to continue.

Enter y to continue.

Result

The system updates the firmware, displays several status messages, and displays the boot prompt.

Note
If you installed a system firmware upgrade on a storage system running Open Firmware (OFW), you might have to run the set-defaults command from the firmware ok prompt before rebooting your storage system. For more information, see Considerations concerning system firmware upgrades.

Enter the following command to reboot the system using the new firmware and software:

bye

If...

Then...

FCP or iSCSI is not in use in system A

When the Waiting for giveback message appears on the console of system A, enter the following command at the console of system B:

cf giveback

Result

This command causes system A to reboot with the new system configuration--a Data ONTAP version or other system firmware and hardware changes--and resume normal operation as a cluster partner.

FCP or iSCSI is in use in system A

When the Waiting for giveback message appears on the console of system A, wait for at least 8 minutes to allow host multipathing software to stabilize. Then enter the following command at the console of system B:

cf giveback

Result

This command causes system A to reboot with the new system configuration--a Data ONTAP version or other system firmware and hardware changes--and resume normal operation as a cluster partner.

If...

Then...

FCP or iSCSI is not in use in system A

Repeat Step 4 through Step 13 to update the partner storage system; in other words, bring down and update system B with partner A in takeover mode.

FCP or iSCSI is in use in system A

After system A resumes normal operation as a cluster partner, wait for at least 8 minutes to allow host multipathing software to stabilize. Then repeat Step 4 through Step 13 to update the partner storage system; in other words, bring down and update system B with partner A in takeover mode.

As needed, perform the procedures described in Concluding the upgrade.