6.3 HP StoreAll 9300/9320 Storage Administrator Guide (AW549-96072, June 2013)

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 StoreAll 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.
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 adds the WWPN for the port to the configuration
database.
ibrix_hba -a [-h HOSTLIST]
Adding standby-paired HBA ports
Identifying standby-paired HBA ports to the configuration database allows the Fusion Manager to
apply the following logic when they fail:
• If one port in a pair fails, do nothing. Traffic will automatically switch to the surviving port, as
configured by the HBA vendor or the software.
• If both ports in a pair fail, fail over the server’s segments to the standby server.
Use the following command to identify two HBA ports as a standby pair:
ibrix_hba -b -P WWPN1:WWPN2 -h HOSTNAME
Enter the WWPN as decimal-delimited pairs of hexadecimal digits. The following command
identifies port 20.00.12.34.56.78.9a.bc as the standby for port 42.00.12.34.56.78.9a.bc for
the HBA on file serving node s1.hp.com:
ibrix_hba -b -P 20.00.12.34.56.78.9a.bc:42.00.12.34.56.78.9a.bc -h s1.hp.com
Turning HBA monitoring on or off
If your cluster uses single-port HBAs, turn on monitoring for all of the ports to set up automated
failover in the event of HBA failure. Use the following command:
ibrix_hba -m -h HOSTNAME -p PORT
64 Configuring failover