Table of Contents
Advertisement
To determine whether you have an agile management console configuration, run the ibrix_fm
-i command. If the output reports the status as quorum is not configured, your cluster
does not have an agile configuration.
Be sure to use the upgrade procedure corresponding to your management console configuration:
For standard upgrades, use
For agile upgrades, use
Online and offline upgrades
Online and offline upgrade procedures are available for both the standard and agile upgrades:
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 you first unmount file systems and stop services.
(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 will experience a short interruption to file
system access while each file serving node is upgraded.
Standard upgrade for clusters with a dedicated Management Server machine or blade
Use these procedures if your cluster has a dedicated Management Server machine or blade hosting
the management console software. The IBRIX software 5.4.x to 5.5 upgrade can be performed
either online or offline. Future releases may require offline upgrades.
NOTE:
Be sure to read all instructions before starting the upgrade procedure.
Standard online upgrade
The management console must be upgraded first. You can then upgrade file serving nodes and
9000 clients in any order.
Upgrading the management console
Complete the following steps on the Management Server machine or blade:
1.
Disable automated failover on all file serving nodes:
<ibrixhome>/bin/ibrix_server -m -U
2.
Verify that automated failover is off:
<ibrixhome>/bin/ibrix_server -l
In the output, the HA column should display off.
3.
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.
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
6.
Verify that the management console is operational:
/etc/init.d/ibrix_fusionmanager status
The status command should report that the correct services are running. The output is similar
to this:
Fusion Manager Daemon (pid 18748) running...
7.
Check /usr/local/ibrix/log/fusionserver.log for errors.
162 Cascading Upgrades
Page
162.
Page
166.
Advertisement
Table of Contents
Troubleshooting
