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 following command:
/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, run the following command and then reboot the machine.
This step causes the server to boot from the old version (the alternate partition).
/usr/local/ibrix/setup/boot_info –r
• If the public network interface is down and inaccessible for any node, power cycle that node.
NOTE: Each node stores its ibrixupgrade.log file in /tmp.
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 following command:
/usr/local/ibrix/autocfg/bin/ibrixapp upgrade –f –s
Offline upgrade fails because iLO firmware is out of date
If the iLO2 firmware is out of date on a node, the auto_ibrixupgrade script will fail. The /usr/
local/ibrix/setup/logs/auto_ibrixupgrade.log reports the failure and describes how
to update the firmware.
After updating the firmware, run the following command on the node to complete the IBRIX software
upgrade:
/root/ibrix/ibrix/ibrixupgrade -f
Node is not registered with the cluster network
Nodes hosting the agile Fusion Manager must be registered with the cluster network. If the
ibrix_fm command reports that the IP address for a node is on the user network, you will need
to reassign the IP address to the cluster network. For example, the following commands report that
node ib51–101, which is hosting the active Fusion Manager, has an IP address on the user
network (15.226.51.101) instead of the cluster network.
[root@ib51-101 ibrix]# ibrix_fm -i
FusionServer: ib51-101 (active, quorum is running)
Upgrading the IBRIX software to the 6.1 release 155