Repository :
http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
---------------------------------------------------------------
commit f6ecc1ea229702f4390b23c31f413e732238621e
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Wed Sep 3 21:56:21 2014 +0200
Improve Channel bonding using ifcfg
after jklimes review.
---------------------------------------------------------------
en-US/Configure_Network_Bonding.xml | 14 +++++++++-----
1 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/en-US/Configure_Network_Bonding.xml b/en-US/Configure_Network_Bonding.xml
index 2c13a25..d3e82ba 100644
--- a/en-US/Configure_Network_Bonding.xml
+++ b/en-US/Configure_Network_Bonding.xml
@@ -352,20 +352,24 @@ See the <filename>modprobe(8)</filename> man page for
more command options.
To create a channel bonding interface, create a file in the <filename
class="directory">/etc/sysconfig/network-scripts/</filename> directory
called
<filename>ifcfg-bond<replaceable>N</replaceable></filename>,
replacing <replaceable>N</replaceable> with the number for the interface, such
as <filename>0</filename>.
</para>
<para>
- The contents of the file can be identical to whatever type of interface is
getting bonded, such as an Ethernet interface. The only difference is that the
<option>DEVICE</option> directive is
<option>bond<replaceable>N</replaceable></option>, replacing
<replaceable>N</replaceable> with the number for the interface. The
<option>NM_CONTROLLED</option> directive can be added to prevent
<application>NetworkManager</application> from configuring this device.
- </para>
- <para>
- The following is a sample channel bonding configuration file:
+ The contents of the file can be based on a configuration file for whatever type
of interface is getting bonded, such as an Ethernet interface. The essential differences
are that the <option>DEVICE</option> directive is
<option>bond<replaceable>N</replaceable></option>, replacing
<replaceable>N</replaceable> with the number for the interface, and TYPE=Bond.
The <option>NM_CONTROLLED</option> directive can be added to prevent
<application>NetworkManager</application> from configuring this device.
</para>
+
<example id="ex-Example_ifcfg-bond0_Interface_Configuration_File">
<title>Example ifcfg-bond0 Interface Configuration File</title>
+ <para>
+ An example of a channel bonding interface.
+ </para>
<programlisting>DEVICE=bond0
+NAME=bond0
+TYPE=Bond
IPADDR=192.168.1.1
NETMASK=255.255.255.0
ONBOOT=yes
BOOTPROTO=none
-NM_CONTROLLED=no
BONDING_OPTS="<replaceable>bonding parameters separated by
spaces</replaceable>"</programlisting>
+<para>
+The NAME directive is useful for naming the connection profile in
<application>NetworkManager</application>. ONBOOT says whether the profile
should be started when booting (or more generally, when auto-connecting a
device).</para>
</example>
<important>
<title>Put all Bonding Module Parameters in ifcfg-bondN
Files</title>