Upgrading a FAS2040 system with internal storage in an HA

pair to a FAS32xx system in an HA pair

You can upgrade your FAS2040 system with internal storage in an HA pair to a FAS32xx system in an HA pair by copying all
the volumes on the FAS2040 system to the FAS32xx system in addition to moving any attached disk shelves.
Before you begin

The system you are upgrading to must support at least as many disks as the original system.
The Hardware Universe (formerly the System Configuration Guide) at support.netapp.com/knowledge/docs/hardware/
NetApp/syscfg/index.shtml lists the number of disks that each system supports.
You must have enough storage attached to the FAS32xx system to accommodate all the volumes copied from the FAS2040
system.
If your system is in an FC or iSCSI environment, you need to record all LUN serial numbers and WWNs before upgrading
the system so you can verify that they remain unchanged after the upgrade.
See the Data ONTAP SAN Administration Guide for 7-Mode.

About this task

This procedure is disruptive.

This procedure is written with the following assumptions:

You are upgrading from a FAS2040 system that has internal storage and that might have attached disk shelves.
You are upgrading to a FAS3210, FAS3240, or FAS3270 system that is running Data ONTAP 7.3.5 or later version in the
7.3.x release family or to Data ONTAP 8.x, or you are upgrading to a FAS3220 or FAS3250 system running Data ONTAP
8.1.2. FAS3220 and FAS3250 systems do not run versions of Data ONTAP earlier than 8.1.2.
Note: The FAS32xx system must already have installed the version of Data ONTAP that you want to use before you
upgrade the hardware.

If you want to upgrade from Data ONTAP 7.3.5 or later version in the 7.3.x release family to Data ONTAP 8.x, see the
Data ONTAP Upgrade and Revert/Downgrade Guide for 7-Mode on the NetApp Support Site at support.netapp.com.
If you want to revert to Data ONTAP 7.3.5 or later version in the 7.3.x release family on a FAS32xx running Data
ONTAP 8.x, see the Knowledgebase article, How to revert Data ONTAP 8.0.1 for FAS/V32xx on the NetApp Support
Site at support.netapp.com.

You are upgrading to a FAS32xx system that has at least one attached disk shelf.
If your system is in an FC or iSCSI environment, you might need to take additional steps.
See the Data ONTAP Upgrade and Revert/Downgrade Guide for 7-Mode and the Data ONTAP SAN Administration Guide
for 7-Mode.
Your FAS2040 system and the FAS32xx system might have Storage Encryption on its disk drives.
Storage Encryption is supported on FAS2040 and FAS32xx systems in Data ONTAP 8.0.1 and later releases in the 8.x
family.
You have basic UNIX administration skills and experience managing storage.
Note: If your system is in an ESX environment, after you replace a controller or an NVRAM card, LUN serial numbers might

change to reflect a serial number based on the new NVRAM ID. This causes an unnecessary resignature event that should be
avoided. See the knowledgebase article, What causes ESX VMFS to "disappear"? on the NetApp Support Site at
support.netapp.com.

215-07166_A0 ur002

Copyright 2012 NetApp, Inc. All rights reserved.

Steps

1.
2.
3.
4.
5.
6.

Gathering tools and documentation on page 2

Preparing the site and equipment for the upgrade on page 3
Guidelines for copying volumes and resizing root volumes on page 6
Copying volumes on page 7
Completing the upgrade on page 9
Decommissioning the old system on page 16

Gathering tools and documentation

Before beginning the upgrade process, you need to gather the necessary tools and recommended documentation.
Steps

1. Gather the tools you need to perform the upgrade:

Grounding strap
#2 Phillips screwdriver

2. Download from the NetApp Support Site the documents that contain information you need or might find helpful during the
upgrade.
Document

Contents

Site Requirements Guide

Contains information about the physical requirements of storage systems.

Data ONTAP Data Protection Online

Backup and Recovery Guide for 7-Mode

Contains instructions for backing up data on the system and detailed

information about using SnapMirror and the vol copy command.

Data ONTAP Software Setup Guide for 7Mode

Contains information about using Data ONTAP to set up and configure

storage systems. Also contains information about Storage Encryption.

Data ONTAP System Administration Guide

for 7-Mode

Contains instructions for editing files in the /etc directory, setting up the
Baseboard Management Controller (BMC), and performing other
administrative tasks.

Data ONTAP Upgrade and Revert/

Downgrade Guide for 7-Mode

Contains instructions for downloading Data ONTAP.

Data ONTAP Storage Management Guide

for 7-Mode

Contains instructions about the following tasks:

Copying volumes using SnapMirror or the vol copy command

Using the vol create and vol restrict commands
Reassigning disks
Modifying RAID groups
Resizing flexible volumes

Also contains information about minimum size of root flexible volumes and
about Storage Encryption.

32xx Installation and Setup Instructions

Contains information for installing and cabling the FAS32xx system.

