Skip to main content

Decide whether to use this aggregate relocation procedure

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

There are several aggregate relocation (ARL) methods for upgrading controller hardware. This procedure describes how to upgrade the controller hardware using ARL with "system controller replace commands" on systems running ONTAP 9.7, 9.6, or 9.5. You should only use this complex procedure if you're an experienced ONTAP administrator.

To help you decide if this ARL procedure is suitable for your controller hardware upgrade, you should review all of the following circumstances for supported upgrades:

  • You are upgrading NetApp controllers running ONTAP 9.5, 9.6 or 9.7. This document is not applicable to upgrades to ONTAP 9.8.

  • You don't want to add the new controllers as a new HA pair to the cluster and migrate the data using volume moves.

  • You are experienced in administering ONTAP and are comfortable with the risks of working in the diagnostic privilege mode.

  • Your hardware upgrade combination is listed in the supported model matrix.

  • If you are upgrading a MetroCluster configuration, it is a 4-node or higher FC configuration, and all nodes are running ONTAP 9.6 or 9.7.

Note

Supported system upgrade combinations

The following tables shows the supported model matrix for the controller upgrade using this ARL procedure.

Old controller Replacement controller

FAS8020, FAS8040, FAS8060, FAS8080

FAS8200, FAS8300, FAS8700, FAS9000

AFF8020, AFF8040, AFF8060, AFF8080

AFF A300, AFF A400, AFF A7001, AFF A8002

FAS8200

FAS8700, FAS9000, FAS83004, 5

AFF A300

AFF A7001, AFF A8002, 3, AFF A4004, 5
Note If your controller upgrade model combination is not in the above table, contact technical support.

1ARL automated upgrade for the AFF A700 system is supported from ONTAP 9.7P2.

2If you are updating to an AFF A800 or a system that supports internal and external disks, you must follow specific instructions for the root aggregate on internal NVMe disks. See Check and configure UTA/UTA2 ports on node3, Step 14 and Check and configure UTA/UTA2 ports on node4, Step 14.

3ARL automated upgrade from an AFF A300 to an AFF A800 system is supported from ONTAP 9.7P5.

4ARL automated upgrade from an AFF A300 to an AFF A400 and an FAS8200 to an FAS8300 system is supported from ONTAP 9.7P8.

5If you are upgrading from an AFF A300 to an AFF A400 or an FAS8200 to an FAS8300 system in a two-node switchless cluster configuration, you must pick temporary cluster ports for the controller upgrade. The AFF A400 and FAS8300 systems come in two configurations, as an Ethernet bundle where the mezzanine card ports are Ethernet type and as an FC bundle where the mezzanine ports are FC type.

  • For an AFF A400 or an FAS8300 with an Ethernet type configuration, you can use any of the two mezzanine ports as temporary cluster ports.

  • For an AFF A400 or an FAS8300 with an FC type configuration, you must add a four-port 10GbE network interface card (part number X1147A) to provide temporary cluster ports.

  • After you complete a controller upgrade by using temporary cluster ports, you can nondisruptively migrate cluster LIFs to e3a and e3b, 100GbE ports on an AFF A400 system, and e0c and e0d, 100GbE ports on an FAS8300 system.

Choose a different hardware upgrade procedure

Related information

Refer to References to link to the ONTAP 9 Documentation.