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

Table 2 Prerequisites checklist for all upgrades (continued)
Step
completed?DescriptionStep
If your FSN network bonded interfaces are currently configured for mode 6, configure them
for mode 4 bonding (LACP). Make sure your Network Administrator reconfigures the network
switch for LACP support on all effected ports. . Mode 4 has been found to outperform mode
6. This finding has resulted in changing the recommendation of mode 6 to mode 4.
7
Verify that all file system nodes can “see” and “access” every segment logical volume that
the file system node is configured for as either the owner or the backup by entering the
following commands:
8
1. To view all segments, logical volume name, and owner, enter the following command
on one line:
ibrix_fs -i | egrep -e OWNER -e MIXED|awk '{ print $1, $3, $6,
$2, $14, $5}' | tr " " "\t"
2. To verify the visibility of the correct segments on the current file system node enter the
following command on each file system node:
lvm lvs | awk '{print $1}'
Ensure that no active tasks are running. Stop any active Remote Replication, data tiering,
or Rebalancer tasks running on the cluster. (Use ibrix_task -l to list active tasks.)
When the upgrade is complete, you can start the tasks again.
9
For additional information on how to stop a task, enter the ibrix_task command for
the help.
Record all host tunings, FS tunings and FS mounting options by using the following
commands:
10
1. To display file system tunings, enter: ibrix_fs_tune -l
>/local/ibrix_fs_tune-l.txt
2. To display default IBRIX tunings and settings, enter: ibrix_host_tune -L
>/local/ibrix_host_tune-L.txt
3. To display all non-default configuration tunings and settings, enter: ibrix_host_tune
-q >/local/ibrix_host_tune-q.txt
Ensure that the "ibrix" local user account exists and it has the same UID number on all the
servers in the cluster. If they do not have the same UID number, create the account and
change the UIDs as needed to make them the same on all the servers. Similarly, ensure
that the "ibrix-user" local user group exists and has the same GID number on all servers.
11
Enter the following commands on each node:
grep ibrix /etc/passwd
grep ibrix-user /etc/group
Ensure that all nodes are up and running. To determine the status of your cluster nodes,
check the health of each server by either using the dashboard on the GUI or entering the
ibrix_health -S -i -h nodeX command for each node in the cluster. At the top of
the output look for “PASSED.”
12
Online upgrades for IBRIX software 6.x to 6.2
Online upgrades are supported only from the IBRIX 6.x release. Upgrades from earlier IBRIX
releases must use the appropriate offline upgrade procedure.
When performing an online upgrade, note the following:
• File systems remain mounted and client I/O continues during the upgrade.
• The upgrade process takes approximately 45 minutes, regardless of the number of nodes.
• The total I/O interruption per node IP is four minutes, allowing for a failover time of two minutes
and a failback time of two additional minutes.
• Client I/O having a timeout of more than two minutes is supported.
112 Upgrading the IBRIX software to the 6.2 release