Updating nodes

Update nodes before an IBM Storage Scale System deployment or upgrade because the entire cluster depends on consistent OS, firmware, kernel modules, and networking behavior. If the underlying nodes are not healthy or aligned, deployment or upgrade cannot be successful.

Before you start deployment, check whether management servers, protocols, and I/O nodes on an IBM Storage Scale System need any updates, and update these nodes if required.
essrun -n emsvm,IOnodes update --precheck
  1. Update a management server.
    • To update the Power9 management server, issue the following command:
      essrun -N <MS1> update --offline
    • To update the Utility Node management server virtual machine (Utility Node VM), issue the following command:
      essrun -N MSVM update --offline
      Note: The Utility Node, a bare-metal host, does not need to be updated separately. Because this host is updated automatically when you update the Utility Node VM node on the host.
      Use ssh to get back to the Utility Node VM when is up and running through the virtual bridge.
      Note: The virtual bridge is not always the same; it varies from 10.23.16.2 to 10.23.16.6.

      Alternatively, use ssh through the campus or use the management address that you assigned to the Utility Node VM.

    If the kernel is changed, run the following commands:
    1. Exit the container.
      exit
    2. Reboot the Power9 management server or Utility Node VM node.
      systemctl reboot
    3. Navigate to the extracted IBM Storage Scale System Start of change7.0.1.x End of change directory, and then restart the container.
      /home/deploy/ess_7.0.1.x_0611-23.tar.dir
      ./essmkyml --restart
    4. Update management server or Utility Node VM nodes again.
      essrun -N <MS1> update --offline
    5. After a successful updates, reboot the Power9 management server or Utility Node VM node.
      systemctl reboot
  2. Update the I/O nodes from Power9 management server or Utility Node VM.
    Start of change
    essrun -N <nodeclasses> update --offline
    End of change
    Start of changeWhere nodeclasses are as follows:
    • IBM Storage Scale System 5000: ess_ppc64le
    • IBM Storage Scale System 3000: ess_x86_64
    • IBM Storage Scale System 3200: ess3200_x86_64
    • IBM Storage Scale System 3500: ess3500_x86_64
    • Start of changeProtocol Power9: ces_ppc64leEnd of change
    • IBM Storage Scale System 6000: s6k_x86_64
    Update all nodes of all building blocks except the Power9 management server or Utility Node VM.End of change
  3. Start of changeUpdate Start of changeI/O and protocol nodes at onceEnd of change from Power9 management sever.
    essrun -N prt01,prt02 update --offline
    End of change
  4. If the protocol node is part of a GPFS cluster, run the mmbuildgpl command after the protocol node update is completed from the Power9 management server.

    For more information, see mmbuildgpl command in IBM Storage Scale documentation.