Configuring High Availability On The Cluster - HP IBRIX 9300 Administrator's Manual

console. This Fusion Manager rebuilds the cluster virtual interface, starts Fusion Manager services
locally, transitions into active mode, and take over Fusion Manager operation.
Failover of the active Fusion Manager affects the following features:
User networks. The virtual interface used by clients will also fail over. Users may notice a brief
reconnect while the newly active Fusion Manager takes over management of the virtual
interface.
GUI. You must reconnect to the Fusion Manager VIF after the failover.
Failing over the Fusion Manager manually
To fail over the active Fusion Manager manually, place the console into nofmfailover mode. Enter
the following command on the node hosting the console:
ibrix_fm -m nofmfailover
The failover will take approximately one minute.
Run to see which node is now the active Fusion Manager, enter the following command:
ibrix_fm –i
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.

Configuring High Availability on the cluster

IBRIX High Availability provides monitoring for servers, NICs, and HBAs.
Server HA. Servers are configured in backup pairs, with each server in the pair acting as a backup
for the other server. The servers in the backup pair must see the same storage. When a server is
failed over, the ownership of its segments and its Fusion Manager services (if the server is hosting
the active FM) move to the backup server.
NIC HA.When server HA is enabled, NIC HA provides additional triggers that cause a server to
fail over to its backup server. For example, you can create a user VIF such as bond0:2 to service
SMB requests on a server and then designate the backup server as a standby NIC for bond0:2.
If an issue occurs with bond0:2 on a server, the server, including its segment ownership and FM
services, will fail over to the backup server, and that server will now handle SMB requests going
through bond0:2.
You can also fail over just the NIC to its standby NIC on the backup server.
HBA monitoring. This method protects server access to storage through an HBA. Most servers ship
with an HBA that has two controllers, providing redundancy by design. Setting up IBRIX HBA
monitoring is not commonly used for these servers. However, if a server has only a single HBA,
you might want to monitor the HBA; then, if the server cannot see its storage because the single
HBA goes offline or faults, the server and its segments will fail over.
You can set up automatic server failover and perform a manual failover if needed. If a server fails
over, you must fail back the server manually.
When automatic HA is enabled, the Fusion Manager listens for heartbeat messages that the servers
broadcast at one-minute intervals. The Fusion Manager initiates a server failover when it fails to
receive five consecutive heartbeats. Failover conditions are detected more quickly when NIC HA
is also enabled; server failover is initiated when the Fusion Manager receives a heartbeat message
indicating that a monitored NIC might be down and the Fusion Manager cannot reach that NIC.
If HBA monitoring is enabled, the Fusion Manager fails over the server when a heartbeat message
indicates that a monitored HBA or pair of HBAs has failed.
Configuring High Availability on the cluster 37