Data ONTAP High Availability and

MetroCluster Configuration Guide for 7Mode

Contains cabling instructions and other information for high-availability

(HA) pairs.

The appropriate disk shelf guide.

Contains instructions for installing and monitoring disk shelves.

Upgrading a FAS2040 system with internal storage in an HA pair to a FAS32xx system in an HA pair

Document

Contents

Universal SAS and ACP Cabling Guide

Contains information for cabling SAS shelves applicable to all platforms.

Commands: Manual Page Reference

Contains the content of the manual (man) pages.

The NetApp Support Site also contains documentation about disk shelves, NICs, and other hardware that you might use with
your system. It also contains the Hardware Universe, which provides information about the hardware that the new system
supports.
Note: This document uses the term HA pair to describe two-controller storage systems in which one controller takes over
and serves data if the other controller fails. Before the release of Data ONTAP 8.0, such systems were called active/active
configurations.

Preparing the site and equipment for the upgrade

You need to provide sufficient space for the FAS32xx system, ensure that it supports the hardware that you plan to migrate,
obtain information for setting up the SPs, install the FAS32xx controllers, and then rename the root volume on one of the
systems. You also might need to upgrade Data ONTAP on your FAS2040 system.
Before you begin

You need to decide whether to use the root volume of your FAS2040 system or the root volume of the FAS32xx on the
upgraded system.
Your choice determines whether you rename the FAS2040 system root volume or the FAS32xx system root volume.
You need to plan port migration from your FAS2040 system to the FAS32xx system.
During the procedure, you match the port locations on your FAS2040 system to those on the FAS32xx system.
Note: FAS2040 systems have four onboard GbE ports per controller, but FAS32xx systems have two GbE ports per
controller. If all the onboard GbE ports on your FAS2040 system are being used, you need to add one or more GbE
adapters to the FAS32xx system.

Steps

1. Measure the amount of space that you have in your equipment rack or system cabinet.
FAS32xx chassis are 3U high. You must allow for the appropriate amount of space for the system.
2. Check the Hardware Universe to ensure that the FAS32xx system supports the disk shelves and any tape devices that you are
migrating from your FAS2040 system.
3. If you want to migrate a tape device, verify support for the new configuration on the NetApp Support Site at
support.netapp.com and with the backup application vendor.
4. Obtain IP addresses, mailhost addresses, and other information for the SPs on the FAS32xx system.
Note: Both the BMCs on the FAS2040 system and the SPs on the FAS32xx system are remote management ports. If you
used the BMCs on your FAS2040 system, you might want to reuse their network parameters on the FAS32xx system.

5. Check the system invoice for the version of Data ONTAP installed on the FAS32xx system.
The same version of Data ONTAP must be installed on your FAS2040 system and the FAS32xx system when you begin the
upgrade procedure. If you are upgrading to a FAS3210, FAS3240, or FAS3270 system, the version must be Data ONTAP
7.3.5 or Data ONTAP 8.0.1 or later. If you are upgrading to a FAS3220 or FAS3250 system, the version must be Data
ONTAP 8.1.2 or later.
6. Take one of the following actions:

If the version of Data ONTAP

on your FAS2040 system is...

Then...

The same as the version on the

FAS32xx system

Go to Step 7.

Different from the version on the Go to the NetApp Support Site at support.netapp.com, navigate to the software download page, and
FAS32xx system
download the version of Data ONTAP for your FAS2040 system that matches the version installed on
the FAS32xx system.
Note: Downloads of the same version of Data ONTAP differ according to system model. You
must choose the correct file for the model of your system.
Note: Make sure that you download the .zip or .tar file to a directory that is accessible to your
FAS2040 system.
See the Data ONTAP Upgrade Guide for instructions about how to download Data ONTAP.

7. Back up the data on your FAS2040 system.

Be sure to copy or save any information about site-specific customizations that you might want to reuse or save for
reference.
8. Install the FAS32xx system and any attached disk shelves, as described in the Installation and Setup Instructions.
9. Take one of the following actions, depending on the version of Data ONTAP installed on your FAS2040 system:
If the version of Data ONTAP on your
FAS2040 system is...

Then...

The same as the version of Data ONTAP on

the FAS32xx system

Go to Step 10.

Different from the version of Data ONTAP

on the FAS32xx system

a. On either controller of your FAS2040 system, install the version of Data ONTAP that
you downloaded in Step 6 by entering the following command:
software update url -r
url is the location of the Data ONTAP system files (.tar or .zip file).
Note: The -r option suppresses the automatic reboot.
b. Repeat the preceding step on the other controller of your FAS2040 system.

10. If you have not done so already, back up the data on both controllers of your FAS2040 system.
11. Take one of the following actions:
If your FAS2040 system...

Then...

Used Storage Encryption

Complete Step 12 through Step 15 on both controllers of the FAS2040 system, all the steps first on one
controller, then all the steps on the other controller, and then go to Step 16.
Note: Contact technical support to perform an optional step to preserve the security of the encrypted
drives by rekeying all drives to a known authentication key.

