Configuring Vlan Tagging - HP StoreAll Series Installation Manual

HTTP. While creating a virtual host from the Create Vhost screen or with the
ibrix_httpvhost command, specify the VIF as the IP address that clients should use to
access shares associated with the Vhost.
HP StoreAll clients. Use the following command to prefer the appropriate user network. Execute
the command once for each destination host that the client should contact using the specified
interface.
ibrix_client -n -h SRCHOST -A DESTNOST/IFNAME
For example:
ibrix_client -n -h client12.mycompany.com -A
ib50-81.mycompany.com/bond1
NOTE:
StoreAll clients, add one or more user network interfaces to ensure that HA and client
communication work together.

Configuring VLAN tagging

VLAN capabilities provide hardware support for running multiple logical networks over the same
physical networking hardware. To allow multiple packets for different VLANs to traverse the same
physical interface, each packet must have a field added that contains the VLAN tag. The tag is a
small integer number that identifies the VLAN to which the packet belongs. When an intermediate
switch receives a "tagged" packet, it can make the appropriate forwarding decisions based on
the value of the tag.
If configured properly, HP StoreAll systems support VLAN tags being transferred to the node network
interfaces. The ability of nodes to handle VLAN tags natively in this manner makes it possible for
the nodes to support multiple VLAN connections simultaneously over a single bonded interface.
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 initial bond created
by HP StoreAll has a VLAN tag of 30, it is then labeled bond0.30.
You can also 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 is labelled,
bond0.30:2.
The following commands show configuring for a bonded VIF and backup nodes for a flat network
topology using the 10.10.x.y subnet. VLAN tagging is configured for hosts ib142-129 and
ib142-131 on the 51 subnet.
Add the bond0.51 interface with the VLAN tag:
# ibrix_nic -a -n bond0.51 -h ib142-129
# ibrix_nic -a -n bond0.51 -h ib142-131
Assign an IP address to the bond0:51 VIFs on each node:
# ibrix_nic -c -n bond0.51 -h ib142-129 -I 192.168.51.101 -M 255.255.255.0
# ibrix_nic -c -n bond0.51 -h ib142-131 -I 192.168.51.102 -M 255.255.255.0
Add the bond0.51:2 VIF on top of the interface:
# ibrix_nic -a -n bond0.51:2 -h ib142-131
# ibrix_nic -a -n bond0.51:2 -h ib142-129
Configure backup nodes:
# ibrix_nic -b -H ib142-129/bond0.51,ib142-131/bond0.51:2
# ibrix_nic -b -H ib142-131/bond0.51,ib142-129/bond0.51:2
Create the user FM VIF:
ibrix_fm -c 192.168.51.125 -d bond0.51:1 -n 255.255.255.0 -v user
Because the backup NIC cannot be used as a preferred network interface for HP
Configuring VLAN tagging 147