Failing Back A Server; Setting Up Hba Monitoring - HP IBRIX 9300 Administrator's Manual

ibrix_server -l
The STATE field indicates the status of the failover. If the field persistently shows Down-InFailover
or Up-InFailover, the failover did not complete; contact HP Support for assistance. For
information about the values that can appear in the STATE field, see
failover" (page

Failing back a server

After an automated or manual failover of a server, you must manually fail back the server, which
restores ownership of the failed-over segments and network interfaces to the server. Before failing
back the server, confirm that it can see all of its storage resources and networks. The segments
owned by the server will not be accessible if the server cannot see its storage.
To fail back a node from the GUI, select the node on the Servers panel and then click Failback on
the Summary panel.
On the GUI, select the node on the Servers panel and then click Failback on the Summary pane
On the CLI, run the following command, where HOSTNAME is the failed-over node:
ibrix_server -f -U -h HOSTNAME
After failing back the node, check the Summary panel or run the ibrix_server -l command
to determine whether the failback completed fully. If the failback is not complete, contact HP
Support.
NOTE: A failback might not succeed if the time period between the failover and the failback is
too short, and the primary server has not fully recovered. HP recommends ensuring that both servers
are up and running and then waiting 60 seconds before starting the failback. Use the
ibrix_server -l command to verify that the primary server is up and running. The status should
be Up-FailedOver before performing the failback.

Setting up HBA monitoring

You can configure High Availability to initiate automated failover upon detection of a failed HBA.
HBA monitoring can be set up for either dual-port HBAs with built-in standby switching or single-port
HBAs, whether standalone or paired for standby switching via software. The IBRIX software does
not play a role in vendor- or software-mediated HBA failover; traffic moves to the remaining
functional port with no Fusion Manager involvement.
HBAs use worldwide names for some parameter values. These are either worldwide node names
(WWNN) or worldwide port names (WWPN). The WWPN is the name an HBA presents when
logging in to a SAN fabric. Worldwide names consist of 16 hexadecimal digits grouped in pairs.
In IBRIX software, these are written as dot-separated pairs (for example, 21.00.00.e0.8b.05.05.04).
To set up HBA monitoring, first discover the HBAs, and then perform the procedure that matches
your HBA hardware:
For single-port HBAs without built-in standby switching: Turn on HBA monitoring for all ports
that you want to monitor for failure.
For dual-port HBAs with built-in standby switching and single-port HBAs that have been set
up as standby pairs in a software operation: Identify the standby pairs of ports to the
configuration database and then turn on HBA monitoring for all paired ports. If monitoring is
turned on for just one port in a standby pair and that port fails, the Fusion Manager will fail
over the server even though the HBA has automatically switched traffic to the surviving port.
When monitoring is turned on for both ports, the Fusion Manager initiates failover only when
both ports in a pair fail.
46 Configuring failover
38).
"What happens during a