Upgrading the protocol nodes

Upgrade the protocol nodes (virtual machines and Power protocol nodes) by using IBM Storage Scale installation toolkit or the essrun command.

You can upgrade the protocol nodes after the target IBM Storage Scale System release image is available on the management server and, if applicable, on the protocol nodes.
Run the essrun commands from the management server or from the active IBM Storage Scale System container, depending on your upgrade workflow.
Note: Start of changeOn IBM Storage Scale System 7.0.1, only online upgrades are supported.End of change
  1. Start of change Upgrade IBM Storage Scale on the protocol nodes.

    To upgrade the protocol nodes by using the essrun command, complete the following upgrade steps:

    1. Populate the protocol node inventory. 
      essrun -N <ems_node> protocol upgrade configpopulate

      For example:

      essrun -N utility1-vm1-hs protocol upgrade configpopulate
    2. Check the configuration of populated nodes. 
      essrun -N <ems_node> protocol upgrade nodelist

      For example:

      essrun -N utility1-vm1-hs protocol upgrade nodelist
    3. Check all protocol nodes before the upgrade. 
      essrun -N <ems_node> protocol upgrade precheck
      For example:
      essrun -N utility1-vm1-hs protocol upgrade precheck
    4. Upgrade the protocol nodes. 
      essrun -N <ems_node> protocol upgrade run

      For example:

      essrun -N utility1-vm1-hs protocol upgrade run

      For protocol nodes upgrade you can use the installation toolkit. For more information, see Performing online upgrade by using the installation toolkit in the IBM Storage Scale documentation.

    Important: A LEAPP upgrade of an operating system can remove IBM Storage Scale and protocol packages from one or more nodes. If this issue occurs, you can reinstall packages. To install the packages, see GPFS and protocol packages removed after LEAPP operating system upgrade.
    End of change
  2. Upgrade the operating system and other components from the IBM Storage Scale System container.
    1. Start of changeShut down the protocol nodes. 
      mmshutdown -N <protocol_node>
      where, protocol_node that is upgraded for the operating system.

      For more information, see the mmshutdown command.

      End of change
    2. Start IBM Storage Scale daemon on protocol nodes. 
      mmstartup -N <protocol_node>

      For more information, see the mmstartup command.

    3. Upgrade the operation system and other components. 
      essrun -N prt1,prt2 update --offline
    4. After the operating system upgrade (kernel changes), create an IBM Storage Scale portability layer. 
      /usr/lpp/mmfs/bin/mmbuildgpl

      For more information, see building the GPL on Linux nodes.

  3. Update the system firmware of the Power protocol nodes.
    Warning: Do not revert the system firmware level to an earlier version because it can cause a system breakage. Instead, upgrade the firmware to any latest firmware level available.
    Remember: The system reboots automatically and the firmware is upgraded. This process can take up to 1 hour and 30 minutes per node. Consider this for planning the maintenance window.
    1. Go to the firmware directory and look for the 1VL950_131_045.img file. 
      cd /install/ess/otherpkgs/rhels8/ppc64le/firmware/
    2. Verify the package. 
      update_flash -v -f 01VL950_131_045.img

      If the result of the verification does not flag any issues, proceed with the update.

    3. Start the update. 
      update_flash -f 01VL950_131_045.img

      Flashing the firmware sets the new image as temporary. After you are comfortable with the new firmware, you must commit it to permanent:

      update_flash -c