Updating the software using the CLI

You can check the current level of software and update the software by using the command-line interface (CLI) as an alternative to using the management GUI.

Before you begin

Before you start the update, ensure that you complete the tasks in the subsections for Before starting the upgrade.

If you plan to use the command-line interface (CLI) to update, go to IBM Fix Central to download the Software Update Test Utility and new software package. You can put these files on either a USB flash drive or a GPFS file system by using any of the standard share protocols like CIFS, NFS, or SCP. If you use a USB flash drive, ensure that the flash drive is partitioned and formatted in the same way as the USB flash drive that is used for the system initialization tool, InitTool.exe. For further information, see USB flash drive and Initialization tool interface. After you upload the Software Update Test Utility and update package to the system, check the health status before you apply the software update.

Attention:
  • Do not make any configuration changes during the update.
  • The update will fail over the management service one or more times during the update. Do not attempt to start the management services while the update is in progress.

Procedure

  1. Initiate the update using either the USB drive or a shared file system.
    1. To update the code using a USB flash drive:
      1. Determine which node is the active management node by running the lsnode command from the command line of the management node. See Figure 1.
        Figure 1. Example of output that shows an active and passive management node.
        [kq186wx.ibm]$ lsnode
        
        Hostname     IP         Description             Role                         Product version Connection status GPFS status CTDB status Last updated
        mgmt001st001 10.254.8.2 active management node  management,interface,storage 1.3.0.0-74e     OK                active      active      12/5/11 12:45 PM
        mgmt002st001 10.254.8.3 passive management node management,interface,storage 1.3.0.0-74e     OK                active      active      12/5/11 12:45 PM
        
        EFSSG1000I The command completed successfully.
        [kq186wx.ibm]$
      2. For example, run this command to locate the active management node and turn on the locator LEDs on the mgmt001st001 node for 20 seconds:
        locatenode mgmt001st001 -e 20 

        This command activates a solid-blue locator LED on the node.

      3. Insert the USB flash drive into the USB port on the front of the active management node.
      4. From the command line, run the following appropriate command. Make sure that you refer to the software package by using the full file system path.
        For systems at 1.4.1.x or lower, run this command:
        applysoftware /media/usb/<name_of_Test_Utility_package>
        For systems at 1.4.2.x or higher, run this command:
        applysoftware /media/usb/<name_of_Test_Utility_package> --options release=/media/usb/<name_of_upgrade_package>
        If there are any errors, correct these errors before running the Test Utility again. When the Test Utility runs with no errors, run this command:
        applysoftware /media/usb/<name_of_upgrade_package>

        This action displays the text in Figure 3

        Note: During the update the active management node fails over to secondary node and fails back to the original node.
      5. From the command line, run this command:
        applysoftware /media/usb/<name of update package>
        .
      Important: The USB flash drive is mounted automatically when the applysoftware command is run. You do not need to mount the USB flash drive manually.
    2. To update the code using the Storwize® V7000 Unified shared file system:
      1. Run the lsexport command to identify the exported file system on which to place the update package. See Figure 2.
        Figure 2. Identifying your export and full system path
        [YourCluster]$ lsexport
        Name      Path                  Protocol Active Timestamp
        boogiesfu /ibm/gpfs0/boogie_sfu FTP      true   1/27/12 2:34 PM
        boogiesfu /ibm/gpfs0/boogie_sfu HTTP     true   1/27/12 1:41 PM
        boogiesfu /ibm/gpfs0/boogie_sfu NFS      true   1/27/12 1:48 PM
        boogiesfu /ibm/gpfs0/boogie_sfu CIFS     true   1/27/12 1:55 PM
        boogiesfu /ibm/gpfs0/boogie_sfu SCP      true   1/27/12 2:02 PM
        EFSSG1000I The command completed successfully.
        [YourCluster]$
      2. Copy the software package and Test Utility to the exported file system.
      3. From the command line, run the following appropriate command. Ensure that you refer to the software package by using the full file system path as determined by lsexport.

        For systems at 1.4.1.x or lower, run the following:

        applysoftware /ibm/<gpfs_filesystem_name>/<name_of_Test_Utility_package>

        For systems at 1.4.2.x or higher, run the following:

        applysoftware /ibm/<gpfs_filesystem_name>/<name_of_Test_Utility_package> --options release=/ibm/<gpfs_filesystem_name>/<name_of_upgrade_package>

        If there are any errors, correct these errors before running the Test Utility again. When the Test Utility runs with no errors, run the following command:

        applysoftware /ibm/<gpfs_filesystem_name>/<name_of_upgrade_package>

        This action displays the text in Figure 3

        Note: During the update the active management node fails over to secondary node and fails back to the original node.
  2. When you invoked the applysoftware command, did you see the message in Figure 3?
    Figure 3. The license agreement has not been accepted
    [YourCluster ~]$ applysoftware /ibm/gpfs0/boogie_sfu/upgrade-1.3.0.3-02
    EFSSA0201C The license agreement has not been accepted.
    1. Yes.
      1. Run the following command.

        enablelicense --accept

      2. Run the applysoftware command again.
  3. Wait for the applysoftware command to finish. Figure 6 shows an example of the applysoftware command that completed successfully.
    1. If the applysoftware command displays error codes and messages, go to Upgrade recovery.
      Remember: The update will fail over the management service one or more times during the update.
      Figure 4. Example of applysoftware command that completed successfully
      [YourCluster]$ applysoftware /ibm/gpfs0/boogie_sfu/upgrade-1.3.0.3-02
      EFSSG1000I The command completed successfully.
  4. After the applysoftware command finishes, run the lsupdate command to view the status of the update.
    1. If the lsupdate command displays a CurrentState of error as shown in Figure 5, go to Upgrade recovery.
      Figure 5. Example of applysoftware command that did not complete successfully
      [YourCluster]$ lsupdate
      Type    Name         CurrentState CurrentTask        PercentComplete
      cluster YourCluster  idle         none               033
      node    mgmt001st001 error 01D2   U030node_stop_gpfs 020
      node    mgmt002st001 idle         none               0
      EFSSG1000I The command did not complete successfully.
      [YourCluster]$
    2. When the lsupdate command displays a CurrentState of complete for cluster, as shown in Figure 6, the update is finished.
      Figure 6. Example of applysoftware command completed successfully
      [YourCluster]$ lsupdate
      Type    Name         CurrentState CurrentTask   PercentComplete
      cluster YourCluster  complete     none          100
      node    mgmt001st001 complete     none          100
      node    mgmt002st001 complete     none          100
      EFSSG1000I The command completed successfully.
      [YourCluster] $
  5. If you updated the software from USB, remove the USB flash drive.

What to do next

Before you complete the update process, ensure that you perform the steps in subsections for After you upgrade.