32xx62xx80xx System

For all operating environments

Adding a second chassis to an existing HA pair

You can upgrade a system with two controller modules in a single chassis to a two-chassis system by moving a controller
module out of the original chassis and adding Input/Output expansion modules (IOXMs) in each chassis. This process is a
multistep process involving both hardware and software changes that must be performed in the proper order.
Before you begin

An existing chassis with two controller modules must be installed, configured, and running Data ONTAP.
This chassis is referred to as the existing chassis.
The chassis that is being added is referred to as the new chassis.

The new chassis must be received from NetApp as part of the upgrade kit.

You must have rack space and cables for the new chassis and components.

About this task

This procedure is disruptive.

If you are converting a FAS8060 in a dual-controller configuration (two controller modules in the same chassis), both nodes
must be running at least Data ONTAP 8.2.3 or a version of Data ONTAP later than Data ONTAP 8.3.0 before you shut
down the system.

This procedure applies if you are moving a controller module from a preexisting system or a system that was previously in
an HA pair to a new chassis to create a new, two-chassis HA pair.

Each controller module must be connected to the network through its e0a port.

Steps

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

Required Data ONTAP upgrades for the FAS8060 storage system on page 1
Installing the new chassis on page 3
Moving the controller module from the old chassis to the new chassis on page 3
Adding I/O expansion modules to the chassis on page 5
Cabling the system on page 6
Booting the system on page 7
Verifying cabling on page 8

Required Data ONTAP upgrades for the FAS8060 storage system

Before you add a second chassis to a FAS8060 system, you must upgrade both controllers to run Data ONTAP 8.2.3 or later, or
to a version of Data ONTAP later than Data ONTAP 8.3.0. Both controllers must run the same version of Data ONTAP before
you shut down the nodes and install the new chassis.

215-06156_B0

January 2015

Copyright 2015 NetApp, Inc. All rights reserved.

Web: www.netapp.com Feedback: doccomments@netapp.com

Planning your upgrade with Upgrade Advisor

You should use the Upgrade Advisor tool (if it is available in your environment) to ensure that you have met the requirements
for upgrading to the current release and to generate an upgrade plan.
Before you begin

To use the Upgrade Advisor tool, your cluster must meet the following requirements:

It must have a valid support contract.

It must be enabled to send AutoSupport messages to NetApp.

Attention: If your cluster does not meet these requirements, you should consult the Release Notes and Upgrade Guide for this

Data ONTAP release to prepare a detailed upgrade plan.

About this task

Upgrade Advisor is an online tool, available on the NetApp Support Site, that simplifies the process of planning Data ONTAP
upgrades. When you submit your system identification and target release to Upgrade Advisor, the tool compares AutoSupport
data about your cluster to known requirements and limitations of the target release. Upgrade Advisor then generates an upgrade
plan (and optionally a back-out plan) with recommended preparation and execution procedures.
To generate an upgrade plan, you must have identifying information for your cluster (host name, system ID, or serial number)
and you must have selected a target upgrade release. You can also select other options, including the following:

Create a plan for a cluster.

Create a back-out plan.

Compare upgrade scenarios.

For more information about Upgrade Advisor, see the Upgrade Advisor Help screens.
Steps

1. Locate and record the system host name, system ID, or serial number of your cluster:
system node run -node nodename sysconfig

The system identification information is near the top of the display.

2. From a web browser, log in to the My AutoSupport home page on the NetApp Support Site.

NetApp AutoSupport
3. Click the Launch My AutoSupport link.
4. Enter the host name, system ID, or serial number of your cluster when prompted.
5. Select the cluster that you want to upgrade from those listed.
6. Select the latest AutoSupport record from the ASUPs row.
7. Click the Upgrade Advisor tab.
8. Select the Data ONTAP release to which you want to upgrade from the Upgrade To menu.
9. Select the upgrade method and the level of detail you want included in your upgrade plan.
10. Click Generate to generate your upgrade plan.

Adding a second chassis to an existing HA pair

Installing the new chassis

When you install a new chassis in the equipment rack or system cabinet, you must perform a specific sequence of steps.
About this task

You must consider the cable length between your components when you select the location of the new chassis in your
environment.

If your system requires copper HA interconnect cables, the two chassis must be close enough to each other for the
interconnect cable to connect the ports on the two controller modules.

NetApp Hardware Universe

If your system has DS2246 or DS4243 disk shelves and no copper HA interconnect cables, the two chassis must be close
enough to each other so that the SAS cables can connect from the disk shelves to the moved controller module in the new
chassis.

