6.2 HP IBRIX 9300/9320 Storage Administrator Guide (AW549-96049, December 2012)
Preparing for the upgrade
1. On the active management console node, disable automated failover on all file serving nodes:
<ibrixhome>/bin/ibrix_server -m -U
2. Verify that automated failover is off. In the output, the HA column should display off.
<ibrixhome>/bin/ibrix_server -l
3. On the active management console node, stop the NFS and SMB services on all file serving
nodes to prevent NFS and SMB clients from timing out.
<ibrixhome>/bin/ibrix_server -s -t cifs -c stop
<ibrixhome>/bin/ibrix_server -s -t nfs -c stop
Verify that all likewise services are down on all file serving nodes:
ps –ef | grep likewise
Use kill -9 to kill any likewise services that are still running.
4. Unmount all IBRIX file systems:
<ibrixhome>/bin/ibrix_umount -f <fsname>
Upgrading the file serving nodes hosting the management console
Complete the following steps:
1. On the node hosting the active management console, force a backup of the management
console configuration:
<ibrixhome>/bin/ibrix_fm -B
The output is stored at /usr/local/ibrix/tmp/fmbackup.zip. Be sure to save this file
in a location outside of the cluster.
2. On the node hosting the passive management console, place the management console into
maintenance mode:
<ibrixhome>/bin/ibrix_fm -m nofmfailover
3. On the active management console node, 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 active management console node, 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 if necessary and run the upgrade:
./ibrixupgrade -f
The installer upgrades both the management console software and the file serving node
software on this node.
6. Verify the status of the management console:
/etc/init.d/ibrix_fusionmanager status
The status command confirms whether the correct services are running. Output will be similar
to the following:
Fusion Manager Daemon (pid 18748) running...
7. Check /usr/local/ibrix/log/fusionserver.log for errors.
8. Upgrade the remaining management console node. Move the ibrix directory used in the
previous release to ibrix.old. Then 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
nl
/root, the installer is in /root/ibrix.
170 Cascading Upgrades