Did not use Storage

Encryption

Go to Step 16.

12. Display the key ID for each self-encrypting disk on the FAS2040 system by entering the following command at the system
prompt:
disk encrypt show
Example
disk encrypt show
Disk
Key ID
4

Locked?
Upgrading a FAS2040 system with internal storage in an HA pair to a FAS32xx system in an HA pair

0c.00.1
0c.00.0
0c.00.3
0c.00.4
0c.00.2
0c.00.5

0x0
080CF0C8000000000100000000000000A948EE8604F4598ADFFB185B5BB7FED3
080CF0C8000000000100000000000000A948EE8604F4598ADFFB185B5BB7FED3
080CF0C8000000000100000000000000A948EE8604F4598ADFFB185B5BB7FED3
080CF0C8000000000100000000000000A948EE8604F4598ADFFB185B5BB7FED3
080CF0C8000000000100000000000000A948EE8604F4598ADFFB185B5BB7FED3

No
Yes
Yes
Yes
Yes
Yes

The first disk in the example is associated with an MSID (the default Security ID set by the manufacturer); the others are
associated with a non-MSID.
13. Examine the output of the disk encrypt show command, and if any disks are associated with a non-MSID key, rekey
them to an MSID key by taking one of the following actions:

To rekey disks individually, enter the following command, once for each disk:
disk encrypt rekey 0x0 disk_name

To rekey all disks at once, enter the following command:

disk encrypt rekey 0x0 *

14. Ensure that all the self-encrypting disks are associated with an MSID by entering the following command and examining the
output:
disk encrypt show

15. Obtain an IP address for the external key management server.

See the Data ONTAP Software Setup Guide for 7-Mode for more information about the external key management server.
16. Take one of the following actions:
If you want to use the root volume of
the...

Then...

FAS2040 system

Complete Step 17, skip Step 18, complete Step 19 through 22, and then go on to the next
section.

FAS32xx system

Skip Step 17, complete Step 18 through Step 22, and then go on to the next section.

17. Rename the root volume on the FAS32xx system, using one of the following methods:
If the FAS32xx system has a...

Then...

Traditional root volume

Rename the root volume by entering the following command:

vol rename your_root_vol_name old_vol0

Flexible (FlexVol) root volume

Rename the root volume and the corresponding aggregates by entering the following commands:
vol rename your_root_vol_name old_vol0
aggr rename your_aggr_name old_aggr0

18. Rename the root volume on the FAS2040 system, using one of the following methods:
If your FAS2040 has a...

Then...

Traditional root volume

Rename the root volume by entering the following command:

vol rename your_root_vol_name old_vol0

FlexVol root volume

Rename the root volume and the corresponding aggregates by entering the following commands:
vol rename your_root_vol_name old_vol0
aggr rename your_aggr_name old_aggr0

19. Repeat Step 17 or Step 18 on the other controller, depending on the root volume that you renamed.
20. Make sure that the port locations on the FAS2040 system match those on the FAS32xx system.
5

There are two methods for matching port locations.

Running the setup command on the FAS2040 system and entering the port information at the appropriate prompts.
This is the recommended method. For information about the setup command, see the Data ONTAP Software Setup
Guide for 7-Mode.
Editing the /etc/rc file in the root volume of the FAS2040 system and then saving the file on the system.
This method requires that you have an external client and that you are knowledgeable about the file contents.
Attention: Take great care in editing the /etc/rc file, which contains startup commands for the system and network
parameters. For information about editing the files in the /etc directory, see the Data ONTAP System Administration

Guide for 7-Mode.

Note: You might need to update the /etc/hosts file or update host information after entering the setup command or
editing the /etc/rc file if host names contain appended interface IDs.

21. After you match the port locations, transfer the information you entered to the storage system by entering the following
command, as directed by the prompt on the screen:
reboot

22. Repeat Step 21 and Step 22 on the other controller.

Guidelines for copying volumes and resizing root volumes

You need to copy the volumes on the internal disk drives of your FAS2040 system to the FAS32xx system before you replace
the hardware. You also might need to resize the root volume of the FAS2040 system if you plan to use it on the upgraded
system.
Methods of copying volumes
There are two methods of copying volumes:

The SnapMirror feature of Data ONTAP

SnapMirror is the preferred method because it copies volumes quickly and does not require you to edit files in the /etc
directory. However, you need a license to use SnapMirror.
The vol copy command
You do not need a license to copy volumes with the vol copy command. However, you need to edit files in the /etc
directory before entering the command, and copying with the vol copy commands takes longer than copying with
SnapMirror.

When you might need to resize the FAS2040 FlexVol root volume
You might need to resize the FAS2040 root volume only if both of the following conditions are true:

You use the FAS2040 root volume on the upgraded system.

The FAS2040 root volume is a FlexVol volume.

