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

When operating normally, FSN 1 has four active interfaces and two standby interfaces:
VIFVLANFunctionActiveNetworkInterfaces
NoYes (VLAN Tag 20)Cluster Network Interface for FSN
1
YesClusterbond0.20
Yes (Base: bond0.20)Yes (VLAN Tag 20)Fusion ManagerYesClusterbond0.20:0
NoYes (VLAN Tag 30)File Serving on VLAN 30 from
FSN 1
YesUser 1bond0.30
Yes (Base: bond0.30)Yes (VLAN Tag 30)Failover for File Serving on VLAN
30 from FSN 2
NoUser 1bond0.30:2
NoYes (VLAN Tag 40)File Serving on VLAN 40 from
FSN 1
YesUser 2bond0.40
Yes (Base: bond0.40Yes (VLAN Tag 40)Failover for File Serving on VLAN
40 from FSN 2
NoUser 2bond0.40:2
FSN 2 has three active interfaces and three standby interfaces:
VIFVLANFunctionActiveNetworkInterfaces
NoYes (VLAN Tag 20)Cluster Network Interface for
FSN 1
YesClusterbond0.20
Yes (Base: bond0.20)Yes (VLAN Tag 20)Fusion Manager FailoverNoClusterbond0.20:0
NoYes (VLAN Tag 30)File Serving on VLAN 30 from
FSN 2
YesUser 1bond0.30
Yes (Base: bond0.30)Yes (VLAN Tag 30)Failover for File Serving on
VLAN 30 from FSN 1
NoUser 1bond0.30:2
NoYes (VLAN Tag 40)File Serving on VLAN 40 from
FSN 2
YesUser 2bond0.40
Yes (Base: bond0.40Yes (VLAN Tag 40)Failover for File Serving on
VLAN 40 from FSN 1
NoUser 2bond0.40:2
The ibrix_nic command displays the cluster-wide configuration of the network. For this
configuration, the output would be similar to:
To see how this maps onto each FSN, check the output from 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.
22 Overview of HP IBRIX 9000 Series networking