X-Git-Url: https://git.whamcloud.com/?a=blobdiff_plain;f=SettingUpBonding.xml;h=1cab0828608d1cfcff9b2bdf3da467632158030e;hb=e835f8ffc92b2b9af8b3ff52854d71214d8c0312;hp=6c082667712deb94938e9aa4eace708c0a68d2ae;hpb=0bf7f3688379b38453ea990df0c4e9ae420e49f0;p=doc%2Fmanual.git diff --git a/SettingUpBonding.xml b/SettingUpBonding.xml index 6c08266..1cab082 100644 --- a/SettingUpBonding.xml +++ b/SettingUpBonding.xml @@ -1,5 +1,4 @@ - - + Setting Up Network Interface Bonding This chapter describes how to use multiple network interfaces in parallel to increase bandwidth and/or redundancy. Topics include: @@ -40,7 +39,8 @@
Network Interface Bonding Overview Bonding, also known as link aggregation, trunking and port trunking, is a method of aggregating multiple physical network links into a single logical link for increased bandwidth. - Several different types of bonding are available in Linux. All these types are referred to as 'modes', and use the bonding kernel module. + Several different types of bonding are available in the Linux distribution. All these + types are referred to as 'modes', and use the bonding kernel module. Modes 0 to 3 allow load balancing and fault tolerance by using multiple interfaces. Mode 4 aggregates a group of interfaces into a single virtual interface where all members of the group share the same speed and duplex settings. This mode is described under IEEE spec 802.3ad, and it is referred to as either 'mode 4' or '802.3ad.'
@@ -100,9 +100,16 @@ Settings for eth1:
Bonding Module Parameters Bonding module parameters control various aspects of bonding. - Outgoing traffic is mapped across the slave interfaces according to the transmit hash policy. For Lustre, we recommend that you set the xmit_hash_policy option to the layer3+4 option for bonding. This policy uses upper layer protocol information if available to generate the hash. This allows traffic to a particular network peer to span multiple slaves, although a single connection does not span multiple slaves. + Outgoing traffic is mapped across the slave interfaces according to the transmit hash + policy. We recommend that you set the xmit_hash_policy option to the + layer3+4 option for bonding. This policy uses upper layer protocol information if available to + generate the hash. This allows traffic to a particular network peer to span multiple slaves, + although a single connection does not span multiple slaves. $ xmit_hash_policy=layer3+4 - The miimon option enables users to monitor the link status. (The parameter is a time interval in milliseconds.) It makes an interface failure transparent to avoid serious network degradation during link failures. A reasonable default setting is 100 milliseconds; run: + The miimon option enables users to monitor the link status. (The + parameter is a time interval in milliseconds.) It makes an interface failure transparent to + avoid serious network degradation during link failures. A reasonable default setting is 100 + milliseconds; run: $ miimon=100 For a busy network, increase the timeout.
@@ -111,9 +118,8 @@ Settings for eth1: To set up bonding: - Create a virtual 'bond' interface by creating a configuration file in: - /etc/sysconfig/network-scripts/ # vi /etc/sysconfig/ network-scripts/ifcfg-\ -bond0 + Create a virtual 'bond' interface by creating a configuration file: + # vi /etc/sysconfig/network-scripts/ifcfg-bond0 Append the following lines to the file. @@ -158,8 +164,8 @@ BOOTPROTO=none - Set up the bond interface and its options in /etc/modprobe.conf. Start the slave interfaces by your normal network method. - # vi /etc/modprobe.conf + Set up the bond interface and its options in /etc/modprobe.d/bond.conf. Start the slave interfaces by your normal network method. + # vi /etc/modprobe.d/bond.conf @@ -180,9 +186,13 @@ options bond0 mode=balance-alb miimon=100 Start/restart the slave interfaces (using your normal network method). - You must modprobe the bonding module for each bonded interface. If you wish to create bond0 and bond1, two entries in modprobe.conf are required. + You must modprobe the bonding module for each bonded interface. If you wish to create bond0 and bond1, two entries in bond.conf file are required. - The examples below are from RedHat systems. For setup use: /etc/sysconfig/networking-scripts/ifcfg-* The website referenced below includes detailed instructions for other configuration methods, instructions to use DHCP with bonding, and other setup details. We strongly recommend you use this website. + The examples below are from systems running Red Hat Enterprise Linux. For setup use: + /etc/sysconfig/networking-scripts/ifcfg-* The website referenced + below includes detailed instructions for other configuration methods, instructions to use + DHCP with bonding, and other setup details. We strongly recommend you use this + website. http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding @@ -241,18 +251,12 @@ eth1 Link encap:Ethernet HWaddr 4C:00:10:AC:61:E0
Examples - This is an example showing modprobe.conf entries for bonding Ethernet interfaces eth1 and eth2 to bond0: - # cat /etc/modprobe.conf + This is an example showing bond.conf entries for bonding Ethernet interfaces eth1 and eth2 to bond0: + # cat /etc/modprobe.d/bond.conf alias eth0 8139too -alias scsi_hostadapter sata_via -alias scsi_hostadapter1 usb-storage -alias snd-card-0 snd-via82xx -options snd-card-0 index=0 -options snd-via82xx index=0 +alias eth1 via-rhine alias bond0 bonding options bond0 mode=balance-alb miimon=100 -options lnet networks=tcp -alias eth1 via-rhine # cat /etc/sysconfig/network-scripts/ifcfg-bond0 DEVICE=bond0 @@ -306,8 +310,11 @@ Interrupt:9 Base address:0x1400
- Configuring Lustre with Bonding - Lustre uses the IP address of the bonded interfaces and requires no special configuration. It treats the bonded interface as a regular TCP/IP interface. If needed, specify bond0 using the Lustre networks parameter in /etc/modprobe. + Configuring a Lustre File System with Bonding + The Lustre software uses the IP address of the bonded interfaces and requires no special + configuration. The bonded interface is treated as a regular TCP/IP interface. If needed, + specify bond0 using the Lustre networks parameter in + /etc/modprobe. options lnet networks=tcp(bond0)
@@ -315,18 +322,24 @@ Interrupt:9 Base address:0x1400 We recommend the following bonding references: - In the Linux kernel source tree, see documentation/networking/bonding.txt + In the Linux kernel source tree, see + documentation/networking/bonding.txt - http://linux-ip.net/html/ether-bonding.html + http://linux-ip.net/html/ether-bonding.html. - http://www.sourceforge.net/projects/bonding + http://www.sourceforge.net/projects/bonding. - Linux Foundation bonding website: http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding + Linux Foundation bonding website: http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding. This + is the most extensive reference and we highly recommend it. This website includes + explanations of more complicated setups, including the use of DHCP with bonding. - This is the most extensive reference and we highly recommend it. This website includes explanations of more complicated setups, including the use of DHCP with bonding.