Each storage system has minimum size requirements for root volumes when the root volume is a FlexVol volume. If you use a
FlexVol FAS2040 root volume on the upgraded system, it needs to match the minimum FlexVol root volume size on the
FAS32xx system. If necessary, you can resize the root volume after you copy volumes and while you complete the upgrade.
Note: You do not need to resize the root volume of your FAS2040 system if it is a traditional volume, even if you plan to use
it on the upgraded system. You do not need to resize the root volume of the FAS32xx system, even if it is a FlexVol root
volume.

Aggregate requirements if you resize the FAS2040 FlexVol root volume

If you need to resize the FAS2040 FlexVol root volume, before you do so, you perform the following tasks:

Upgrading a FAS2040 system with internal storage in an HA pair to a FAS32xx system in an HA pair

Identify the aggregate that will contain the FlexVol root volume on the upgraded system
Ensure that the aggregate has enough space to accommodate the resized FlexVol root volume
Note: You need to perform these steps regardless of whether the root volume is on an internal disk drive or an external disk

drive.
The following list shows the minimum FlexVol root volume size required by each FAS32xx model:

FAS3210: 151 GB for Data ONTAP 8.x; 17 GB for Data ONTAP 7.3.5
FAS3220: 250 GB for Data ONTAP 8.1.2
FAS3240: 205 GB for Data ONTAP 8.x; 22 GB for Data ONTAP 7.3.5
FAS3250: 250 GB for Data ONTAP 8.1.2
FAS3270: 250 GB for Data ONTAP 8.x; 30 GB for Data ONTAP 7.3.5

If you are upgrading using the FAS2040 FlexVol root volume, and that FlexVol root volume is on an external disk drive, be
aware that the aggregate might not be able to accommodate a resized root volume. If that is the case, you need to copy the
FlexVol root volume to an aggregate that can accommodate the resized root volume, or you need to add additional external
storage.
See the Data ONTAP Storage Management Guide for 7-Mode for information about root volumes, minimum FlexVol root
volume sizes, and aggregates.

Copying volumes
Copying volumes consists of creating matching volumes on the FAS32xx system, restricting the volumes, and then using
SnapMirror or the vol copy command to copy the volumes on the FAS2040 system to the FAS32xx system.
Before you begin

You need to read and understand the documentation about using the SnapMirror feature of Data ONTAP or the Data
ONTAP vol copy command.
Information about SnapMirror and the vol copy command is in the Storage Management Guide, Data Protection Online
Backup and Recovery Guide, and the man pages.
You need to read and understand the information about copying and resizing volumes in the section Guidelines for copying
volumes and resizing root volumes.
If you plan to upgrade using the root volume of your FAS2040 system, you need to verify that certain files are present on the
FAS2040 controllers:

/etc/rc, /etc/registry, and /etc/boot if the system you are upgrading to is running Data ONTAP 7.3.5
/etc/rc and /etc/registry if the system you are upgrading to is running Data ONTAP 8.x.

If the files are not present, you should restore them from backup.
Steps

1. Take one of the following actions, depending on the method that you plan to use to copy the volumes on your FAS2040
system.

If you plan to
copy volumes
using...

Then...

SnapMirror

a. Make sure that a SnapMirror license is installed on both controllers of the FAS2040 system and both controllers of
the FAS32xx system.
b. Display the SnapMirror options on both controllers of the FAS2040 system by entering the following command:
options snapmirror
c. On each controller, ensure that the option snapmirror.access has the value host=host_name/IP
address of destination system and that the option snapmirror.enable is set to on, as shown in
the following example:
> options snapmirror
snapmirror.access host=host_name/IP address of destination system
snapmirror.checkip.enable off
snapmirror.delayed_acks.enable on
snapmirror.enable on
snapmirror.log.enable on
snapmirror.vbn_log_enable off (value might be overwritten in takeover)
d. On both controllers of the FAS32xx system, ensure that the option snapmirror.enable is set to on.

The vol
copy
command

a. Make sure that RSH is enabled on the FAS2040 by entering the following command on both controllers:
options rsh.enable
The console displays the value on if RSH is enabled and off if RSH is not enabled.
b. If RSH is not enabled, enter the following command on both controllers:
options rsh.enable on
c. Define the FAS2040 and FAS32xx systems as the trusted host of the other system by editing the /etc/
hosts.equiv file on each system so that each file includes the other system's host name.
d. Edit the /etc/hosts file to add the loopback address.
For information about editing the /etc/hosts.equiv file, see the Data Protection Tape Backup and Recovery
Guide. For information about editing files in the /etc directory, see the System Administration Guide.

2. On the FAS2040 system, display information about the volumes of the system by entering the following command:
vol status

