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 BACKUP STATE HA ID GROUP
----------- ------- ------------ --- ------------------------------------ -----
ib50-81 ib50-82 Up on 132cf61a-d25b-40f8-890e-e97363ae0d0b servers
ib50-82 ib50-81 Up on 7d258451-4455-484d-bf80-75c94d17121d servers
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 TYPE STATE IP_ADDRESS BACKUP_HOST BACKUP_IF
------- ------ ------- ------------------- ------------- ----------- ---------
ib50-81 bond1:1 User Up, LinkUp 16.226.50.220 ib50-82 bond1:1
ib50-81 bond0 Cluster Up, LinkUp 172.16.0.81
ib50-81 bond1:2 User Inactive, Standby
ib50-81 bond1 User Up, LinkUp 16.226.50.81
ib50-82 bond0 Cluster Up, LinkUp 172.16.0.82
ib50-82 bond1 User Up, LinkUp 16.226.50.82
ib50-82 bond1:2 User Inactive, Standby
ib50-82 bond1:1 User Up, LinkUp 16.226.50.228 ib50-81 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
Содержание StorageWorks X9320
Страница 97: ...13 When the Configure Network dialog box reappears select bond0 Configuring a file serving node manually 97 ...
Страница 108: ...Cabling diagrams Cluster network cabling diagram 108 System component and cabling diagrams ...
Страница 109: ...SATA option cabling Description Line SAS I O pathController A SAS I O pathController B Cabling diagrams 109 ...
Страница 144: ...English notice Estonian notice Finnish notice French notice 144 Regulatory compliance and safety ...
Страница 145: ...German notice Greek notice Hungarian notice Italian notice Waste Electrical and Electronic Equipment directive 145 ...
Страница 146: ...Latvian notice Lithuanian notice Polish notice Portuguese notice 146 Regulatory compliance and safety ...
Страница 147: ...Slovakian notice Slovenian notice Spanish notice Swedish notice Waste Electrical and Electronic Equipment directive 147 ...