You are on page 1of 10

Upgrading a FAS2000-series system to an Active/Active Configuration

Installing a second controller module and upgrading the FAS2000-series system to an active/active configuration is a multistep process. Review the following sections before undertaking the procedure.

Preparing for the upgrade


To prepare for the upgrade to an active/active configuration, make sure your system meets the following requirements and that you gather the required information:

Use the disk show -n command on the existing controller to ensure that your system has at least three unowned disks for the new controller module. Two are required for file system installation and the third is a spare. These three are in addition to a spare disk for the existing controller module. If you are adding disks or disk shelves to your system, see the Storage Management Guide on the NOWtm site.
Note You must set the auto_assign option to off on the existing controller module before adding any new disks. See the Storage Management Guide on the NOW site.

Ensure that you have new license codes for both the existing controller module and the new controller module. These licenses come with the upgrade kit. Have network cables and storage cables ready. Have a serial port console available for the controller modules. Have at least one hour to zero the disks during the upgrade procedure. Ensure that the existing controller module has the correct boot files and software distribution files in the /etc directory:

/etc/boot/netapp-x86 or /etc/software/PC_ELFdist.zip /etc/software/setup.exe

See the Site Requirements Guide on the NOW site and gather all IP and other network parameters for the new controller module.

Upgrading a FAS2000-series system to an Active/Active Configuration 215-03093_A0 Copyright 2007 Network Appliance, Inc. All rights reserved.

Conventions in these procedures


These procedures make the following assumptions about your system:

The controller module in the bottom slot of the FAS2000-series system is already installed and configured and is running Data ONTAP. This controller module is referred to as the bottom controller module and has the console prompt bot>. The new controller module is being installed in the top slot of the FAS2000-series system. This controller module does not have Data ONTAP installed. This controller module is referred to as the top controller module and has the console prompt top>. Each controller module is connected to the network through its e0a port.

Installing the second controller module


Step 1: Prepare the bottom controller module to act as a netboot server on page 3 Step 2: Physically install the new controller module on page 4 Step 3: Assign an IP address, netboot, and install Data ONTAP on the new controller module on page 4 Step 4: Set up Data ONTAP on the top controller module on page 5 Step 5: Install the file system on the top controller module and add licenses to both controller modules on page 6 Step 6: Run setup on the bottom controller module to add the partner IP address on page 6 Step 7: Reboot both controller modules and enable failover on page 7 Step 8: Clone the configuration from the bottom to the top controller module on page 7 Step 9: Verify the configuration with the Configuration Checker on page 8 Step 10: Clean up files on the bottom controller module on page 9

Conventions in these procedures

Step 1: Prepare the bottom controller module to act as a netboot server


Complete the following steps on the existing (bottom) controller module:
1. Copy the boot image files from the controller modules /etc/boot directory to the /etc/http directory.

These files include the following:


/etc/boot/netapp-x86 or /etc/software/PC_ELFdist.zip /etc/software/setup.exe

The files in /etc/http are used in a later step to netboot the new controller module and install the software. Use the following commands:
Note If the existing (bottom) controller module is bot, then the command prompt switches between the bot> and jsh> prompts.
bot> java netapp.cmds.jsh jsh> cp /etc/boot/netapp-x86 /etc/http/x86 jsh> cp /etc/software/PC_ELFdist.zip /etc/http/dist

If the directory does not contain the PC_ELFdist.zip file, copy the setup.exe file:
jsh> cp /etc/software/setup.exe /etc/http/dist

If you want to view the files that were copied in the /etc/http directory:
jsh> cd /etc/http jsh> ls

2. Exit the java shell to return to the bot> prompt:


jsh> exit bot>

3. Determine the IP address of the bottom controller module (referred to in this procedure as existing_controller_ip_address). In the following example, the IP address is in bold in the command output:
bot> ifconfig -a e0a: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 inet 172.22.133.8 netmask 0xffffe000 broadcast 172.22.159.255 partner inet 172.22.130.194 (not in use) ether 00:a0:98:09:08:8c (auto-100tx-fd-up) flowcontrol full bot>

In this case, the existing_controller_ip_address is 172.22.133.8.


