Identifying standbys
To protect a network interface, you must identify a standby for it on each file serving node that
connects to the interface. The following restrictions apply when identifying a standby network
interface:
•
The standby network interface must be unconfigured and connected to the same switch (network)
as the primary interface.
•
The file serving node that supports the standby network interface must have access to the file
system that the clients on that interface will mount.
Virtual interfaces are highly recommended for handling user network interface failovers. If a VIF
user network interface is teamed/bonded, failover occurs only if all teamed network interfaces
fail. Otherwise, traffic switches to the surviving teamed network interfaces.
To identify standbys for a network interface, execute the following command once for each file
serving node.
IFNAME1
is the network interface that you want to protect and
IFNAME2
is the
standby interface.
<installdirectory>/bin/ibrix_nic -b -H HOSTNAME1/IFNAME1,HOSTNAME2/IFNAME2
The following command identifies virtual interface
eth2:2
on file serving node s2.hp.com as the
standby interface for interface
eth2
on file serving node s1.hp.com:
<installdirectory>/bin/ibrix_nic -b -H s1.hp.com/eth2,s2.hp.com/eth2:2
Setting up a monitor
File serving node failover pairs can be identified as network interface monitors for each other.
Because the monitoring must be declared in both directions, this is a two-pass process for each
failover pair.
To set up a network interface monitor, use the following command:
<installdirectory>/bin/ibrix_nic -m -h MONHOST -A DESTHOST/IFNAME
For example, to set up file serving node s2.hp.com to monitor file serving node s1.hp.com over
user network interface
eth1
:
<installdirectory>/bin/ibrix_nic -m -h s2.hp.com -A s1.hp.com/eth1
To delete network interface monitoring, use the following command:
<installdirectory>/bin/ibrix_nic -m -h MONHOST -D DESTHOST/IFNAME
30
Configuring failover
