5.5 HP StorageWorks X9300 Network Storage Gateway Administrator Guide (AW539-96007, March 2011)

<installdirectory>/bin/ibrix_nic -m -h MONHOST -D DESTHOST/IFNAME
Deleting standbys
To delete a standby for a network interface, use the following command:
<installdirectory>/bin/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:
<installdirectory>/bin/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. X9000 Software does not
play any role in vendor- or software-mediated HBA failover—traffic moves to the remaining functional
port without any management console 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 “Turning HBA monitoring on or off” on page 34).
• For dual-port HBAs with built-in standby switching and single-port HBAs that have been set up as
standby pairs via software: Identify the standby pairs of ports to the configuration database (see
“Identifying standby-paired HBA ports” on page 34, and then turn on HBA monitoring for all
paired ports (see “Turning HBA monitoring on or off” on page 34). If monitoring is turned on for
just one port in a standby pair and that port then fails, the management console will fail over the
server even though the HBA has automatically switched traffic to the surviving port. When monit-
oring is turned on for both ports, the management console initiates failover only when both ports
in a pair fail.
When both HBA monitoring and automated failover for file serving nodes are set up, the management
console will fail over a server in two situations:
• Both ports in a monitored set of standby-paired ports fail. Because, during the HBA monitoring
setup, all standby pairs were identified in the configuration database, the management console
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
management console 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 only a port’s
WWPN. You must identify ports that are teamed as standby pairs. Use the following command:
<installdirectory>/bin/ibrix_hba -a [-h HOSTLIST]
X9300 Network Storage Gateway Administrator Guide 33