3. Record the output of the vol status command so that you can use the information in the following steps.
4. On the FAS32xx system, complete the following substeps.
a) Identify the aggregate on the FAS32xx system where you want to copy the root volume of the FAS2040 system and
determine if it is large enough to accommodate the root volume.
Note: In Step 5, you will create volumes on the FAS32xx system to match those on the FAS2040 system. You need to
ensure that you have an aggregate large enough to accommodate the FAS2040 root volume because it is larger than
the FAS32xx root volume.

b) If the aggregate where you want to copy the FAS2040 root volume is too small, find a larger aggregate or create one by
entering the following command:
aggr create aggregate_name disk_count

c) Create additional aggregates, as needed, to accommodate the other volumes that you will copy from the FAS2040 system
by entering the following command for each aggregate:
aggr create aggregate_name disk_count

You need to create aggregates for volumes that are too large for existing aggregates.

Upgrading a FAS2040 system with internal storage in an HA pair to a FAS32xx system in an HA pair

5. On the FAS32xx system, use the vol create command and the parameters appropriate to your system to create volumes
that match those on the FAS2040 in size and type (traditional volume or FlexVol volume).
You need to enter the command once for each volume you are matching. For information about using the vol create
command, see the Storage Management Guide and the man pages.
Note: Both the source and destination volumes must either be traditional volumes or FlexVol volumes. You cannot copy

between different volume types.

6. On the FAS32xx system, restrict client access to the volumes by entering the following command for each volume:
vol restrict volume_name
Note: If a volume contains CIFS shares, warn users by adding the -t cifsdelaytime option and argument to the
command; cifsdelaytime specifies the number of minutes to delay before the volume is taken offline.
Example

The following example shows the command to warn users that the volume will be taken offline in five minutes:
vol restrict volume_name -t 5

7. Copy the volumes on your FAS2040 system to the FAS32xx system, using one of the following methods.
If you use...

Then...

SnapMirror

On the FAS32xx system, enter the following command for each volume:
snapmirror initialize -S source_system:source_volume destination_volume

The vol copy command On the FAS32xx system, enter the following command for each volume:
vol copy start -S source_system:source_volume destination_volume

8. Take one of the following actions, depending on the method you used to copy the volumes.
If you used...

Then...

SnapMirror

On the FAS32xx system, for each volume, break the SnapMirror relationship by entering the following
command:
snapmirror break destination_volume

The vol copy command On the FAS32xx system, bring the volumes online by entering the following command for each volume:
vol online destination_volume

9. If you copied volumes using the vol copy command, and if RSH was disabled before you copied volumes, disable RSH
again on the FAS2040 system by entering the following command on both controllers:
options rsh.enable off

Completing the upgrade

There are two methods of completing the upgrade, depending on whether you plan to use the root volume of the FAS2040
system or the root volume of the FAS32xx system after the upgrade.
Choices

Completing the upgrade using the FAS2040 root volume on page 10

Completing the upgrade using the FAS32xx root volume on page 13

Completing the upgrade using the FAS2040 root volume

Completing the upgrade consists of shutting down and turning off power to the two systems, moving any attached disk shelves
to the FAS32xx controllers, reassigning the disks, updating licenses, enabling the HA pair, and configuring the SP.
Before you begin

You need to verify that the FAS2040 controllers are in an HA pair before you replace them. You can do this by entering the
command disk show -a on one of the controllers and ensuring that you can see the disk assignments for both controllers. If
the controllers cannot access the partner mailbox disks, they cannot perform takeover and giveback for each other.
Steps

1. Disable the HA configuration by entering the following command on either controller of your FAS2040 system and on
either controller of the FAS32xx system:
cf disable

2. Shut down the FAS2040 system and the FAS32xx system by entering the following command on each of their consoles:
halt

3. Properly ground yourself.

4. Turn off power to the FAS32xx system and disk shelves.
5. Turn off the power to the FAS2040 system and any disk shelves attached to the system.
6. Disconnect the cables on the FAS2040 system.
7. Cable any FAS2040 disk shelves to the FAS32xx system, as described in the Installation and Setup Instructions.
Note: If you are migrating SAS disk shelves, you should also connect ACP cabling.

See the Installation and Setup Instructions for the FAS32xx system and the Universal SAS and ACP Cabling Guide for
cabling information.
8. Turn on the disk shelves and then turn on the FAS32xx system.
9. Observe the startup messages on the console of each controller, and when the message Press CTRL-C for special
boot menu appears, press Ctrl-c to display the boot menu on each controller.
10. Select option 5 at the boot menu and continue with the boot on each controller.
The Maintenance mode command prompt (*>) appears.
11. View disk ownership on the FAS32xx system by entering the following command on one of the controllers:
disk show -v
Note: For Step 12 through Step 24, perform each step first on one controller, and then on the other.

12. Assign the disks that you migrated from the FAS2040 system to the FAS32xx system by entering the following command:
disk reassign -s old_sysid -d new_sysid
Note: If you are reassigning disks from the FAS2040 system to both controllers in the FAS32xx system, assign disks from
controller A of the FAS2040 system to controller A of the FAS32xx system and disks from controller B of the FAS2040
system to controller B of the FAS32xx system.

