16. From the node on which you failed back the active management console in step 8, change
the status of the management console from maintenance to passive:
<ibrixhome>/bin/ibrix_fm -m passive
17. If the node with the passive management console is also a file serving node, manually fail
over the node from the active management console:
<ibrixhome>/bin/ibrix_server -f -p -h HOSTNAME
Wait a few minutes for the node to reboot, and then run the following command to verify that
the failover was successful. The output should report
Up, FailedOver
.
<ibrixhome>/bin/ibrix_server -l
18. On the node with the passive agile management console, 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 StoreAll installation on this node, the
installer is in
nl
/root/ibrix
.
19. On the node hosting the passive agile management console, 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
.
20. 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 the node.
21. 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...
Also run the following command, which should report that the console is passive:
<ibrixhome>/bin/ibrix_fm -i
22. Check
/usr/local/ibrix/log/fusionserver.log
for errors.
23. If the upgrade was successful, fail back the node. Run the following command on the node
with the active agile management console:
<ibrixhome>/bin/ibrix_server -f -U -h HOSTNAME
24. Verify that the agile management console software and the file serving node software are
now upgraded on the two nodes hosting the agile management console:
<ibrixhome>/bin/ibrix_version -l -S
Following is some sample output:
Fusion Manager version: 5.5.XXX
===============================
Segment Servers
===============
HOST_NAME FILE_SYSTEM IAD/IAS IAD/FS OS KERNEL_VERSION ARCH
--------- ---------------------- ------- ------- --------- -------------- ----
ib50-86 5.5.205(9000_5_5) 5.5.XXX 5.5.XXX GNU/Linux 2.6.18-128.el5 x86_64
ib50-87 5.5.205(9000_5_5) 5.5.XXX 5.5.XXX GNU/Linux 2.6.18-128.el5 x86_64
You can now upgrade any remaining file serving nodes.
Upgrading remaining file serving nodes
Complete the following steps on each file serving node:
196
Cascading Upgrades
