Considerations for upgrading controller hardware

To plan for the upgrade, you should familiarize yourself with the general upgrade considerations. If necessary, contact technical support for recommendations and guidance specific to the configuration of your cluster.

Requirements and limitations

• The procedure for upgrading by moving storage is disruptive. The procedure for upgrading by moving volumes is nondisruptive.
• The new nodes must support the same software version as the original nodes.

  ONTAP 9 Upgrade and Revert/Downgrade Guide

  Find the Upgrade and Revert/Downgrade Guide for your version of Data ONTAP 8

• You must observe the maximum cluster size.

  When you upgrade by moving volumes, new nodes are joined to the cluster before the original nodes are removed. Ensure the number of controllers in the cluster does not exceed the supported maximum cluster size during the procedure.

  NetApp Hardware Universe

• When combining different controller platform model in a cluster, you must follow storage platform mixing rules.

  NetApp Hardware Universe

• The new nodes must have enough storage to accommodate storage associated with the original nodes.

  ONTAP 9 Disks and Aggregates Power Guide

  Find a Storage Management Guide for your version of Data ONTAP 8

• The root aggregate size and the number of disks supported by the new system must be equal to or greater than those supported by the original system.

  For root aggregate size requirements, see the NetApp Hardware Universe

• The controllers in a HA pair must be two AFF models or two FAS models.
• You can upgrade by moving volumes or physical storage from one FAS2xxx to a later FAS2xxx if the nodes are in the same cluster. For example, you can move volumes or physical storage from a FAS2552 to a FAS2750.
• If you are upgrading a two-node MetroCluster configuration, see: Choosing a MetroCluster upgrade or refresh method

• If your system is not listed above, see the NetApp Hardware Universe to check if it has internal drives.
• If you have a system with internal storage, the recommended upgrade method is upgrading by moving volumes.
• If you have a system with internal storage, you can convert the system to a drive shelf and attach it to a new node in the same cluster. FAS2220 and FAS2520 controllers cannot be converted to a drive shelf.

  Converting a FAS2240 or FAS255x system to a drive shelf is an optional task in the workflow for upgrading by moving storage.

• If you have a system with internal storage or a system with volumes or aggregates on internal SATA drives or SSDs, you can upgrade by transferring the internal storage to a drive shelf that is attached to the new node in the same cluster.

  Transferring the internal storage is an optional task in the workflow for upgrading by moving storage.

Situations where additional steps might be needed

• If the new system has fewer slots than the original system, or if it has fewer or different types of ports, you might need to add an adapter to the new system.

  NetApp Hardware Universe

• If the original nodes or new nodes use FlexArray Virtualization software.

  NetApp KB Article: What are the specific steps involved in FlexArray for NetApp controller upgrades and replacements

• If your cluster has SAN hosts you might need to take steps to resolve issues with LUN serial number changes.

  NetApp Knowledgebase Answer 1032849: How to resolve issues during storage controller motherboard replacement and head upgrades with iSCSI and FCP

• If your system uses out-of-band ACP, you might need to migrate from out-of-band ACP to in-band ACP.

  NetApp KB Article 1029778: In-Band ACP Setup and Support