4. Proceed to Step 2: Physically install the new controller module on page 4.

Upgrading a FAS2000-series system to an Active/Active Configuration

Step 2: Physically install the new controller module


Insert (hot plug) the new controller module in the top slot. Gently push the controller module all the way into the chassis. See the FAS2020 or FAS2050 Hardware Overview for an illustration. After the controller module is completely seated in the chassis, it boots to the loader prompt (LOADER>) automatically. The new controller module does not have the Data ONTAP operating system installed. If there is no LOADER> prompt, record the error message and contact NetApp technical support. Proceed to Step 3: Assign an IP address, netboot, and install Data ONTAP on the new controller module on page 4.

Step 3: Assign an IP address, netboot, and install Data ONTAP on the new controller module
Complete the following steps on the newly installed (top) controller module:
1. Enter the following commands at the LOADER> prompt to configure the IP address of the new controller module:

If DHCP is available:
LOADER> ifconfig e0a -auto

If DHCP is not available:


LOADER> ifconfig e0a -addr=<new_controller_ip_address> LOADER> ifconfig e0a -mask=255.255.xxx.xxx LOADER> ifconfig e0a -gw= xxx.xxx.xxx.xxx LOADER> ifconfig e0a -dns= xxx.xxx.xxx.xxx LOADER> ifconfig e0a -domain=yourCompanyname.com

You enter the <new_controller_ip_address> again in later steps.


2. Netboot the new controller module, using the IP address determined in Step 3 of section Step 1: Prepare the bottom controller module to act as a netboot server on page 3:
LOADER> netboot http://<existing_controller_ip_address>/na_admin/x86 Loading

After loading is complete and the following text is displayed, press CTRL-C:
Starting program at 0x00200000 cpuid 0x80000000: 0x80000004 0x0 0x0 0x0 Press CTRL-C for special boot menu

The boot menu is displayed, from which you can install Data ONTAP:
(1) Normal boot. (2) Boot without /etc/rc. (3) Change password. (4) Assign ownership and initialize disks for root volume. (4a) Same as option 4, but create a flexible root volume. (5) Maintenance mode boot.

Installing the second controller module

3. Select option 4 or 4a from the boot menu to zero disks and install Data ONTAP:
Selection (1-5)?4 Zero disks and install a new file system? yes This will erase all the data on the disks, are you sure? yes

Note Zeroing disks takes about 45 minutes.

The system automatically assigns two disks to the new controller module. See the Storage Management Guide for information about managing disks and assigning additional disks.
4. Proceed to Step 4: Set up Data ONTAP on the top controller module on page 5.

Step 4: Set up Data ONTAP on the top controller module


After you are done with disk zeroing in the sectionStep 3: Assign an IP address, netboot, and install Data ONTAP on the new controller module on page 4, the setup process prompts for configuration information for the new controller module.
1. Proceed through the prompts and enter the appropriate information for your site:
Please enter the new hostname []:top Do you want to configure virtual network interfaces? [n]:[Respond appropriately for your site] Please enter the IP address for Network Interface e0a [ip_addr]:<new_controller_ip_address> Please enter the netmask for Network Interface e0a [255.255.224.0]: [Respond appropriately for your site] Should interface e0a take over a partner IP address during failover? [n]:y Please enter the IP address or interface name to be taken over by e0a []:<existing_controller_ip_address>

: : When the setup procedure finishes the Data ONTAP prompt should appear, showing the name assigned to the controller module (in our example, top).
2. Press the Enter key a few times to verify that Data ONTAP responds and is operating. 3. Proceed to Step 5: Install the file system on the top controller module and add licenses to both controller modules on page 6.

Upgrading a FAS2000-series system to an Active/Active Configuration

Step 5: Install the file system on the top controller module and add licenses to both controller modules
Note You must enable the licenses for the same Data ONTAP services on both nodes in a cluster, or takeover does not function properly. 1. Install the new controller modules operating system and download it into the controller modules CompactFlash (CF) card:
top> software update http://<existing_controller_ip_address>/na_admin/dist -r

The software command has the following options: -r disable auto reboot after finishing installation -f overwrite destination files -d disable auto download of software into CF
2. Add licenses for the top controller module:
top> license add XXXXXXX

