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

Upgrading the IBRIX software to the 5.6 release
This section describes how to upgrade to the latest IBRIX software release. The management console
and all file serving nodes must be upgraded to the new release at the same time. Note the following:
• Upgrades to the IBRIX software 5.6 release are supported for systems currently running IBRIX
software 5.5.x. If your system is running an earlier release, first upgrade to the 5.5 release,
and then upgrade to 5.6.
• The upgrade procedure upgrades the operating system to Red Hat Enterprise Linux 5.5.
IMPORTANT: Do not start new remote replication jobs while a cluster upgrade is in progress. If
replication jobs were running before the upgrade started, the jobs will continue to run without
problems after the upgrade completes.
The upgrade to IBRIX software 5.6 is supported only as an offline upgrade. Because it requires an
upgrade of the kernel, the local disk must be reformatted. Clients will experience a short interruption
to administrative and file system access while the system is upgraded.
There are two upgrade procedures available depending on the current installation. If you have an
IBRIX software 5.5 system that was installed through the QR procedure, you can use the automatic
upgrade procedure. If you used an upgrade procedure to install your IBRIX software 5.5 system,
you must use the manual procedure. To determine if your system was installed using the QR
procedure, run the df command. If you see separate file systems mounted on /, /local, /stage,
and /alt, your system was quick-restored and you can use the automated upgrade procedure.
If you do not see these mount points, proceed with the manual upgrade process.
• Automatic upgrades. This process uses separate partitioned space on the local disk to save
node-specific configuration information. After each node is upgraded, its configuration is
automatically reapplied.
• Manual upgrades. Before each server upgrade, this process requires that you back up the
node-specific configuration information from the server onto an external device. After the
server is upgraded, you will need to copy and restore the node-specific configuration
information manually.
The upgrade takes approximately 45 minutes for 9320 systems with a standard configuration.
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.
Automatic upgrades
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. To determine the status of your
cluster nodes, check the dashboard on the GUI or use the ibrix_health command.
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. Obtain the latest release image from the HP kiosk at http://www.software.hp.com/kiosk (you
will need your HP-provided login credentials).
3. Copy the release .iso file onto the current active management console.
4. Run the following command, specifying the location of the local iso copy as the argument:
/usr/local/ibrix/setup/upgrade <iso>
The upgrade script performs all necessary upgrade steps on every server in the cluster and
logs progress in the file /usr/local/ibrix/setup/upgrade.log. After the script
completes, each server will be automatically rebooted and will begin installing the latest
software.
5. After the install is complete, the upgrade process automatically restores node-specific
configuration information and the cluster should be running the latest software. If an UPGRADE
Upgrading the IBRIX software to the 5.6 release 157