English

Upgrade compute node firmware

Contributors netapp-amitha netapp-dbagwell amgrissino netapp-mwallis Download PDF of this topic

For any H-series compute node, you can upgrade the firmware for hardware components such as the BMC, BIOS, and NIC.

After the upgrade, the compute node boots into ESXi and works as before, retaining the configuration.

What you’ll need

See the firmware and driver matrix for your hardware in NetApp KB article 1088658 (login required).

It takes approximately 25 to 30 minutes for the upgrade via the BMC UI.
Upgrade options

Choose the option that is relevant to your upgrade scenario:

About this task

In production environments, upgrade the firmware on one compute node at a time.

Use a USB drive with the latest firmware image downloaded

You can insert a USB drive with the latest firmware image downloaded into a USB port on the compute node. As an alternative to using the USB thumb drive method described in this procedure, you can mount the compute node RTFI image on the compute node using the Virtual CD/DVD option in the Virtual Console in the Baseboard Management Controller (BMC) interface. The BMC method takes considerably longer than the USB thumb drive method. Ensure that your workstation or server has the necessary network bandwidth and that your browser session with the BMC does not time out.

Steps
  1. Browse to the NetApp software downloads page, click NetApp HCI, and click the download link for correct version of NetApp HCI.

  2. Accept the End User License Agreement.

  3. Under the Compute and Storage Nodes section, download the compute node image.

  4. Write the raw contents of the compute node RTFI image to a USB thumb drive with at least 32GB capacity (using dd or Etcher).

  5. Place the compute node in maintenance mode using VMware vCenter, and evacuate all virtual machines from the host.

    If VMware Distributed Resource Scheduler (DRS) is enabled on the cluster (this is the default in NetApp HCI installations), virtual machines will automatically be migrated to other nodes in the cluster.
  6. Insert the USB thumb drive into a USB port on the compute node and reboot the compute node using VMware vCenter.

  7. During the compute node POST cycle, press F11 to open the Boot Manager. You may need to press F11 multiple times in quick succession. You can perform this operation by connecting a video/keyboard or by using the console in BMC.

  8. Select One Shot > USB Flash Drive from the menu that appears. If the USB thumb drive does not appear in the menu, verify that USB Flash Drive is part of the legacy boot order in the BIOS of the system.

  9. Press Enter to boot the system from the USB thumb drive. The firmware flash process begins.

    After firmware flashing is complete and the node reboots, it might take a few minutes for ESXi to start.

  10. After the reboot is complete, exit maintenance mode on the upgraded compute node using vCenter.

  11. Remove the USB flash drive from the upgraded compute node.

  12. Repeat this task for other compute nodes in your ESXi cluster until all compute nodes are upgraded.

Use the Baseboard Management Controller (BMC) user interface (UI)

You must perform the sequential steps to load the compute firmware ISO and reboot the node to the ISO to ensure that the upgrade is successful. The ISO should be located on the system or virtual machine (VM) hosting the web browser. Ensure that you have downloaded the ISO before you start the process.

The recommendation is to have the system or VM and the node on the same network.

Upgrade firmware on H410C and H300E/H500E/H700E nodes

If your node is part of a cluster, you must place the node in maintenance mode before the upgrade, and take it out of maintenance mode after the upgrade.