13. Clear the mailbox by entering the following commands:

mailbox destroy local
mailbox destroy partner

10

Upgrading a FAS2040 system with internal storage in an HA pair to a FAS32xx system in an HA pair

Mailbox disks store configuration information and, in HA pairs, maintain consistency between nodes and monitor partner
activity.
14. Exit Maintenance mode by entering the following command at the Maintenance mode prompt:
halt

15. Boot Data ONTAP by entering the following command at the boot loader prompt:
boot_ontap

16. Take one of the following actions, depending on the FAS2040 system root volume type:
If the FAS2040
system had a...

Then...

Traditional root
volume

Bring the root volume from the FAS2040 system online and set it to the traditional or FlexVol root volume for the
FAS32xx system by entering the following commands:
vol online vol0
vol options vol0 root

FlexVol root
volume

Complete the following steps:

a. Bring the aggregate from the FAS2040 system online by entering the following command:
aggr online aggr0
b. Check the size of the FlexVol root volume on the FAS2040 system by entering one of the following commands:
vol size vol_name
df vol_name
The FlexVol root volume of the FAS2040 system must meet the minimum FlexVol root volume size
requirement on the FAS32xx system.
Note: See the minimum FlexVol root volume size requirements for FAS32xx systems in the section
Guidelines for copying volumes and resizing root volumes.
c. If the FlexVol root volume of the FAS2040 system is less than the minimum for the model of FAS32xx to
which you are upgrading, increase it by entering the following command:
vol size vol_name ng
n is the desired size of the volume.
g is gigabytes.
For more information about resizing FlexVol root volumes, see the Data ONTAP Storage Management Guide
for 7-Mode.
d. Set the aggregate from the FAS2040 system to the root volume of the FAS32xx system by entering the
following command:
vol options vol0 root
e. Take one of the following actions if you see a message that begins: Necessary system files are not
present on the volume vol_name.

If the system is running Data ONTAP 7.3.5 or later version of the 7.3.x release family, make sure that you
have performed this procedure correctly to this point, double-check that the /etc/rc, /etc/registry,
and /etc/boot are on the controller, and then perform Substep d again.
If the system is running Data ONTAP 8.x, double-check that /etc/rc and /etc/registry are on the
controller, and then continue with setting the root volume as prompted, ignoring the message if it appears
again.

17. Display the names of the aggregates that you migrated from the FAS2040 system by entering the following command at the
system prompt:
aggr status

11

18. Bring online all the nonroot aggregates that you migrated from the FAS2040 system by entering the following command at
the system prompt, once for each of the aggregates:
aggr online aggr_name

19. Enter the following command at the system prompt:

reboot

This ensures that when you download and install the appropriate version of Data ONTAP, the software package ends up in
the /etc/software directory of the root volume of the old FAS2040 system.
20. Observe the prompt that appears after the reboot, and then take one of the following actions:
If the prompt that appears after the reboot is the...

Then...

FAS32xx system prompt

Complete Step 16 through Step 19 again.

The FAS2040 system prompt

Go to Step 21.

21. Update the licenses by entering the following command, once for each license, at the system prompt:
license add service/protocol code
service/protocol code is the license code that you were given when you bought the license for a service or protocol.
Example
license add ABCDEFG
Note: Make sure to update the cf (controller failover) license on both controllers if the system is running Data ONTAP 8.x
or later. Make sure to update the cluster license on both controllers if the system is running Data ONTAP 7.3.5.

22. Download and install the appropriate version of Data ONTAP by entering the following command:
software update url
url is the location of the Data ONTAP system files (.tar or .zip file).

Do not add the -r option to the software update command to suppress the automatic system reboot. The reboot is
required at this point to activate the licenses and complete the software update.
23. Ensure that your ports are assigned correctly by entering the following command at the system prompt and then changing
information as necessary at the appropriate prompts:
setup

24. Optional: Remove the old root volume by entering one of the following sets of commands.
If the old root volume on the FAS32xx system was a...

Then...

Traditional volume

Remove the old root volume by entering the following commands:

vol offline old_vol0
vol destroy old_vol0

FlexVol volume

Remove the old root volume by entering the following commands:

aggr offline old_aggr0
aggr destroy old_aggr0

25. Modify the RAID groups and volumes as needed, as described in the Storage Management Guide.
26. Enable the HA pair by entering the following command on either controller:
cf enable

27. Verify that the HA pair is set up correctly by entering the following command on one of the controllers:
disk show -a
12

Upgrading a FAS2040 system with internal storage in an HA pair to a FAS32xx system in an HA pair

If the HA pair is set up correctly, the disk show -a command displays disk ownership for both controllers.
28. Enter the following command from the system prompt:
sp setup