Steps

1. If you are not already grounded, properly ground yourself.

2. Install additional angel wings or rails in your equipment rack or system cabinet as needed, using the instructions included
with the applicable kits.
3. Using two or three people, install the empty chassis into the equipment rack or system cabinet by guiding the chassis onto
the rail guides in a system cabinet or the angel wings in an equipment rack.
4. Slide the chassis all the way into the equipment rack or system cabinet.
5. Secure the rear of the chassis to the support rail, if applicable.
6. Secure the front of the chassis to the equipment rack or system cabinet upright, using the screws in the new chassis kit.
7. If necessary, install the fan modules into the new chassis.
8. Install the bezel by aligning it with the ball studs on the front of the chassis and gently push the bezel onto the ball studs.

Moving the controller module from the old chassis to the new chassis
You must move the bottom controller module from the old chassis to the new chassis.
About this task

This procedure is disruptive.

Steps

1. Check the status of the target node by entering the appropriate command at the system console of either node:
If your system is configured in...

Then issue this command...

7-Mode

cf status

clustered Data ONTAP

storage failover show

2. Take one of the following actions, depending on the result of the cf status or the storage failover show command:

Installing the new chassis

If...

Then...

Neither node is in takeover mode

Complete the following substeps:

A node is in takeover mode

a.

Disable the HA configuration by entering the cf disable command (if in a 7-Mode

system) or storage failover modify false command (if in a Cluster-Mode
system) on either console.

b.

Shut down both nodes by entering the halt command (if in a 7-Mode system) or halt
local (if in a Cluster-Mode system) on each node's console.

Complete the following substeps:

a.

Reenable HA by entering the cf giveback command (if in a 7-Mode system) or

storage failover giveback -fromnode nodename command (if in a
Cluster-Mode system) from the target node console.

b.

Disable the HA configuration by entering the cf disable command (if in a 7-Mode

system) or storage failover modify false command (if in a Cluster-Mode
system) on either console.

c.

Shut down both nodes by entering the halt command (if in a 7-Mode system) or halt
local (if in a Cluster-Mode system) on each node's console.

3. Turn off both power supplies and disconnect them from the power source.
4. Loosen the hook and loop strap binding the cables to the cable management armcable management traycable management
device, and then unplug the system cables and SFPs (if needed) from the controller module, and keep track of where the
cables were connected.
Leave the cables in the cable management armcable management tray so that when you reinstall the cable management
armcable management tray, the cables are organized.
Leave the cables in the cable management device so that when you reinstall the cable management device, the cables are
organized.
5. Loosen the hook and loop straps binding the cables to the bottom cable management arm or device. and then unplug the
system cables from the bottom controller module as needed and keep track of where the cables were connected.
Leave the cables in the cable management arm or device so that when you reinstall the cable management arms or device,
that cables are organized.
6. Remove the cable management arms or tray from the bottom controller module.
If your system is a...

Then...

32xx

Remove the cable management arms for the left and right sides of the controller module and
set them aside.

6210 or 6220

Grasp the cable management tray by the side, gently push one side of the tray so that the arm
slides across and off the retaining pin, slide the other arm off the retaining pin on the other
side of the controller module, and then lift it off the back of the controller module and set it
aside.

FAS8060

Remove the cable management device from the controller module and set it aside.

7. Loosen the thumbscrew on the cam handle, pull the cam handle downward, and then slide the controller module out of the
chassis.

If your system is a...

Then...

32xx

Slide the controller module out of the chassis, supporting it with your free hand.

Adding a second chassis to an existing HA pair

If your system is a...

Then...

6210, 6220 or FAS8060

Slide the controller module out of the chassis until it catches, and then push in the release latch
on the left side of the controller module and slide the controller module out of the system.
Note: Make sure that you support the bottom of the controller module with your free hand.

8. Install the controller module in the top slot of the new chassis:
a. Align the end of the controller module with the opening in the chassis, and then gently push the controller module into
the system until it meets the midplane and is fully seated.
b. Close the cam handle to the locked position, and then tighten the thumbscrew.
9. Your next step depends on your system configuration.
If your system is a...

Then...

3210, 3220, 6210, or 6220

Install the blank panel in the bottom controller module opening of each chassis and go to
Cabling the system on page 6 in this procedure.

3240, 3270 or FAS8060

Go to Adding I/O expansion modules to the chassis on page 5.

Adding I/O expansion modules to the chassis

