Skip to main content

Complete the preparation for upgrade

Contributors netapp-pcarriga
PDFs

Learn about ONTAP licensing and managing Storage Encryption using the Onboard Key Manager (OKM). Optionally, quiesce the SnapMirror relationships.

Learn about ONTAP licensing

Some features require licenses, which are issued as packages that include one or more features. Each node in the cluster must have its own key for each feature to be used in the cluster.

If you do not have new license keys, currently licensed features in the cluster are available to the new controller. However, using unlicensed features on the controller might put you out of compliance with your license agreement, so you should install the new license key or keys for the new controller after the upgrade is complete.

Refer to References to link to the NetApp Support Site where you can obtain new 28-character license keys for ONTAP. The keys are available in the My Support section under Software licenses. If the site does not have the license keys you need, you can contact your NetApp sales representative.

For detailed information about ONTAP licensing, refer to References to link to the System Administration Reference.

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.

Steps

  1. 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.

  2. Verify the passphrase and the key-manager operation:

    security key-manager onboard sync

    When prompted, enter the cluster-wide OKM passphrase that you recorded in the previous step.

  3. Verify that cc-mode is enabled by reviewing the output of the following command:

    security key-manager config show

  4. 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.

Steps

  1. Verify the SnapMirror relationship status on the destination cluster:

    snapmirror show

    Note

    If the status is "Transferring", you must abort those transfers:
    snapmirror abort -destination-vserver vserver_name

    The abort fails if the SnapMirror relationship is not in the "Transferring" state.

  2. Quiesce all relationships between the cluster:

    snapmirror quiesce -destination-vserver *

What's next?

After preparing for upgrade, relocate non-root aggregates and NAS data LIFs owned by node1 to node2.