Upgrading the SAN Volume Controller firmware using the SAN Volume Controller Console Software upgrade strategy Installing the upgrade using the CLI

This task provides step-by-step instructions about upgrading the cluster software using the SAN Volume Controller Console.

Software upgrade files can be quite large, if you experience problems when uploading upgrade files to the cluster reliably, you should disable proxies on the Web browser from where you will upload the file. This should also shorten the file upload time.

Note:Note: If you disable proxies, you may not be able to connect to external Web sites. It is therefore advised that prior to disabling proxies, you make a record of your existing settings in case you need to restore access to other Web sites.
Prerequisites

If you are using Internet Explorer, perform the following:

  1. Click on Tools in the menu.
  2. Select Internet Options ->Connections tab.
  3. Click on LAN Settings... and ensure that the box marked Use a proxy server is unchecked. Click OK twice to accept the settings.

If you are using Netscape, perform the following:

  1. Click on Edit in the menu.
  2. Click on Preferences.... Expand the Advanced section and select Proxies.
  3. Select the radio button marked Direct connection to the Internet. Click OK to accept the settings.
Note:Note: You cannot download the upgrade. You need to download the file to your local directory so the package can be uploaded in the process.
Steps

Perform the following steps to upgrade the software:

  1. Click Service and Maintenance from the portfolio.
  2. Click Upgrade Software to check the installed software level or to install a new level of software on the cluster. The Software Upgrade panel is displayed.
    Figure 167. Software upgrade panel
    svc_icatsoftwareupgrademain_238AVm
    Specify the location of the software upgrade file. This could be a URL.
  3. Click Upload to copy a new software level from your host to the cluster. (This action uses the upload feature of the Web browser.) The Software upgrade - file upload panel is displayed.
    Figure 168. Software upgrade - file upload panel
    svc_icatsoftwareupload_238AVW
    You can get new software levels from the IBM Product Support Web site, or from an installation CD.

    After a successful copy of the file, the install process fails if all the nodes configured into the cluster are not present. This behavior cannot be overridden using the force flag. If any node configured to be a member of the cluster is not present then in order to upgrade the software the node must either be deleted from the cluster or must be brought online. Furthermore, if a node has been deleted from the cluster such that any IO group has only one member then the software upgrade will also fail. This is because the upgrade process will result in loss of access to data. The force flag can be used to override this restriction if you are prepared to loose access to data during the upgrade.

    Before you begin the software upgrade, make sure that you are aware of the following:

    • The code is distributed to all the nodes in the cluster using fibre channel connections between the nodes.
    • Nodes are updated one at a time.
    • Nodes will begin executing the new software, concurrently with normal cluster activity.
    • The procedure to update a single node takes approximately 5 minutes.
    • During the update of a node it does not participate in I/O activity in the I/O group. Thus all I/O activity for the virtual disks in the I/O group is directed to the other node in the I/O group by the host multipathing software. During the update of a node the other node in the I/O group will notice that it's partner is not participating in the cluster and will as a result attempt to flush the write-back cache and set it into write-through mode. This flush is not guaranteed to be successful or to complete and as a result concurrent software update does create a single point of data loss. Should the remaining node in an I/O group experience a failure during a software update of its partner then the only valid copy of dirty data in the write-back cache could be lost.
    • All of the nodes connected to one uninterruptible power supply are updated first before any of the nodes connected to the other uninterruptible power supply.
    • A 30-minute delay is inserted into the procedure between updating the nodes connected to one uninterruptible power supply and starting to update the nodes on the other uninterruptible power supply. This allows time for the host multipathing software to rediscover paths to the nodes on the first uninterruptible power supply so that when nodes on the second uninterruptible power supply are updated loss of access does not result.
    • The update is not committed until all nodes in the cluster have been successfully updated to the new code level. If all nodes successfully re-start with the new code the new version is committed. When this happens, the cluster VPD is updated to reflect the new level of code. After this point downgrade to a package with a lower major number is no longer possible.
    • New behaviors or functions in the installed software will only be available to be invoked when all member nodes are upgraded and the update is committed.
    • Since the software upgrade process takes some time the install command completes as soon as the software package is verified by the cluster. To determine when the upgrade has completed you must either display the software version in the cluster VPD or look for the Software upgrade complete event in the error/event log. If any node fails to re-start with the new code level or fails at any other time during the process the code is backed-off.
    • During a software upgrade the version number of each node is updated when the software has been installed and that node has been restarted. The cluster software version number is updated when the new version of software is committed.
    • When code upgrade starts an entry is made in the error or event log and another entry is made when the upgrade completes or fails.
  4. Click Apply upgrade to display the Applying Software Upgrade panel. This page enables you to select the upgrade and to apply it to the cluster. This page displays a list of the software levels that you can apply to the cluster.
    Figure 169. Applying software upgrade panel
    svc_icatapplysoftwareupgrade_238AaF
Result

When a new code level is applied, it is automatically installed on all the nodes that are in the cluster. Note this process can take up to 30 minutes per node.

Related topics Software upgrade strategy Installing the upgrade using the CLI

(C) Copyright International Business Machines Corporation 2003, 2004