Table of Contents
Advertisement
1.
Power on the node hosting the active Fusion Manager.
2.
Power on the file serving nodes (*root segment = segment 1; power on owner first, if possible).
3.
Monitor the nodes on the GUI and wait for them all to report UP in the output from the following
command:
ibrix_server -l
4.
Mount file systems and verify their content. Run the following command on the file serving
node hosting the active Fusion Manager:
ibrix_mount -f fs_name -m <mountpoint>
On Linux 9000 clients, run the following command:
ibrix_lwmount -f fsname -m <mountpoint>
5.
Enable HA on the file serving nodes. Run the following command on the file serving node
hosting the active Fusion Manager:
ibrix_server -m
6.
On the node hosting the passive agile Fusion Manager, move the console back to passive
mode:
ibrix_fm -m passive
The IBRIX software is now available, and you can now access your file systems.
Powering file serving nodes on or off
When file serving nodes are connected to properly configured power sources, the nodes can be
powered on or off or can be reset remotely. To prevent interruption of service, set up standbys for
the nodes (see
them over before powering them off (see
powering off a file serving node does not trigger failover.
To power on, power off, or reset a file serving node, use the following command:
ibrix_server -P {on|reset|off} -h HOSTNAME
Performing a rolling reboot
The rolling reboot procedure allows you to reboot all file serving nodes in the cluster while the
cluster remains online. Before beginning the procedure, ensure that each file serving node has a
backup node and that IBRIX HA is enabled. See
(page 31)
and
creating standby backup pairs, where each server in a pair is the standby for the other.
Use one of the following schemes for the reboot:
Reboot the file serving nodes one-at-a-time.
Divide the file serving nodes into two groups, with the nodes in the first group having backups
in the second group, and the nodes in the second group having backups in the first group.
You can then reboot one group at-a-time.
To perform the rolling reboot, complete the following steps on each file serving node:
1.
Reboot the node directly from Linux. (Do not use the "Power Off" functionality in the GUI, as
it does not trigger failover of file serving services.) The node will fail over to its backup.
2.
Wait for the GUI to report that the rebooted node is Up.
3.
From the GUI, failback the node, returning services to the node from its backup. Run the
following command on the backup node:
ibrix_server -f -U -h HOSTNAME
HOSTNAME is the name of the node that you just rebooted.
90
Maintaining the system
"Configuring High Availability on the cluster" (page
"Configuring High Availability on the cluster" (page 37)
"Failing a server over manually" (page
"Configuring virtual interfaces for client access"
37), and then manually fail
45)). Remotely
for more information about
Advertisement
Table of Contents
Troubleshooting
