Complete the preparation for upgrade
Learn about ONTAP licensing and managing Storage Encryption using the Onboard Key Manager (OKM). Optionally, quiesce the SnapMirror relationships.
Learn about ONTAP licensing
For detailed information about ONTAP licensing, refer to License management.
|
|
Using unlicensed features on the controller might put you out of compliance with your license agreement. |
Manage storage encryption using the Onboard Key Manager
Use the Onboard Key Manager (OKM) to manage encryption keys. If you have the OKM set up, you must record the passphrase and backup material before beginning the upgrade.
-
Record the cluster-wide passphrase.
This is the passphrase that was entered when the OKM was configured or updated using the CLI or REST API.
-
Verify the passphrase and the key-manager operation:
security key-manager onboard syncWhen prompted, enter the cluster-wide OKM passphrase that you recorded in the previous step.
-
Verify that cc-mode is enabled by reviewing the output of the following command:
security key-manager config show -
Back up the key-manager information:
security key-manager onboard show-backup
Optionally, quiesce the SnapMirror relationships
Before continuing with the procedure, you must confirm that all the SnapMirror relationships are quiesced. When a SnapMirror relationship is quiesced, it remains quiesced across reboots and failovers.
-
Verify the SnapMirror relationship status on the destination cluster:
snapmirror showIf the status is "Transferring", you must abort those transfers:
snapmirror abort -destination-vserver vserver_nameThe abort fails if the SnapMirror relationship is not in the "Transferring" state.
-
Quiesce all relationships between the cluster:
snapmirror quiesce -destination-vserver *
After preparing for upgrade, relocate non-root aggregates and NAS data LIFs owned by node1 to node2.