29. After the sp setup command runs, configure the SP by answering the questions that appear on the console.
See the Data ONTAP System Administration Guide for 7-Mode.
30. Take one of the following actions:
If the FAS2040 system...

Then...

Used Storage Encryption

Go to Step 31.

Did not use Storage Encryption

Go to the section Decommissioning the old system.

31. Take one of the following actions:

If the FAS32xx
system

Then...

Uses Storage
Encryption

a. Set up the key management server on the FAS32xx system.

You need to follow the instructions for installing the public and private keys and for running the Storage
Encryption setup wizard in the Data ONTAP Software Setup Guide for 7-Mode.
b. Update the Storage Encryption System ID and authentication key on the FAS32xx system to the new key by
completing the following steps:
a. Enter the following command at the system prompt:
key_manager setup
b. Follow the prompts to complete the configuration.
Ensure that a new pass phrase is generated and that you select Yes to lock all drives.
c. Repeat Step 31a and 31b on the other controller.
c. Go to the section Decommissioning the old system.

Does not use

Storage Encryption

Go to the section Decommissioning the old system.

Completing the upgrade using the FAS32xx root volume

Completing the upgrade consists of shutting down and turning off power to the two systems, moving any attached disk shelves
to the FAS32xx controllers, reassigning the disks, updating licenses, enabling the HA pair, and configuring the SP.
Before you begin

You need to verify that the FAS2040 controllers are in an HA pair before you replace them. You can do this by entering the
command disk show -a on one of the controllers and ensuring that you can see the disk assignments for both controllers. If
the controllers cannot access the partner mailbox disks, they cannot perform takeover and giveback for each other.
Steps

1. Disable the HA configuration by entering the following command on either controller of your FAS2040 system and on
either controller of the FAS32xx system:
cf disable

2. Shut down the FAS2040 system and the FAS32xx system by entering the following command on each of their consoles:
halt

3. Properly ground yourself.

13

4. Turn off power to the FAS32xx system and disk shelves.

5. Turn off the power to the FAS2040 system and any disk shelves attached to the system.
6. Disconnect the cables on the FAS2040 system.
7. Cable any FAS2040 disk shelves to the FAS32xx system, as described in the Installation and Setup Instructions.
Note: If you are migrating SAS disk shelves, you should also connect ACP cabling.

See the Installation and Setup Instructions for the FAS32xx system and the Universal SAS and ACP Cabling Guide for
cabling information.
8. Turn on the disk shelves and then turn on the FAS32xx system.
9. Observe the startup messages on the console of each controller, and when the message Press CTRL-C for special
boot menu appears, press Ctrl-c to display the boot menu on each controller.
10. Select option 5 at the boot menu and continue with the boot on each controller.
The Maintenance mode command prompt (*>) appears.
11. View disk ownership on the FAS32xx system by entering the following command on one of the controllers:
disk show -v
Note: For Step 12 through Step 20, complete each step first on one controller, and then on the other.

12. Assign the disks that you migrated from the FAS2040 system to the FAS32xx system by entering the following command:
disk reassign -s old_sysid -d new_sysid
Note: If you are reassigning disks from the FAS2040 system to both controllers in the FAS32xx system, assign disks from

controller A of the FAS2040 system to controller A of the FAS32xx system and disks from controller B of the FAS2040
system to controller B of the FAS32xx system.
13. Clear the mailbox by entering the following commands:
mailbox destroy local
mailbox destroy partner

Mailbox disks store configuration information and, in HA pairs, maintain consistency between nodes and monitor partner
activity.
14. Exit Maintenance mode by entering the following command at the Maintenance mode prompt:
halt

15. Boot Data ONTAP by entering the following command at the boot loader prompt:
boot_ontap

16. Display the names of the aggregates that you migrated from the FAS2040 system by entering the following command at the
system prompt:
aggr status

17. Bring online all the nonroot aggregates that you migrated from the FAS2040 system by entering the following command at
the system prompt, once for each of the aggregates:
aggr online aggr_name

18. Check the volume status by entering the following command at the system prompt:
vol status

19. Optional: Copy data from the old root volume to the new system's disks.
This step preserves the data from the old root volume if you remove the old root volume in the optional next step.

14

Upgrading a FAS2040 system with internal storage in an HA pair to a FAS32xx system in an HA pair

20. Optional: Remove the old root volume by entering one of the following sets of commands:
If the old root volume on the FAS2040 system was a...

Then...

Traditional volume

Enter the following commands:

vol offline old_vol0
vol destroy old_vol0

FlexVol volume

Enter the following commands:

vol offline old_vol0
vol destroy old_vol0
aggr offline old_aggr0
aggr destroy old_aggr0

21. Modify the RAID groups and volumes as needed, as described in the Storage Management Guide.
22. Update the licenses by entering the following command, once for each license, at the system prompt of both controllers:
license add service/protocol code
service/protocol code is the license code that you were given when you bought the license for a service or protocol.
Note: Make sure to update the cf (controller failover) license on both controllers if the system is running Data ONTAP 8.x
or later. Make sure to update the cluster license on both controllers if the system is running Data ONTAP 7.3.5.

