Skip to main content
Element Software
12.5 and 12.7

Upgrade a management node

Contributors netapp-pcarriga netapp-dbagwell

You can upgrade your management node to management node 12.5 or later from version 12.3.x or later.

Upgrading the management node operating system is no longer required to upgrade Element software on the storage cluster. You can simply upgrade the management services to the latest version to perform Element upgrades using NetApp Hybrid Cloud Control. Follow the management node upgrade procedure for your scenario if you would like to upgrade the management node operating system for other reasons, such as security remediation.

Note If you require information on upgrading management nodes 12.2 or earlier, see the Element 12.3.x management node upgrade documentation.
Upgrade options

Choose one of the following options:

Note If you do not sequentially update your management services followed by Element storage, you cannot reconfigure reauthentication using this procedure. Follow the appropriate upgrade procedure instead.

Upgrade a management node to version 12.5 or later from version 12.3.x or later

You can perform an in-place upgrade of the management node from version 12.3.x or later to version 12.5 or later without needing to provision a new management node virtual machine.

Note The Element 12.5 or later management node is an optional upgrade. It is not required for existing deployments.
What you'll need
  • The RAM of the management node VM is 24GB.

  • The management node you are intending to upgrade is version 12.0 and uses IPv4 networking. The management node version 12.5 or later does not support IPv6.

    Tip To check the version of your management node, log in to your management node and view the Element version number in the login banner.
  • You have updated your management services bundle to the latest version using NetApp Hybrid Cloud Control. You can access NetApp Hybrid Cloud Control from the following IP: https://<ManagementNodeIP>

  • If you are updating your management node to version 12.5 or later, you need management services 2.21.61 or later to proceed.

  • You have configured an additional network adapter (if required) using the instructions for configuring an additional storage NIC.

    Note Persistent volumes might require an additional network adapter if eth0 is not able to be routed to the SVIP. Configure a new network adapter on the iSCSI storage network to allow the configuration of persistent volumes.
  • Storage nodes are running Element 12.3.x or later.

  1. Log in to the management node virtual machine using SSH or console access.

  2. Download the management node ISO for Element software from the NetApp Support Site to the management node virtual machine.

    Note The name of the ISO is similar to solidfire-fdva-<Element release>-patchX-XX.X.X.XXXX.iso
  3. Check the integrity of the download by running md5sum on the downloaded file and compare the output to what is available on the NetApp Support Site for Element software, as in the following example:

    sudo md5sum -b <path to iso>/solidfire-fdva-<Element release>-patchX-XX.X.X.XXXX.iso

  4. Mount the management node ISO image and copy the contents to the file system using the following commands:

    sudo mkdir -p /upgrade
    sudo mount <solidfire-fdva-<Element release>-patchX-XX.X.X.XXXX.iso> /mnt
    sudo cp -r /mnt/* /upgrade
  5. Change to the home directory, and unmount the ISO file from /mnt:

    sudo umount /mnt
  6. Delete the ISO to conserve space on the management node:

    sudo rm <path to iso>/solidfire-fdva-<Element release>-patchX-XX.X.X.XXXX.iso
  7. On the management node that you are upgrading, run the following command to upgrade your management node OS version. The script retains all necessary configuration files after the upgrade, such as Active IQ collector and proxy settings.

    sudo /sf/rtfi/bin/sfrtfi_inplace file:///upgrade/casper/filesystem.squashfs sf_upgrade=1

    The management node reboots with a new OS after the upgrade process completes.

    Note After you run the sudo command described in this step, the SSH session is killed. Console access is required for continued monitoring. If no console access is available to you when performing the upgrade, retry the SSH login and verify connectivity after 15 to 30 minutes. Once you log in, you can confirm the new OS version in the SSH banner that indicates that the upgrade was successful.
  8. On the management node, run the redeploy-mnode script to retain previous management services configuration settings:

    Note The script retains previous management services configuration, including configuration from the Active IQ collector service, controllers (vCenters), or proxy, depending on your settings.
    sudo /sf/packages/mnode/redeploy-mnode -mu <mnode user>
Important If you had previously disabled SSH functionality on the management node, you need to disable SSH again on the recovered management node. SSH capability that provides NetApp Support remote support tunnel (RST) session access is enabled on the management node by default.

Reconfigure authentication using the management node REST API

You can keep your existing management node if you have sequentially upgraded (1) management services and (2) Element storage. If you have followed a different upgrade order, see the procedures for in-place management node upgrades.

Before you begin
  • You have updated your management services to version 2.20.69 or later.

  • Your storage cluster is running Element 12.3 or later.

  • You have sequentially updated your management services followed by upgrading your Element storage. You cannot reconfigure authentication using this procedure unless you have completed upgrades in the sequence described.

  1. Open the management node REST API UI on the management node:

  2. Select Authorize and complete the following:

    1. Enter the cluster user name and password.

    2. Enter the client ID as mnode-client if the value is not already populated.

    3. Select Authorize to begin a session.

  3. From the REST API UI, select POST /services/reconfigure-auth.

  4. Select Try it out.

  5. For the load_images parameter, select true.

  6. Select Execute.

    The response body indicates that reconfiguration was successful.

Find more information