[networking-guide] master: Creating SLAVE Interfaces (57a536d)

[stephenw at fedoraproject.org]

Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git

On branch  : master

>---------------------------------------------------------------

commit 57a536d5836f6d88d8edd1b8a1e493b5cd40fb30
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Wed Sep 3 21:50:16 2014 +0200

    Creating SLAVE Interfaces
    
    was "Creating MASTER and SLAVE Interfaces"
    but the "channel bonding interface" is the master.


>---------------------------------------------------------------

 en-US/Configure_Network_Bonding.xml |   19 ++++++++++++-------
 1 files changed, 12 insertions(+), 7 deletions(-)

diff --git a/en-US/Configure_Network_Bonding.xml b/en-US/Configure_Network_Bonding.xml
index 7d17c93..f7b2935 100644
--- a/en-US/Configure_Network_Bonding.xml
+++ b/en-US/Configure_Network_Bonding.xml
@@ -376,24 +376,29 @@ BONDING_OPTS="<replaceable>bonding parameters separated by spaces</replaceable>"
 
  </section>
 
-   <section id="sec-Creating_MASTER_and_SLAVE_Interfaces">
-   <title>Creating MASTER and SLAVE Interfaces</title>
+   <section id="sec-Creating_SLAVE_Interfaces">
+   <title>Creating SLAVE Interfaces</title>
        <para>
-        After the channel bonding interface is created, the network interfaces to be bound together must be configured by adding the <option>MASTER</option> and <option>SLAVE</option> directives to their configuration files. The configuration files for each of the channel-bonded interfaces can be nearly identical.
+        The channel bonding interface is the <quote>master</quote> and the interfaces to be bonded are referred to as the <quote>slaves</quote>. After the channel bonding interface is created, the network interfaces to be bound together must be configured by adding the <option>MASTER</option> and <option>SLAVE</option> directives to the configuration files of the slaves. The configuration files for each of the slave interfaces can be nearly identical.
       </para>
+            <example id="ex-Example_Slave_Interface_Configuration_File">
+        <title>Example Slave Interface Configuration File</title>
 
   <para>
-        For example, if two Ethernet interfaces are being channel bonded, both <systemitem class="etheraddress">eth0</systemitem> and <systemitem class="etheraddress">eth1</systemitem> may look like the following example:
+        For example, if two Ethernet interfaces are being channel bonded, <literal>eth0</literal> and <literal>eth1</literal>, they can both look like the following example:
       </para>
       <programlisting>DEVICE=eth<replaceable>N</replaceable>
+NAME=bond0-slave
+TYPE=Ethernet
 BOOTPROTO=none
 ONBOOT=yes
 MASTER=bond0
-SLAVE=yes
-NM_CONTROLLED=no</programlisting>
+SLAVE=yes</programlisting>
       <para>
-        In this example, replace <replaceable>N</replaceable> with the numerical value for the interface.
+        In this example, replace <replaceable>N</replaceable> with the numerical value for the interface. Note that if more than one profile or configuration file exists with ONBOOT=yes for an interface, they may race with each other and a plain TYPE=Ethernet profile may be activated instead of a bond slave.
       </para>
+      </example>
+ </section>
 
  </section>