23. Enter the following command at the system prompt of both controllers:
halt

24. Enter the following command at the boot environment prompt of both controllers:
boot_ontap

25. Ensure that your ports are assigned correctly by entering the following command at the system prompt and then changing
information as necessary at the appropriate prompts:
setup

26. Enable the HA pair by entering the following command on either controller:
cf enable

27. Verify that the HA configuration is set up correctly by entering the following command on one of the controllers:
disk show -a

If the HA configuration is set up correctly, the disk show -a command displays disk ownership for both controllers.
28. Enter the following command from the system prompt:
sp setup

29. After the sp setup command runs, configure the SP by answering the questions that appear on the console.
See the Data ONTAP System Administration Guide for 7-Mode for more information about setting up the SP.
30. Take one of the following actions:
If the FAS2040 system...

Then...

Used Storage Encryption

Go to Step 31.

Did not use Storage Encryption

Go to the section Decommissioning the old system.

31. Take one of the following actions:

15

If the FAS32xx
system

Then...

Uses Storage
Encryption

a. Set up the key management server on the FAS32xx

You need to follow the instructions for installing the public and private keys and for running the Storage
Encryption setup wizard in the Data ONTAP Software Setup Guide for 7-Mode.
b. Update the Storage Encryption System ID and authentication key on the FAS32xx system to the new key by
completing the following steps:
a. Enter the following command at the system prompt:
key_manager setup
b. Follow the prompts to complete the configuration.
Ensure that a new pass phrase is generated and that you select Yes to lock all drives.
c. Repeat Step 31a and 31b on the other controller.
c. Go to the section Decommissioning the old system.

Does not use

Storage Encryption

Go to the section Decommissioning the old system.

Decommissioning the old system

After upgrading, you can decommission the old system through the NetApp Support Site. Decommissioning the system tells
NetApp that the system is no longer in operation and removes it from support databases.
Steps

1. Go to the NetApp Support Site at support.netapp.com and log in.

2. Click the link My Installed Products.
3. On the Installed Products page, enter the serial number of the old system in the form and then click Go!
A new page displays information about the controller.
4. Make sure that the information about the controller is correct.
If the information about the controller is...

Then...

Correct...

a. Select Decommission this system in the Product Tool Site drop-down menu.
b. Go to Step 5.

Not correct...

a. Click the feedback link to open the form for reporting the problem.
b. Fill out and submit the form.

5. On the Decommission Form page, fill out the form and click Submit.

Trademark information
NetApp, the NetApp logo, Network Appliance, the Network Appliance logo, Akorri, ApplianceWatch, ASUP, AutoSupport,
BalancePoint, BalancePoint Predictor, Bycast, Campaign Express, ComplianceClock, Cryptainer, CryptoShred, Data ONTAP,
DataFabric, DataFort, Decru, Decru DataFort, DenseStak, Engenio, Engenio logo, E-Stack, FAServer, FastStak, FilerView,
FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol, FPolicy, GetSuccessful, gFiler, Go further, faster,
Imagine Virtually Anything, Lifetime Key Management, LockVault, Manage ONTAP, MetroCluster, MultiStore, NearStore,
NetCache, NOW (NetApp on the Web), Onaro, OnCommand, ONTAPI, OpenKey, PerformanceStak, RAID-DP, ReplicatorX,
SANscreen, SANshare, SANtricity, SecureAdmin, SecureShare, Select, Service Builder, Shadow Tape, Simplicity, Simulate
16

Upgrading a FAS2040 system with internal storage in an HA pair to a FAS32xx system in an HA pair

ONTAP, SnapCopy, SnapDirector, SnapDrive, SnapFilter, SnapLock, SnapManager, SnapMigrator, SnapMirror, SnapMover,
SnapProtect, SnapRestore, Snapshot, SnapSuite, SnapValidator, SnapVault, StorageGRID, StoreVault, the StoreVault logo,
SyncMirror, Tech OnTap, The evolution of storage, Topio, vFiler, VFM, Virtual File Manager, VPolicy, WAFL, Web Filer, and
XBB are trademarks or registered trademarks of NetApp, Inc. in the United States, other countries, or both.
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in
the United States, other countries, or both. A complete and current list of other IBM trademarks is available on the web at
www.ibm.com/legal/copytrade.shtml.
Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the United States and/or other countries.
Microsoft is a registered trademark and Windows Media is a trademark of Microsoft Corporation in the United States and/or
other countries. RealAudio, RealNetworks, RealPlayer, RealSystem, RealText, and RealVideo are registered trademarks and
RealMedia, RealProxy, and SureStream are trademarks of RealNetworks, Inc. in the United States and/or other countries.
All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such.
NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.
NetApp, Inc. NetCache is certified RealSystem compatible.

17