To install the I/O expansion modules (IOXMs) into the chassis, you must perform a specific sequence of steps.
Before you begin

You must use the IOXMs that you ordered as part of the upgrade process. These modules already have the PCIe cards that
support your configuration installed in them.
You must have installed any additional PCIe cards in the IOXMs, as space allows, before you install the IOXMs into the
chassis.

NetApp Hardware Universe

Note: The 3210 and 6210 systems do not support IOXMs. If you are adding a second chassis to a 3210 or 6210 system, skip
this procedure.
Steps

1. If you are not already grounded, properly ground yourself.

2. Install any additional PCIe cards into your new IOXMs.
These are cards you might have in addition to what you ordered for your system.
3. Align the IOXM with the bottom bay opening of the target chassis (labeled B on the bay), and use the cam handle to gently
slide the IOXM all the way into the chassis.
The IOXM cam handle begins to engage before the IOXM is fully seated into the chassis. The cam handle enables you to
fully seat the IOXM.
4. Push the cam handle all the way to the closed position, and then tighten the thumbscrew on the cam handle.
5. Install the cable management arm or tray by completing the substeps for your platform:

Adding I/O expansion modules to the chassis

If your system is a...

32xx

62xx

FAS8060

Then...
a.

Align the cable management arm with the slot on the IOXM.
Make sure that the release button on the cable management arm faces to the outside of the
IOXM.

b.

Push the cable management arm into the slot on the IOXM until it clicks in place.

a.

Align the cable management tray uprights with the IOXM, tilting the cable management
tray uprights toward the IOXM.

b.

Gently pinch the cable management tray uprights inward, aligning the holes in the end of
the arms with the posts in the upper corners of the IOXM.

c.

Slide the cable management arm uprights onto the posts on the IOXM, and then swing the
bottom of the cable management tray to rest on the bottom of the IOXM.

a.

Align the cable management device uprights with the IOXM.

b.

Gently push the cable management device into the brackets on the edges of the IOXM
until it clicks into place.

6. Repeat these steps for the remaining IOXM.

Cabling the system

To cable the controller module and I/O expansion modules, you must follow the cabling rules for systems with SAS-based disk
shelves.
Before you begin

You must have read the following documentation:

Universal SAS and ACP Cabling Guide for SAS and ACP cabling rules

Data ONTAP High-Availability Configuration Guide for installation and management for high availability configurations

Installation and Setup Instructions for your system

Steps

1. If you have not already done so, reinstall the cable management arms or cable management tray/device in the controller
module you moved.
2. Reconnect the cables to the moved controller module and then secure them to the cable management device with the hook
and loop straps on the cable management device
3. Cable the HA interconnect and then cable the disk shelves, as necessary.

Installation and Setup Instructions 32xx Systems

Installation and Setup Instructions 62xx Systems
Installation and Setup Instructions FAS8040/FAS8060 Systems
Find the Active/Active Configuration Guide for your version of Data ONTAP 7G
Find the High-Availability Configuration Guide for your version of Data ONTAP 8

Adding a second chassis to an existing HA pair

Booting the system

You must reboot both controller modules, check their HA state and modify it if needed, and modify the boot time variable prior
to the final system boot.
Steps

1. Turn on the power to one system.

2. Stop the reboot process in the existing chassis by pressing Ctrl-C when prompted by the system.
3. Select the menu option to enter Maintenance mode.
4. Check the state of both controller modules by entering the following command from the prompt on each console:
ha-config show

This command displays the HA state of all system components. The HA state should be the same for both the controllers and
the chassis; it should be either ha or mcc.
If the controller module status...

Then...

Displays ha or mcc for both the

controller module and chassis

Go to the next step.

Does not display ha or mcc for the

controller module

Correct the status for the controller module by completing the following substeps:
a.

Enter the following command at the prompt:

ha-config modify controller ha-state

Does not display ha or mcc for the

chassis

b.

Check the status of the chassis and modify it as needed.

c.

Go to the next step.

Correct the status for the chassis by completing the following substeps:
a.

Enter the following command at the prompt:

ha-config modify chassis ha-state

b.

Go to the next step.

5. Turn on the power to the second system and repeat Steps 2 on page 7 through 4 on page 7 for the other chassis and controller
module.
6. Go to the boot environment prompt (LOADER prompt) by entering the following command on each node's console:
halt

7. Check the boot time environment variable by completing the following substeps on both nodes:
a. Enter the following command at the boot environment prompt:
printenv psm-cc-config?
If the variable is set to...

Description

empty

Go to the next step.

