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

Automatic upgrade
Check the following:
• If the initial execution of /usr/local/ibrix/setup/upgrade fails, check
/usr/local/ibrix/setup/upgrade.log for errors. It is imperative that all servers are
up and running the IBRIX software before you execute the upgrade script.
• If the install of the new OS fails, power cycle the node. Try rebooting. If the install does not
begin after the reboot, power cycle the machine and select the upgrade line from the grub
boot menu.
• After the upgrade, check /usr/local/ibrix/setup/logs/postupgrade.log for errors
or warnings.
• If configuration restore fails on any node, look at
/usr/local/ibrix/autocfg/logs/appliance.log on that node to determine which
feature restore failed. Look at the specific feature log file under /usr/local/ibrix/setup/
logs/ for more detailed information.
To retry the copy of configuration, use the command appropriate for your server:
◦ A file serving node:
/usr/local/ibrix/autocfg/bin/ibrixapp upgrade –s
◦ An agile node (a file serving node hosting the agile management console):
/usr/local/ibrix/autocfg/bin/ibrixapp upgrade –f –s
• If the install of the new image succeeds, but the configuration restore fails and you need to
revert the server to the previous install, execute boot_info –r and then reboot the machine.
This step causes the server to boot from the old version (the alternate partition).
• If the public network interface is down and inaccessible for any node, power cycle that node.
Manual upgrade
Check the following:
• If the restore script fails, check /usr/local/ibrix/setup/logs/restore.log for
details.
• If configuration restore fails, look at /usr/local/ibrix/autocfg/logs/appliance.log
to determine which feature restore failed. Look at the specific feature log file under /usr/
local/ibrix/setup/logs/ for more detailed information.
To retry the copy of configuration, use the command appropriate for your server:
◦ A file serving node:
/usr/local/ibrix/autocfg/bin/ibrixapp upgrade –s
◦ An agile node (a file serving node hosting the agile management console):
/usr/local/ibrix/autocfg/bin/ibrixapp upgrade –f –s
Upgrading the IBRIX software to the 5.5 release
This section describes how to upgrade to the IBRIX software 5.5 release. The management console
and all file serving nodes must be upgraded to the new release at the same time.
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.
160 Cascading Upgrades