HP StoreAll Storage Network Best Practices Guide

Linux networking tools such as ifconfig display a network interface with an associated VLAN
tag using a device label with the form bond#.<VLAN_id>. For example, if the first bond created
by StoreAll has a VLAN tag of 30, it will be labeled bond0.30.
It is also possible to add a VIF on top of an interface that has an associated VLAN tag. In this case,
the device label of the interface takes the form bond#.<VLAN_id>.<VVIF_label>. For example,
if a VIF with a label of 2 is added for the bond0.30 interface, the new interface device label will
be bond0.30:2.
Cluster/user/management network support
The StoreAll platform supports the use of VLAN tagging on the cluster and user networks. The
management network does not currently support VLAN tagging because some of the embedded
components that could potentially be attached to the management network do not have support
for VLAN tagging.
When operating in the flat network topology with VLAN tagging enabled on the cluster network,
it is the responsibility of the customer route between the cluster/user subnet and the management
subnet to perform the necessary stripping or addition of VLAN tags for packets traversing between
a node and a management component.
VLAN tagging example
The following example shows the network setup for an StoreAll 9730 platform in a flat network
topology, operating with two user VLANs; however, the principal configuration is the same for all
StoreAll Storage platforms. StoreAll nodes 1 and 2 have been configured to serve files to VLAN
30 and VLAN 40. StoreAll node 1 is serving files from IP Address 172.16.116.230 on VLAN 30,
and from IP address 172.16.117.231 on VLAN 40. StoreAll node 2 is serving files from IP address
172.16.116.231 on VLAN 30, and from IP address 172.16.117.230 on VLAN 40.
Figure 7 (page 23) shows the configuration of the interfaces on the two nodes, which are set up
as a failover pair. The interfaces in bold (bond 0) are active on the node; the other interfaces are
standbys put in place for failover. All IP addresses and other identifiers have been chosen for
illustration purposes and could be different on a customer installation.
Figure 7 StoreAll node with VLAN tagging
In Figure 7 (page 23):
• StoreAll node 1 is servicing file client requests to 172.16.116.230–vlan tag 30 (StoreAll node
1–bond0.30).
• StoreAll node 1 is servicing file client requests to 172.16.117.231–vlan tag 40 (StoreAll node
1–bond0.40).
• StoreAll node 2 is servicing file client requests to 172.16.116.231–vlan tag 30 (StoreAll node
2–bond0.30).
• StoreAll node 2 is servicing file client requests to 172.16.117.230–vlan tag 40 (StoreAll node
2–bond0.40).
• Fusion Manager is active on StoreAll node 1, accepting requests to 172.16.115.166–vlan
tag 20 (StoreAll node 1–bond20:0.
StoreAll node customer integration features 23