Setting Up Hba Monitoring; Discovering Hbas - HP IBRIX X9720 System Administrator Manual

ibrix_nic -m -h MONHOST -D DESTHOST/IFNAME
Deleting standbys
To delete a standby for a network interface, use the following command:
ibrix_nic -b -U HOSTNAME1/IFNAME1
For example, to delete the standby that was assigned to interface eth2 on file serving node
s1.hp.com:
ibrix_nic -b -U s1.hp.com/eth2

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 X9000 software does
not play a role in vendor- or software-mediated HBA failover—traffic moves to the remaining
functional port without any 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 X9000 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 (see
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 (see
on HBA monitoring for all paired ports (see
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.
When both HBA monitoring and automated failover for file serving nodes are configured, the
Fusion Manager will fail over a server in two situations:
Both ports in a monitored set of standby-paired ports fail. Because all standby pairs were
identified in the configuration database, the Fusion Manager knows that failover is required
only when both ports fail.
A monitored single-port HBA fails. Because no standby has been identified for the failed port,
the Fusion Manager knows to initiate failover immediately.

Discovering HBAs

You must discover HBAs before you set up HBA monitoring, when you replace an HBA, and when
you add a new HBA to the cluster. Discovery informs the configuration database of a port's WWPN
only. You must identify ports that are teamed as standby pairs using the following command:
ibrix_hba -a [-h HOSTLIST]
"Turning HBA monitoring on or off" (page
"Identifying standby-paired HBA ports" (page
"Turning HBA monitoring on or off" (page
44)).
44), and then turn
44)).
Cluster high availability 43