Beruflich Dokumente
Kultur Dokumente
system in an HA pair
You can upgrade your FAS2040 storage system in an HA pair to a FAS32xx storage system in an HA pair by replacing the
controllers.
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 supported by each 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.
You are upgrading from a FAS2040 system without internal storage but with at least one attached disk shelf.
You are upgrading to a FAS3210, FAS3240, or FAS3270 system running Data ONTAP 7.3.5 or Data ONTAP 8.x. or later,
or you are upgrading to a FAS3220 or FAS3250 running Data ONTAP 8.1.2 or later. FAS3220 and FAS3250 systems do not
run versions of Data ONTAP earlier than 8.1.2.
Note: The FAS32xx system must have the version of Data ONTAP that you want to use installed before you upgrade the
hardware.
If you want to upgrade from Data ONTAP 7.3.5 or a 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 a later version in the 7.3.x release family on a system running Data ONTAP
8.0.1, 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.
The FAS32xx system that you are upgrading to has the same name and IP address as the FAS2040 system.
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 storage knowledge.
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-07164_A0 ur002
Steps
1.
2.
3.
4.
Grounding strap
#2 Phillips screwdriver
2. Download from the NetApp Support Site at support.netapp.com the documents that contain information helpful during the
upgrade.
Download the version of the document for the version of Data ONTAP that the system is running.
Document
Contents
Data ONTAP Software Setup Guide for 7-Mode Contains information about configuring the Service Processor (SP).
Also contains information about Storage Encryption.
Data ONTAP Storage Management Guide for 7- Contains instructions reassigning disks.
Mode
Also contains information about Storage Encryption.
32xx Installation and Setup Guide
Document
Contents
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.
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.
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 systems are 3U high. You must allow for the appropriate amount of space for the system.
2. Check the Hardware Universe (formerly the System Configuration Guide) at support.netapp.com/knowledge/docs/hardware/
NetApp/syscfg/index.shtml to ensure that the FAS32xx system supports the disk shelves and any other hardware 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: The Baseboard Management Controllers (BMCs) on your 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 for the SPs on the FAS32xx system.
5. Check the system invoice for the version of Data ONTAP installed on the FAS32xx system.
If you are upgrading to a FAS3210, FAS3240, or FAS3270 system, Data ONTAP 7.3.5 or Data ONTAP 8.x or later must be
installed on the FAS2040 system before you can upgrade the hardware. If you are upgrading to a FAS3220 or FAS3250
system, Data ONTAP 8.1.2 or later must be installed on the FAS2040 before you upgrade the hardware.
6. Take one of the following actions:
Then...
Go to Step 7.
Different from the version on the Go to the NetApp Support Site at support.netapp.com and download the version of Data ONTAP for
FAS32xx system
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 .tar, .tgz, or .zip file to a directory that is accessible to
your FAS2040 system. See the Data ONTAP Upgrade and Revert/Downgrade Guide for 7-Mode
for instructions about how to download Data ONTAP.
Then...
Uses Storage
Encryption
Go to Step 9 and complete Step 9 through Step 17, as appropriate, on both controllers of the FAS2040 system,
all the steps first on one controller, and then all the steps on the other controller.
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.
Go to Step 13 and complete Step 13 through Step 17, as appropriate, on both controllers of the FAS2040
system, all the steps first on one controller, and then all the steps on the other controller.
9. 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
0c.00.1
0x0
0c.00.0
080CF0C8000000000100000000000000A948EE8604F4598ADFFB185B5BB7FED3
0c.00.3
080CF0C8000000000100000000000000A948EE8604F4598ADFFB185B5BB7FED3
0c.00.4
080CF0C8000000000100000000000000A948EE8604F4598ADFFB185B5BB7FED3
0c.00.2
080CF0C8000000000100000000000000A948EE8604F4598ADFFB185B5BB7FED3
0c.00.5
080CF0C8000000000100000000000000A948EE8604F4598ADFFB185B5BB7FED3
Locked?
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.
10. 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:
11. Ensure that all the self-encrypting disks are associated with an MSID by entering the following command and examining the
output:
4
Then...
Go to Step 16.
FAS2040 system after the upgrade, and the root volume is a traditional root volume
Go to Step 16.
FAS2040 system after the upgrade, and the root volume is a FlexVol volume
Go to Step 14.
14. Check the size of the FlexVol root volume on the FAS2040 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 size requirement on the FAS32xx
system before you upgrade the hardware.
The following list shows the minimum FlexVol size requirement for each FAS32xx model:
FAS3210: 100 GB
FAS3220: 250 GB
FAS3240: 150 GB
FAS3250: 250 GB
FAS3270: 300 GB
15. 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
In the preceding command, n indicates the desired size of the volume and g specifies gigabytes.
For more information about resizing FlexVol volumes, see the Data ONTAP Storage Management Guide for 7-Mode.
16. Make sure that the port locations on the FAS2040 system match the port locations on the FAS32xx system.
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
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. Install the FAS32xx system and any disk shelves associated with it, as described in the FAS32xx System Installation and
Setup instructions.
2. 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...
Go to Step 3.
On either controller of your FAS2040 system, install the version of Data ONTAP that
you downloaded in Preparing for the upgrade by entering the following command:
software update url -r
url is the location of the Data ONTAP system files (.tar, .tgz, or .zip file).
Note: The -r option suppresses the automatic reboot.
Note: Complete Step 3 and Step 4 on the same controller that you completed Step 2.
3. Rename the root volume on the FAS32xx system using one of the following methods, depending on the type of root volume
on the system:
If the FAS32xx system has a... Then...
Traditional root volume
Rename the root volume to old_vol0 and the corresponding aggregates to old_aggr0 by entering
the following commands:
vol rename your_root_vol_name old_vol0
aggr rename your_aggr_name old_aggr0
Note: If you are upgrading a FAS2040 system running Data ONTAP 8.x, you can have only a FlexVol root volume unless
you previously migrated a traditional root volume from another system.
4. If you have not done so already, back up the data on your FAS2040 system, particularly the /etc/rc and /etc/hosts
files.
5. Repeat Step 2 through Step 4 on the second controller of your FAS2040 system.
6. Disable clustering by entering the following command on either controller of your FAS2040 system and on either controller
of the FAS32xx system:
cf disable
7. Shut down your FAS2040 system and the FAS32xx system by entering the following command on each of their consoles:
halt
See the Installation and Setup Instructions for the FAS32xx system and the Universal SAS and ACP Cabling Guide for
cabling information.
Note: Different systems have different numbers of ports. You might need to add a PCI card to match the required
configuration for the upgrade.
12. Turn on the disk shelves and then turn on the FAS32xx controllers, observing the startup messages on the console of each
controller.
13. When the message Press CTRL-C for special boot menu appears on the console, press CTRL-C to display the boot
menu on each controller.
Complete Step 14 through Step 25 first on one controller and then on the other controller.
14. Select option 5 at the boot menu and continue with the boot.
The Maintenance mode command prompt (*>) appears.
15. View disk ownership on the FAS32xx system by entering the following command on one of the controllers:
disk show -v
16. 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 FAS32xxsystem, 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.
17. 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.
18. Exit Maintenance mode by entering the following command at the Maintenance mode prompt:
halt
19. Boot Data ONTAP by entering the following command at the boot loader prompt:
boot_ontap
20. Take one of the following actions, depending on the FAS2040 system root volume:
If the FAS2040 system had Then...
a...
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
Bring the aggregate from the FAS2040 system online and set it to the root volume for the FAS32xx
system by entering the following commands:
aggr online aggr0
vol options vol0 root
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.
22. 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.
23. Ensure that the ports are assigned correctly by entering the setup command at the system prompt and then changing
information as necessary at the appropriate prompts.
24. 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, .tgz, 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. For details about installing Data ONTAP, see
the Data ONTAP Upgrade Guide.
25. Optional: Remove the old root volume of the FAS32xx system by entering one of the following sets of commands:
If the old root volume on the FAS32xx system was a...
Then...
Traditional volume
Then...
FlexVol volume
26. Modify the RAID groups and volumes as needed, as described in the Storage Management Guide.
27. Enable clustering by entering the following command on either controller:
cf enable
28. Verify that the HA pair is set up correctly by entering the following command on one of the controllers:
disk show -a
If the HA pair is set up correctly, the disk show -a command displays disk ownership for both controllers.
29. Configure the SPs by entering the following command on both controllers:
sp setup
Use the IP address that you obtained in Step 4 in the section Preparing the site and equipment for the upgrade.
30. After the sp setup command runs, follow the setup script, which starts automatically.
See the Data ONTAP System Administration Guide for more information.
31. Take one of the following actions:
If the FAS2040 system...
Then...
Go to Step 32.
Then...
Uses Storage
Encryption
a. Set up the key management server used by the FAS2040 system 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 theFAS32xx 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 32a and 32b on the other controller.
c. Go to the section Decommissioning the old system.
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. Install the FAS32xx system and any disk shelves associated with it, as described in the FAS32xx System Installation and
Setup instructions.
2. 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...
Go to Step 3.
On either controller of your FAS2040 system, install the version of Data ONTAP that
you downloaded in Preparing for the upgrade by entering the following command:
software update url -r
url is the location of the Data ONTAP system files (.tar, .tgz, or .zip file).
Note: The -r option suppresses the automatic reboot.
3. On the same controller of your FAS2040 system that you used to complete Step 2, rename the root volume using one of the
following methods, depending on the type of root volume on the system.
If your FAS2040 system has a... Then...
Traditional root volume
Rename the root volume to old_vol0 and the corresponding aggregates to old_aggr0 by
entering the following commands:
vol rename your_root_vol_name old_vol0
aggr rename your_aggr_name old_aggr0
Note: If you are upgrading a FAS2040 system running Data ONTAP 8.x, you can have only a FlexVol root volume unless
you previously migrated a traditional root volume from another system.
6. Shut down your FAS2040 system and the FAS32xx system by entering the following command on each of their consoles:
halt
10
9. Turn off the power to the FAS2040 system and disk shelves attached to the system, and then disconnect the cables.
10. Cable the FAS2040 disk shelves to the FAS32xx system, as described in Installation and Setup Instructions for NetApp
FAS32xx Storage Systems and the appropriate disk shelf guide.
Also follow the cabling instructions in the High-Availability Configuration Guide.
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.
Note: Different systems have different numbers of ports. You might need to add a PCI card to match the required
configuration for the upgrade.
11. Turn on the disk shelves and then turn on the FAS32xx controllers, observing the startup messages on the console of each
controller.
12. When the message Press CTRL-C for special boot menu appears on the console, press CTRL-C to display the boot
menu on each controller.
Complete Step 13 through Step 21 first on one controller and then on the other controller.
13. Select option 5 at the boot menu and continue with the boot.
The Maintenance mode command prompt (*>) appears.
14. View disk ownership on the FAS32xx system by entering the following command on one of the controllers:
disk show -v
15. Assign the disks that you migrated from the FAS2040system 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 of 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.
16. 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.
17. Exit Maintenance mode by entering the following command at the Maintenance mode prompt:
halt
18. Boot Data ONTAP by entering the following command at the boot environment prompt:
boot_ontap
19. Check the volume status by entering the following command at the system prompt:
vol status
20. 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.
21. Optional: Remove the old root volume of the FAS2040 system by entering one of the following sets of commands.:
11
Then...
Traditional volume
FlexVol volume
22. Modify RAID groups and volumes as needed, as described in the Data ONTAP Storage Management Guide for 7-Mode.
23. Update the licenses by entering the following command, once for each license, at the system prompt:
license add service/protocol_code
Example
license add ABCDEFG
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.
24. Enter the following command at the system prompt of both controllers:
halt
25. Enter the following command at the boot environment prompt of both controllers:
boot_ontap
26. Ensure that the ports are assigned correctly by entering the setup command at the system prompt and then changing
information as necessary at the appropriate prompts.
27. Enable the HA pair by entering the following command on either controller:
cf enable
28. Verify that the HA pair is set up correctly by entering the following command on one of the controllers:
disk show -a
If the HA pair is set up correctly, the disk show -a command displays disk ownership for both controllers.
29. Configure the SP by entering the following command on both controllers:
sp setup
Use the IP address that you obtained in Step 4 in the section Preparing the site and equipment for the upgrade.
30. After the sp setup command runs, follow the setup script, which starts automatically.
See the Data ONTAP System Administration Guide for 7-Mode for more information.
31. Take one of the following actions:
If the FAS2040 system...
Then...
Go to Step 32.
If the FAS32xx
system...
Then...
Uses Storage
Encryption
a. Set up the key management server used by the FAS2040 system 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 32a and 32b on the other controller.
c. Go to the section Decommissioning the old system.
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
13
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.
14