HP StoreAll Storage Network Best Practices Guide

When operating normally, StoreAll node 1 has four active interfaces and two standby interfaces:
VIFVLANFunctionActiveNetworkInterfaces
NoYes (VLAN Tag 20)Cluster Network Interface for
node 1
YesClusterbond0.20
Yes (Base: bond0.20)Yes (VLAN Tag 20)Fusion ManagerYesClusterbond0.20:0
NoYes (VLAN Tag 30)File Services on VLAN 30 from
node 1
YesUser 1bond0.30
Yes (Base: bond0.30)Yes (VLAN Tag 30)Failover for File Services on
VLAN 30 from node 2
NoUser 1bond0.30:2
NoYes (VLAN Tag 40)File Services on VLAN 40 from
node 1
YesUser 2bond0.40
Yes (Base: bond0.40Yes (VLAN Tag 40)Failover for File Services on
VLAN 40 from node 2
NoUser 2bond0.40:2
StoreAll node 2 has three active interfaces and three standby interfaces:
VIFVLANFunctionActiveNetworkInterfaces
NoYes (VLAN Tag 20)Cluster Network Interface for
node 1
YesClusterbond0.20
Yes (Base: bond0.20)Yes (VLAN Tag 20)Fusion Manager FailoverNoClusterbond0.20:0
NoYes (VLAN Tag 30)File Services on VLAN 30 from
node 2
YesUser 1bond0.30
Yes (Base: bond0.30)Yes (VLAN Tag 30)Failover for File Services on
VLAN 30 from node 1
NoUser 1bond0.30:2
NoYes (VLAN Tag 40)File Services on VLAN 40 from
node 2
YesUser 2bond0.40
Yes (Base: bond0.40)Yes (VLAN Tag 40)Failover for File Services on
VLAN 40 from node 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 node, check the output from the Linux ifconfig command for
each node. The ifconfig output shows only the active interfaces. VIFs and failover are handled
at the StoreAll solution layer, which dynamically creates and removes the necessary interfaces on
the nodes to react to conditions that cause failover.
24 Overview of HP StoreAll Storage networking