6.2 HP IBRIX 9000 Storage Network Best Practices Guide (TA768-96069, December 2012)

Example FSN failover
The following example illustrates what occurs when a file serving node is forced to fail over. The
example shows an IBRIX 9730 platform in a unified network topology. All IP addresses and other
identifiers have been chosen for illustration purposes and could be different on a customer
installation.
In this example, the cluster starts with two active file serving nodes. FSN 1 has the active Fusion
Manager and is serving files from IP address 10.30.214.202. FSN 2 is serving files from IP address
10.30.214.203. Figure 4 illustrates the initial state of this cluster. The interfaces in bold (bond
0) are active on the FSN, while the other interfaces are the standby interfaces that have been put
in place for failover.
Figure 4 FSN failover example start state
Initially, FSN 1 has three active interfaces and one standby interface:
bond0 is the cluster network interface
bond0:0 is a cluster network VIF for the active Fusion Manager
bond0:2 is a user network VIF for file serving from FSN 1
bond0:3 is not active, but has been provisioned for failover of file serving duties from
nl
FSN 2
Initially, FSN 2 has two active interfaces and two standby interfaces:
bond0 is the cluster network interface
bond0:0 is not active, but has been provisioned to support Fusion Manager failover.
bond0:2 is a user network VIF for file serving from FSN 2
bond0:3 is not active, but is n provisioned for failover of file serving duties from FSN 1
The ibrix_nic command displays the cluster-wide configuration of the network. Before failing
over FSN1, the output would be similar to the following:
To see how this maps onto each FSN, check the output of the Linux ifconfig command for each
FSN. The ifconfig output shows only the active interfaces. VIFs and failover are handled at the
IBRIX solution layer, which dynamically creates and removes the necessary interfaces on the FSNs
to react to conditions that cause failover.
User VIF failover 13