Configuring Nic Failover; Configuring Automated Failover; Example Configuration; Specifying Vifs In The Client Configuration - HP StorageWorks X9320 Administrator's Manual

1. Identify the VIF:
# ibrix_nic –a -n bond1:2 –h node1,node2,node3,node4
2. Set up a standby server for each VIF:
# ibric_nic –b –H node1/bond1:1,node2/bond1:2
# ibric_nic –b –H node2/bond1:1,node1/bond1:2
# ibric_nic –b –H node3/bond1:1,node4/bond1:2
# ibric_nic –b –H node4/bond1:1,node3/bond1:2

Configuring NIC failover

NIC monitoring should be configured on VIFs that will be used by NFS, CIFS, FTP, or HTTP. Use
the same backup pairs that you used when configuring standby servers. For example:
# ibric_nic –m -h node1 -A node2/bond1:1
# ibric_nic –m -h node2 -A node1/bond1:1
# ibric_nic –m -h node3 -A node4/bond1:1
# ibric_nic –m -h node4 -A node3/bond1:1

Configuring automated failover

To enable automated failover for your file serving nodes, execute the following command:
ibrix_server —m [-h SERVERNAME]

Example configuration

This example uses two nodes, ib50-81 and ib50-82. These nodes are backups for each other,
forming a backup pair.
[root@ib50-80 ~]# ibrix_server -l
Segment Servers
===============
SERVER_NAME
-----------
ib50-81
ib50-82
All VIFs on ib50-81 have backup (standby) VIFs on ib50-82. Similarly, all VIFs on ib50-82
have backup (standby) VIFs on ib50-81. NFS, CIFS, FTP, and HTTP clients can connect to bond1:1
on either host. If necessary, the selected server will fail over to bond1:2 on the opposite host.
X9000 clients could connect to bond1 on either host, as these clients do not support or require
NIC failover. (The following sample output shows only the relevant fields.)
[root@ib50-80 ~]# ibrix_nic -l
HOST IFNAME
------- ------
ib50-81 bond1:1
ib50-81 bond0
ib50-81 bond1:2
ib50-81 bond1
ib50-82 bond0
ib50-82 bond1
ib50-82 bond1:2
ib50-82 bond1:1

Specifying VIFs in the client configuration

When you configure your clients, you may need to specify the VIF that should be used for client
access.
NFS/CIFS. Specify the VIF IP address of the servers (for example, bond1:0) to establish connection.
You can also configure DNS round robin to ensure NFS or CIFS client-to-server distribution. In both
cases, the NFS/CIFS clients will cache the initial IP they used to connect to the respective share,
usually until the next reboot.
22 Configuring virtual interfaces for client access
BACKUP STATE
------- ------------
ib50-82 Up
ib50-81 Up
TYPE STATE
------- -------------------
User Up, LinkUp
Cluster Up, LinkUp
User Inactive, Standby
User Up, LinkUp
Cluster Up, LinkUp
User Up, LinkUp
User Inactive, Standby
User Up, LinkUp
HA ID
--- ------------------------------------
on 132cf61a-d25b-40f8-890e-e97363ae0d0b
on 7d258451-4455-484d-bf80-75c94d17121d
IP_ADDRESS
-------------
16.226.50.220
172.16.0.81
16.226.50.81
172.16.0.82
16.226.50.82
16.226.50.228
GROUP
-----
servers
servers
BACKUP_HOST BACKUP_IF
----------- ---------
ib50-82 bond1:1
ib50-81 bond1:1