Viewing Information About Fusion Managers; Cluster High Availability; Failover Modes; What Happens During A Failover - HP IBRIX X9720 System Administrator Manual

The command takes effect immediately.
The failed-over Fusion Manager remains in nofmfailover mode until it is moved to passive mode
using the following command:
ibrix_fm -m passive
NOTE: A Fusion Manager cannot be moved from nofmfailover mode to active mode.

Viewing information about Fusion Managers

To view mode information, use the following command:
ibrix_fm –i
NOTE: If the Fusion Manager was not installed in an agile configuration, the output will report
FusionServer: fusion manager name not set! (active, quorum is not
configured).
When a Fusion Manager is installed, it is registered in the Fusion Manager configuration. To view
a list of all registered management consoles, use the following command:
ibrix_fm –l

Cluster high availability

The High Availability feature keeps your data accessible at all times. Failover protection can be
configured for file serving nodes, network interfaces, individual segments, and HBAs. Through
physical and logical configuration policies, you can set up a flexible and scalable high availability
solution. X9000 clients experience no changes in service and are unaware of the failover events.

Failover modes

High Availability has two failover modes: manual failover (the default) and tautomated failover.
For manual failover, use the ibrix_server command or the GUI to fail over a file serving node
to its standby. The server can be powered down or remain up during the procedure. Manual
failover also includes failover of any network interfaces having defined standbys. You can perform
a manual failover at any time, regardless of whether automated failover is in effect.
Automated failover allows the Fusion Manager to initiate failover when it detects that
standby-protected components have failed. A basic automated failover setup protects all file serving
nodes. A comprehensive setup also includes network interface monitoring to protect user network
interfaces and HBA monitoring to protect access from file serving nodes to storage through an
HBA.
When automated failover is enabled, the Fusion Manager listens for heartbeat messages that the
file serving nodes broadcast at one-minute intervals. The Fusion Manager automatically initiates
failover when it fails to receive five consecutive heartbeats or, if HBA monitoring is enabled, when
a heartbeat message indicates that a monitored HBA or pair of HBAs has failed.
If network interface monitoring is enabled, automated failover occurs when the Fusion Manager
receives a heartbeat message indicating that a monitored network might be down and the Fusion
Manager cannot reach that interface.
If a file serving node fails over, you must fail back the node manually.

What happens during a failover

The following actions occur during automated or manual failover of a file serving node to its
standby:
38 Configuring failover