Table of Contents
Advertisement
1.
Power on the dedicated Management Console or the node hosting the active agile management
console.
2.
Power on the file serving nodes (*root segment = segment 1; power on owner first, if possible).
3.
Monitor the nodes on the management console 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 Management
Console or file serving node hosting the active agile management console:
ibrix_mount -f fs_name -m <mountpoint>
On Linux X9000 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 Management Console
or file serving node hosting the active agile management console:
ibrix_server -m
6.
On the node hosting the passive agile management console, move the console back to passive
mode:
ibrix_fm -m passive
The X9000 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
Remotely 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:
<installdirectory>/bin/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 X9000 HA is enabled. See
(page 21)
and
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:
54
Maintaining the system
"Identifying standbys for file serving nodes" (page
"Cluster high availability" (page 25)
"Manually failing over a file serving node" (page
"Configuring virtual interfaces for client access"
for more information about creating standby
26)), and then manually fail
28)).
Hide quick links:
Advertisement
Table of Contents
Troubleshooting