Ignore the following informational message you see during the process: Untrusty Debug Firmware Key is used, SecureFlash is currently in Debug Mode
Steps
  1. If your node is part of a cluster, place it in maintenance mode as follows. If not, skip to step 2.

    1. Log in to the VMware vCenter web client.

    2. Right-click the host (compute node) name and select Maintenance Mode > Enter Maintenance Mode.

    3. Click OK.
      VMs on the host will be migrated to another available host. VM migration can take time depending on the number of VMs that need to be migrated.

      Ensure that all the VMs on the host are migrated before you proceed.
  2. Navigate to the BMC UI, https://BMCIP/#login, where BMCIP is the IP address of the BMC.

  3. Log in using your credentials.

  4. Select Remote Control > Console Redirection.

  5. Click Launch Console.

    You might have to install Java or update it.
  6. When the console opens, click Virtual Media > Virtual Storage.

  7. On the Virtual Storage screen, click Logical Drive Type, and select ISO File.

    Shows the navigation path to select the ISO file.

  8. Click Open Image to browse to the folder where you downloaded the ISO file, and select the ISO file.

  9. Click Plug In.

  10. When the connection status shows Device#: VM Plug-in OK!!, click OK.

  11. Reboot the node by pressing F12 and clicking Restart or clicking Power Control > Set Power Reset.

  12. During reboot, press F11 to select the boot options and load the ISO. You might have to press F11 a few times before the boot menu is displayed.

    You will see the following screen:

    Shows the screen the virtual ISO boots up to.

  13. On the above screen, press Enter. Depending on your network, it might take a few minutes after you press Enter for the upgrade to begin.

    NOTE: Some of the firmware upgrades might cause the console to disconnect and/or cause your session on the BMC to disconnect. You can log back into the BMC, however some services, such as the console, may not be available due to the firmware upgrades. After the upgrades have completed, the node will perform a cold reboot, which can take approximately five minutes.
  14. Log back in to the BMC UI and click System to verify the BIOS version and build time after booting to the OS. If the upgrade completed correctly, you see the new BIOS and BMC versions.

    The BIOS version will not show the upgraded version until the node has finished fully booting.
  15. If the node is part of a cluster, complete the steps below. If it is a standalone node, no further action is needed.

    1. Log in to the VMware vCenter web client.

    2. Take the host out of maintenance mode. This might show a disconnected red flag. Wait until all statuses are cleared.

    3. Power on any of the remaining VMs that were powered off.

Upgrade firmware on H610C/H615C nodes

The steps vary depending on whether the node is standalone or part of a cluster. The procedure can take approximately 25 minutes and includes powering the node off, uploading the ISO, flashing the devices, and powering the node back on after the upgrade.

Steps
  1. If your node is part of a cluster, place it in maintenance mode as follows. If not, skip to step 2.

    1. Log in to the VMware vCenter web client.

    2. Right-click the host (compute node) name and select Maintenance Mode > Enter Maintenance Mode.

    3. Click OK.
      VMs on the host will be migrated to another available host. VM migration can take time depending on the number of VMs that need to be migrated.

      Ensure that all the VMs on the host are migrated before you proceed.
  2. Navigate to the BMC UI, https://BMCIP/#login, where BMC IP is the IP address of the BMC.

  3. Log in using your credentials.

  4. Click Remote Control > Launch KVM (Java).

  5. In the console window, click Media > Virtual Media Wizard.

    Start the Virtual Media Wizard from the BMC UI.
  6. Click Browse and select the compute firmware .iso file.

  7. Click Connect.
    A popup indicating success is displayed, along with the path and device showing at the bottom. You can close the Virtual Media window.

    Popup window showing ISO upload success.
  8. Reboot the node by pressing F12 and clicking Restart or clicking Power Control > Set Power Reset.

  9. During reboot, press F11 to select the boot options and load the ISO.

  10. Select AMI Virtual CDROM from the list displayed and click Enter. If you do not see AMI Virtual CDROM in the list, go into the BIOS and enable it in the boot list. The node will reboot after you save. During the reboot, press F11.

    Shows the window where you can select the boot device.
  11. On the screen displayed, click Enter.

    Some of the firmware upgrades might cause the console to disconnect and/or cause your session on the BMC to disconnect. You can log back into the BMC, however some services, such as the console, might not be available due to the firmware upgrades. After the upgrades have completed, the node will perform a cold reboot, which can take approximately five minutes.
  12. If you get disconnected from the console, select Remote Control and click Launch KVM or Launch KVM (Java) to reconnect and verify when the node has finished booting back up. You might need multiple reconnects to verify that the node booted successfully.

    During the powering on process, for approximately five minutes, the KVM console displays No Signal.
  13. After the node is powered on, select Dashboard > Device Information > More info to verify the BIOS and BMC versions. The upgraded BIOS and BMC versions are displayed. The upgraded version of the BIOS will not be displayed until the node has fully booted up.

  14. If you placed the node in maintenance mode, after the node boots to ESXi, right-click the host (compute node) name, and select Maintenance Mode > Exit Maintenance Mode, and migrate the VMs back to the host.

  15. In vCenter, with the host name selected, configure and verify the BIOS version.

Find more information