Reviewing cluster upgrade/downgrade requirements
Before updating the ONTAP software, you must verify that your cluster meets the general requirements. Some configurations and features also have requirements that you should understand.
- Cluster update requirements
There are release and configuration requirements that your cluster should meet before you perform an update. Additionally, there are mixed version requirements that you should be aware of while you are performing the update. - Guidelines for estimating the duration of the upgrade process
You should plan for at least 30 minutes to complete preparatory steps, 60 minutes to upgrade each HA pair, and at least 30 minutes to complete post-upgrade steps. - Upgrade considerations for SVM routing
The routing table for an SVM determines the network path the SVM uses to communicate with a destination. It’s important to understand how routing tables work so that you can prevent network problems before they occur. - Upgrade considerations for root-data partitioning and root-data-data partitioning
Root-data partitioning and root-data-data-partitioning is supported for some platform models and configurations. This partitioning capability is enabled during system initialization; it cannot be applied to existing aggregates. - Upgrade requirements for SnapMirror
You must perform certain tasks to successfully upgrade a cluster that is running SnapMirror. - Upgrade requirements for MetroCluster configurations
If you have to upgrade a MetroCluster configuration, you should be aware of some important requirements. - Upgrade considerations for SnapLock
SnapLock does not allow the download of certain kernel versions if these are qualified as bad SnapLock releases or if SnapLock is disabled in those releases. These download restrictions only apply if the node has SnapLock data.
Give documentation feedback