Repeat this step for each required license.


3. Switch to the console for the existing (bottom) controller module and add the cluster license for this controller module. This license was not required previously because the controller module was not in an active/active configuration.
bot> license add XXXXXXX

Repeat this step for all other required licenses. Proceed to Step 6: Run setup on the bottom controller module to add the partner IP address on page 6.

Step 6: Run setup on the bottom controller module to add the partner IP address
1. Run setup on the existing (bottom) controller module to add the new_controller_ip_address to the existing controller module. The newly added controller module acts as partner.
bot> setup Are you sure you want to continue? [yes] y

2. Proceed through the setup prompts, shown in Step 4: Set up Data ONTAP on the top controller module on page 5. Make no other change except to enter the new_controller_ip_address at the following prompts:
Should interface e0a take over a partner IP address during failover? [y]:y Please enter the IP address or interface name to be taken over by e0a []:<new_controller_ip_address>

3. Proceed to Step 7: Reboot both controller modules and enable failover on page 7.

Installing the second controller module

Step 7: Reboot both controller modules and enable failover


1. Reboot both controller modules to enable the new licenses: a. Enter the following command:
bot> halt

The system reboots and the LOADER> prompt comes up.


b. Enter the following command:
LOADER> boot_ontap

c. Repeat substep a and substep b on the top controller module. 2. After the controller modules have finished rebooting, enable controller failover by entering the following command at either controller modules prompt:
top> cf enable

3. Proceed to Step 8: Clone the configuration from the bottom to the top controller module on page 7.

Step 8: Clone the configuration from the bottom to the top controller module
1. Clone the existing (bottom) controller modules configuration data to the top controller module by entering the following command:
top> config clone <existing_controller_IP_address> root

2. Reboot the top controller module so that the cloned options take effect:
top> reboot

3. Copy the image from the CompactFlash to a backup location:


top> download

4. Proceed to Step 9: Verify the configuration with the Configuration Checker on page 8.

Upgrading a FAS2000-series system to an Active/Active Configuration

Step 9: Verify the configuration with the Configuration Checker


Use the Configuration Checker tool to verify that the controller modules are properly configured for failover. The tool checks licenses, network configurations, options, and so on, and provides output showing when error conditions occur.
1. Go to the Configuration Checker page on the NOW site:

http://now.netapp.com/NOW/download/tools/cf_config_check/
2. Review the instructions on the pages and download the Configuration Checker tar utility. 3. Review the readme file for specific directions about running the Configuration Checker. 4. Enter the following commands at the top> and bot> prompts to gather the IP addresses of the top and bottom controller modules:
top> ifconfig -a bot> ifconfig -a

5. Enter the following command to run the Configuration Checker:


C:\data\cfigCheck> cf-config-check -l <existing_controller_ip_address> <new_controller_ip_address>

The two controller modules prompt for login name and password. See the example following Step 6.
6. Proceed to Step 10: Clean up files on the bottom controller module on page 9.

Example of the Configuration Checker run from the DOS prompt


C:\data\cfigCheck> cf-config-check -l 172.22.133.8 172.22.130.175 172.22.131.49 rsh login: root Password: 172.22.133.8 rsh login: root Password: == NetApp Cluster Configuration Checker v1.4.4 == Checking rsh logins ... OK Checking OS versions... OK Checking licenses... OK Checking cluster identity... OK Checking cf status... OK Checking fcp cfmode settings... fcp: FCP is not licensed.
8 Installing the second controller module

N/A Checking options... OK Checking Network Configuration... Checking network config in /etc/rc OK No Cluster Issues Found Done. C:\data\cfigCheck>

Step 10: Clean up files on the bottom controller module


1. Enter the following commands on the existing (bottom) controller module to delete the files used for netboot:
bot> java netapp.cmds.jsh jsh> rm /etc/http/x86 jsh> rm /etc/http/dist

2. Confirm that the files are deleted and return to the Data ONTAP prompt by entering these commands:
jsh> cd /etc/http/ jsh> ls jsh> exit bot>

Upgrading a FAS2000-series system to an Active/Active Configuration

10

Installing the second controller module