-<?xml version='1.0' encoding='UTF-8'?>
-<!-- This document was created with Syntext Serna Free. --><chapter xmlns="http://docbook.org/ns/docbook" xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en-US" xml:id="settingupbonding">
+<?xml version='1.0' encoding='UTF-8'?><chapter xmlns="http://docbook.org/ns/docbook" xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en-US" xml:id="settingupbonding">
<title xml:id="settingupbonding.title">Setting Up Network Interface Bonding</title>
<para>This chapter describes how to use multiple network interfaces in parallel to increase bandwidth and/or redundancy. Topics include:</para>
<itemizedlist>
<section xml:id="dbdoclet.50438258_95824">
<title>Network Interface Bonding Overview</title>
<para>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.</para>
- <para>Several different types of bonding are available in Linux. All these types are referred to as 'modes', and use the bonding kernel module.</para>
+ <para>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.</para>
<para>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.'</para>
</section>
<section xml:id="dbdoclet.50438258_29107">
<section xml:id="dbdoclet.50438258_25353">
<title>Bonding Module Parameters</title>
<para>Bonding module parameters control various aspects of bonding.</para>
- <para>Outgoing traffic is mapped across the slave interfaces according to the transmit hash policy. For Lustre, we recommend that you set the <literal>xmit_hash_policy</literal> 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.</para>
+ <para>Outgoing traffic is mapped across the slave interfaces according to the transmit hash
+ policy. We recommend that you set the <literal>xmit_hash_policy</literal> 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.</para>
<screen>$ xmit_hash_policy=layer3+4</screen>
- <para>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:</para>
+ <para>The <literal>miimon</literal> 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:</para>
<screen>$ miimon=100</screen>
<para>For a busy network, increase the timeout.</para>
</section>
<para>To set up bonding:</para>
<orderedlist>
<listitem>
- <para>Create a virtual 'bond' interface by creating a configuration file in:</para>
- <screen>/etc/sysconfig/network-scripts/ # vi /etc/sysconfig/ network-scripts/ifcfg-\
-bond0</screen>
+ <para>Create a virtual 'bond' interface by creating a configuration file:</para>
+ <screen># vi /etc/sysconfig/network-scripts/ifcfg-bond0</screen>
</listitem>
<listitem>
<para>Append the following lines to the file.</para>
</orderedlist>
</listitem>
<listitem>
- <para>Set up the bond interface and its options in /etc/modprobe.conf. Start the slave interfaces by your normal network method.</para>
- <screen># vi /etc/modprobe.conf
+ <para>Set up the bond interface and its options in <literal>/etc/modprobe.d/bond.conf</literal>. Start the slave interfaces by your normal network method.</para>
+ <screen># vi /etc/modprobe.d/bond.conf
</screen>
<orderedlist>
<listitem>
<listitem>
<para>Start/restart the slave interfaces (using your normal network method).</para>
<note>
- <para>You must <literal>modprobe</literal> the bonding module for each bonded interface. If you wish to create bond0 and bond1, two entries in <literal>modprobe.conf</literal> are required.</para>
+ <para>You must <literal>modprobe</literal> the bonding module for each bonded interface. If you wish to create bond0 and bond1, two entries in <literal>bond.conf</literal> file are required.</para>
</note>
- <para>The examples below are from RedHat systems. For setup use: <literal>/etc/sysconfig/networking-scripts/ifcfg-*</literal> 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.</para>
+ <para>The examples below are from systems running Red Hat Enterprise Linux. For setup use:
+ <literal>/etc/sysconfig/networking-scripts/ifcfg-*</literal> 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.</para>
<para><link xl:href="http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding">http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding</link></para>
</listitem>
<listitem>
</orderedlist>
<section remap="h3">
<title>Examples</title>
- <para>This is an example showing <literal>modprobe.conf</literal> entries for bonding Ethernet interfaces <literal>eth1</literal> and <literal>eth2</literal> to <literal>bond0</literal>:</para>
- <screen># cat /etc/modprobe.conf
+ <para>This is an example showing <literal>bond.conf</literal> entries for bonding Ethernet interfaces <literal>eth1</literal> and <literal>eth2</literal> to <literal>bond0</literal>:</para>
+ <screen># 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
</section>
</section>
<section xml:id="dbdoclet.50438258_54769">
- <title>Configuring Lustre with Bonding</title>
- <para>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.</para>
+ <title>Configuring a Lustre File System with Bonding</title>
+ <para>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 <literal>bond0</literal> using the Lustre <literal>networks</literal> parameter in
+ <literal>/etc/modprobe</literal>.</para>
<screen>options lnet networks=tcp(bond0)</screen>
</section>
<section xml:id="dbdoclet.50438258_92244">
<para>We recommend the following bonding references:</para>
<itemizedlist>
<listitem>
- <para>In the Linux kernel source tree, see documentation/networking/bonding.txt</para>
+ <para>In the Linux kernel source tree, see
+ <literal>documentation/networking/bonding.txt</literal></para>
</listitem>
<listitem>
- <para><link xl:href="http://linux-ip.net/html/ether-bonding.html">http://linux-ip.net/html/ether-bonding.html</link></para>
+ <para><link xl:href="http://linux-ip.net/html/ether-bonding.html"
+ >http://linux-ip.net/html/ether-bonding.html</link>.</para>
</listitem>
<listitem>
- <para><link xl:href="http://www.sourceforge.net/projects/bonding">http://www.sourceforge.net/projects/bonding</link></para>
+ <para><link xl:href="http://www.sourceforge.net/projects/bonding"
+ >http://www.sourceforge.net/projects/bonding</link>.</para>
</listitem>
<listitem>
- <para>Linux Foundation bonding website: <link xl:href="http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding">http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding</link></para>
+ <para>Linux Foundation bonding website: <link
+ xl:href="http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding"
+ >http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding</link>. 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.</para>
</listitem>
</itemizedlist>
- <para>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.</para>
</section>
</chapter>
git://git.whamcloud.com / doc / manual.git / blobdiff