6.2 HP IBRIX 9300/9320 Storage Administrator Guide (AW549-96049, December 2012)

NOTE: If you are upgrading from an IBRIX 5.x release, any support tickets collected with the
ibrix_supportticket command will be deleted during the upgrade. Download a copy of the
archive files (.tgz) from the /admin/platform/diag/supporttickets directory.
Upgrades can be run either online or offline:
• 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 file systems be unmounted on the node and
that services be stopped. (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 experience
a short interruption to file system access while each file serving node is upgraded.
You can use an automatic or a manual procedure to perform an offline upgrade. Online upgrades
must be performed manually.
Automatic upgrades
The automated upgrade procedure is run as an offline upgrade. When each file serving node is
upgraded, all file systems are unmounted from the node and services are stopped. Clients will
experience a short interruption to file system access while the node is upgraded.
All file serving nodes and management consoles must be up when you perform the upgrade. If a
node or management console is not up, the upgrade script will fail and you will need to use a
manual upgrade procedure instead. To determine the status of your cluster nodes, check the
dashboard on the GUI.
To upgrade all nodes in the cluster automatically, complete the following steps:
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 IBRIX 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.
Upgrading the IBRIX software to the 5.5 release 161