Skip to main content

Overview

Contributors netapp-pcarriga netapp-martyh netapp-aoife netapp-aherbin
PDFs

This procedure describes how to upgrade the controller hardware using aggregate relocation (ARL) for the following system configurations:

Method ONTAP version Supported systems

Manual upgrade using ARL

9.8 or later

  • FAS system to FAS system

  • FAS system to a system with FlexArray Virtualization Software or a V-Series system

  • AFF system to AFF system

  • System with FlexArray Virtualization Software or a V-Series system to a FAS system, provided that the system with FlexArray Virtualization Software or V-Series system has no array LUNs.

  • V-Series system to a system with FlexArray Virtualization Software or a V-Series system

During the procedure, you upgrade the original controller hardware with the replacement controller hardware, relocating the ownership of non-root aggregates. You migrate aggregates multiple times from node to node to confirm that at least one node is serving data from the aggregates throughout the upgrade procedure. You also migrate data logical interfaces (LIFs) and assign the network ports on the new controller to the interface groups as you proceed.

Note In this document, the original nodes are called node1 and node2, and the new nodes are called node3 and node4. During the described procedure, node1 is replaced by node3, and node2 is replaced by node4.
The terms node1, node2, node3, and node4 are used only to distinguish between the original and new nodes. When following the procedure, you must substitute the real names of your original and new nodes. However, in reality, the names of the nodes do not change: node3 has the name node1, and node4 has the name node2 after the controller hardware is upgraded.
This document uses the term systems with FlexArray Virtualization Software to refer to systems that belong to these new platforms. It uses the term V-Series system to refer to the separate hardware systems that can attach to storage arrays
Important information:

  • This procedure is complex and assumes that you have advanced ONTAP administration skills. You also must read and understand the Guidelines for upgrading controllers with ARL and the ARL upgrade workflow sections before beginning the upgrade.

  • This procedure assumes that the replacement controller hardware is new and has not been used. The steps required to prepare used controllers with the wipeconfig command are not included in this procedure. You must contact technical support if the replacement controller hardware was previously used, especially if the controllers were running Data ONTAP in 7-Mode.

  • You can use this procedure to upgrade the controller hardware in clusters with more than two nodes; however, you need to perform the procedure separately for each high-availability (HA) pair in the cluster.

  • This procedure applies to FAS systems, V-Series systems, AFF systems, and systems with FlexArray Virtualization Software. FAS systems released after ONTAP 9 can attach to storage arrays if the required license is installed. The existing V-Series systems are supported in ONTAP 9. For information about the storage array and V-Series models, refer to References to link to the Hardware Universe and see the V-Series Support Matrix.

  • In addition to non-MetroCluster configurations, this procedure applies to Fabric MetroCluster four-node and eight-node configurations running ONTAP 9.8 and later.

    • For MetroCluster configurations running ONTAP 9.7 and earlier, go to References to link to Using Aggregate Relocation to Manually Upgrade Controller Hardware Running ONTAP 9.7 or Earlier.

    • For MetroCluster IP configurations and additional upgrade options for Fabric MetroCluster
      configurations, go to References to link to the MetroCluster Upgrade and Expansion content.