6.3 HP StoreAll 9300/9320 Storage Administrator Guide (AW549-96072, June 2013)

1. Check the dashboard on the management console GUI to verify that all nodes are up.
2. Verify that you have an even number of FSNs configured in a couplet pair high availability
architecture by running the following command:
ibrix_server -l
3. On the current active management console, move the <installer_dir>/ibrix directory
used in the previous release installation to ibrix.old. For example, if you expanded the
tarball in /root during the previous StoreAll installation on this node, the installer is in /root/
ibrix.
4. On the current active management console, expand the distribution tarball or mount the
distribution DVD in a directory of your choice. Expanding the tarball creates a subdirectory
named ibrix that contains the installer program. For example, if you expand the tarball in
/root, the installer is in /root/ibrix.
5. Change to the installer directory on the active management console, if necessary. Run the
following command:
./auto_ibrixupgrade
The upgrade script performs all necessary upgrade steps on every server in the cluster and
logs progress in the upgrade.log file. The log file is located in the installer directory.
Manual upgrades
Upgrade paths
There are two manual upgrade paths: a standard upgrade and an agile upgrade.
• The standard upgrade is used on clusters having a dedicated Management Server machine
or blade running the management console software.
• The agile upgrade is used on clusters having an agile management console configuration,
where the management console software is installed in an active/passive configuration on
two cluster nodes.
To determine whether you have an agile management console configuration, run the ibrix_fm
-i command. If the output reports the status as quorum is not configured, your cluster
does not have an agile configuration.
Be sure to use the upgrade procedure corresponding to your management console configuration:
• For standard upgrades, use Page 168.
• For agile upgrades, use Page 172.
Online and offline upgrades
Online and offline upgrade procedures are available for both the standard and agile upgrades:
• Online upgrades. This procedure upgrades the software while file systems remain mounted.
Before upgrading a file serving node, you will need to fail the node over to its backup node,
allowing file system access to continue. This procedure cannot be used for major upgrades,
but is appropriate for minor and maintenance upgrades.
• Offline upgrades. This procedure requires that you first unmount file systems and stop services.
(Each file serving node may need to be rebooted if NFS or SMB causes the unmount operation
to fail.) You can then perform the upgrade. Clients will experience a short interruption to file
system access while each file serving node is upgraded.
Standard upgrade for clusters with a dedicated Management Server machine or blade
Use these procedures if your cluster has a dedicated Management Server machine or blade hosting
the management console software. The StoreAll software 5.4.x to 5.5 upgrade can be performed
either online or offline. Future releases may require offline upgrades.
NOTE: Be sure to read all instructions before starting the upgrade procedure.
168 Cascading Upgrades