Booting the system

If the variable is set to...

Description

true

Reset the psm-cc-config? variable by completing the following substeps:

a.

Enter the following command on the console:

unset psm-cc-config?

b.

Go to the next step.

8. Boot the system by entering the following command:

boot_ontap

The system boots normally.

9. Enable the HA configuration:
If your system is running Data
ONTAP in...

Then...

7-Mode

Enter the following command on either node's console:

cf enable

clustered Data ONTAP

Enter the following command on either node's console:

storage failover modify true

Verifying cabling
You use the Config Advisor tool to verify that the system is cabled correctly and that your system is configured correctly.
Before you begin

The hardware setup must be complete and all components must be powered on.
About this task

The Config Advisor tool is available at mysupport.netapp.com. Information about how to use the tool is available in the user
guide, which is available in the download package. If you need support for the Config Advisor tool, you must follow the
procedure in the tool's Reporting Issues in Config Advisor online help topic. The Config Advisor tool is not supported by the
typical NetApp support process.
Steps

1. Connect your laptop to the management network for the cluster.

2. If needed, change the IP address of your laptop to an unused address on the subnet for the management network.
3. Start Config Advisor, and then select the profile Clustered Data ONTAP.
4. Select the cluster switch model, or switchless, if appropriate.
5. Enter the requested IP addresses and credentials.
6. Click Collect Data.
The Config Advisor tool displays any problems found. If problems are found, correct them and run the tool again.
7. Click the System Config Summary tab and check the output.
If problems are found, correct them and run the tool again.

Adding a second chassis to an existing HA pair

Related information

Config Advisor from NetApp Support Site: support.netapp.com/eservice/toolchest

Copyright information
Copyright 19942015 NetApp, Inc. All rights reserved. Printed in the U.S.
No part of this document covered by copyright may be reproduced in any form or by any meansgraphic, electronic, or
mechanical, including photocopying, recording, taping, or storage in an electronic retrieval systemwithout prior written
permission of the copyright owner.
Software derived from copyrighted NetApp material is subject to the following license and disclaimer:
THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
NetApp reserves the right to change any products described herein at any time, and without notice. NetApp assumes no
responsibility or liability arising from the use of products described herein, except as expressly agreed to in writing by NetApp.
The use or purchase of this product does not convey a license under any patent rights, trademark rights, or any other intellectual
property rights of NetApp.
The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in
subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.277-7103 (October 1988)
and FAR 52-227-19 (June 1987).

Trademark information
NetApp, the NetApp logo, Go Further, Faster, ASUP, AutoSupport, Campaign Express, Cloud ONTAP, clustered Data
ONTAP, Customer Fitness, Data ONTAP, DataMotion, Fitness, Flash Accel, Flash Cache, Flash Pool, FlashRay, FlexArray,
FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexVol, FPolicy, GetSuccessful, LockVault, Manage ONTAP, Mars,
MetroCluster, MultiStore, NetApp Insight, OnCommand, ONTAP, ONTAPI, RAID DP, SANtricity, SecureShare, Simplicity,
Simulate ONTAP, Snap Creator, SnapCopy, SnapDrive, SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover,
SnapProtect, SnapRestore, Snapshot, SnapValidator, SnapVault, StorageGRID, Tech OnTap, Unbound Cloud, and WAFL are
trademarks or registered trademarks of NetApp, Inc., in the United States, and/or other countries. A current list of NetApp
trademarks is available on the web at http://www.netapp.com/us/legal/netapptmlist.aspx.
Cisco and the Cisco logo are trademarks of Cisco in the U.S. and other countries. All other brands or products are trademarks or
registered trademarks of their respective holders and should be treated as such.

Copyright information

How to send comments about documentation and receive

update notification
You can help us to improve the quality of our documentation by sending us your feedback. You can receive automatic
notification when production-level (GA/FCS) documentation is initially released or important changes are made to existing
production-level documents.
If you have suggestions for improving this document, send us your comments by email to doccomments@netapp.com. To help
us direct your comments to the correct division, include in the subject line the product name, version, and operating system.
If you want to be notified automatically when production-level documentation is released or important changes are made to
existing production-level documents, follow Twitter account @NetAppDoc.
You can also contact us in the following ways:

10

NetApp, Inc., 495 East Java Drive, Sunnyvale, CA 94089 U.S.

Telephone: +1 (408) 822-6000

Fax: +1 (408) 822-4501

Support telephone: +1 (888) 463-8277

Adding a second chassis to an existing HA pair