6.0 HP X9320 Network Storage System Administrator Guide (AW542-96009, December 2011)

1. The management console verifies that the standby is powered on and accessible.
2. The management console migrates ownership of the node’s segments to the standby and
notifies all file serving nodes and X9000 clients about the migration. This is a persistent change.
3. If network interface monitoring has been set up, the management console activates the standby
user network interface and transfers the IP address of the node’s user network interface to it.
To determine the progress of a failover, view the Status tab on the GUI or execute the
ibrix_server -l command. While the management console is migrating segment ownership,
the operational status of the node is Up-InFailover or Down-InFailover, depending on whether the
node was powered up or down when failover was initiated. When failover is complete, the
operational status changes to Up-FailedOver or Down-FailedOver. For more information about
operational states, see “Monitoring the status of file serving nodes” (page 50).
Both automated and manual failovers trigger an event that is reported on the GUI.
Setting up automated failover
The recommended minimum setup for automated failover protection is as follows:
1. Configure file serving nodes in standby pairs.
2. Identify power sources for file serving nodes.
3. Turn on automated failover.
If your cluster includes one or more user network interfaces carrying NFS/CIFS client traffic, HP
recommends that you identify standby network interfaces and set up network interface monitoring.
If your file serving nodes are connected to storage via HBAs, HP recommends that you set up HBA
monitoring.
Configuring standby pairs
File serving nodes can be configured in standby pairs, where each server in a pair is the standby
for the other. The following restrictions apply:
• The management console must have access to both the primary server and its standby.
• The same file system must be mounted on both the primary server and its standby.
• A server identified as a standby must be able to see all segments that might fail over to it.
• In a SAN environment, a primary server and its standby must use the same storage infrastructure
to access a segment’s physical volumes (for example, a multiported RAID array).
To identify a standby for a file serving node, use the following command:
<installdirectory>/bin/ibrix_server -b -h HOSTNAME1,HOSTNAME2
For example, to identify node s2.hp.com as the standby for node s1.hp.com:
<installdirectory>/bin/ibrix_server -b -h s1.hp.com,s2.hp.com
Identifying power sources
To implement automated failover, perform a forced manual failover, or remotely power a file
serving node up or down, you must set up programmable power sources for the nodes and their
standbys. Using programmable power sources prevents a “split-brain scenario” between a failing
file serving node and its standby, allowing the failing server to be centrally powered down by the
management console in the case of automated failover, and manually in the case of a forced
manual failover.
X9000 Software works with iLO, IPMI, OpenIPMI, and OpenIPMI2 integrated power sources.
Cluster high availability 29