Nondisruptive upgrades

At the console of each filer, enter the following command to copy the executables to the boot blocks of the filer'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 6.5.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 filer console is unavailable until the download procedure is complete.

At the console of each filer, 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.2_i1

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

1:/x86/firmware/xfiler/firmware.img: Firmware 4.2.2_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 filer does not need a system firmware update.
• Later than the installed firmware displayed by sysconfig, your filer 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 Filer A

Go to Step 4.

CIFS is in use in Filer A

Enter the following command:

cifs terminate -t nn

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

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

cf takeover

Result

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

Note
When filer A displays the Waiting for giveback message, you can also halt filer 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

Got to Step 12.

If you need to update system firmware

Go to Step 6.

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

• Enter Del at the filer A console when instructed after the boot sequence starts.
• When the Waiting for giveback message appears on the console of filer A, enter Ctrl-C at the filer 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 downloaded and installed the 4.2.2 or the 4.2.3 firmware upgrade, or if you are upgrading from 4.2.2 or 4.2.3 to 4.3 firmware, you must run the set-defaults command from the firmware ok prompt before rebooting your filer. For more information, see the Bug ID 105365 public report (on the NOW site at http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=105365).

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

bye

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

cf giveback

Result

This command causes filer 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.

Repeat Step 3 through Step 12 to update the partner filer; in other words, bring down and update filer B with partner A in takeover mode.

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