The failed-over management console remains in maintenance mode until it is moved to passive
mode using the following command:
ibrix_fm -m passive
A management console cannot be moved from maintenance mode to active mode.
Viewing information about management consoles
To view mode information, use the following command:
ibrix_fm –i
NOTE:
If the management console was not installed in an agile configuration, the output will
report
FusionServer: fusion manager name not set! (active, quorum is not
configured)
.
When a management console is installed, it is registered in the management console configuration.
To view a list of all registered management consoles, use the following command:
ibrix_fm –f
Cluster high availability
X9000 Software High Availability 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: the default manual failover and the optional automated
failover. A manual failover uses the
ibrix_server
command or the management console 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 management console 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 via an HBA.
When automated failover is enabled, the management console listens for heartbeat messages that
the file serving nodes broadcast at one-minute intervals. The management console 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 management console
receives a heartbeat message indicating that a monitored network might be down and then the
console cannot reach that interface.
If a file serving node fails over, you will need to manually fail back the node.
What happens during a failover
The following events occur during automated or manual failover of a file serving node to its standby:
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.
Cluster high availability
25
