[networking-guide] master: Make new section: Network Bridge with Bond (8676edf)

[stephenw at fedoraproject.org]

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

On branch  : master

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

commit 8676edfb339aaa0c0c372e3798f55d2d2038e466
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Fri Apr 10 17:03:08 2015 +0200

    Make new section: Network Bridge with Bond
    
    it was hard to understand with out section breaks


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

 en-US/Configure_Network_Bridging.xml |   22 +++++++++++++++++++---
 1 files changed, 19 insertions(+), 3 deletions(-)

diff --git a/en-US/Configure_Network_Bridging.xml b/en-US/Configure_Network_Bridging.xml
index 4599718..b24986d 100644
--- a/en-US/Configure_Network_Bridging.xml
+++ b/en-US/Configure_Network_Bridging.xml
@@ -333,6 +333,9 @@ BRIDGE=br0</programlisting>
       <para>
       Restart the networking service in order for the changes to take effect. As <systemitem class="username">root</systemitem> issue the following command:</para>
       <screen>~]#&nbsp;<command>systemctl network restart</command></screen>
+</section>
+      <section id="sec-Network_Bridge_with_Bond">
+      <title>Network Bridge with Bond</title>
       <para>
       An example of a network bridge formed from two or more bonded Ethernet interfaces will now be given as this is another common application in a virtualization environment. If you are not very familiar with the configuration files for bonded interfaces then please refer to <xref linkend="sec-Create_a_Channel_Bonding_Interface"/>
       </para>
@@ -355,8 +358,8 @@ HWADDR=AA:BB:CC:DD:EE:FF</programlisting>
       <programlisting>DEVICE=bond0
 ONBOOT=yes
 BONDING_OPTS='mode=1 miimon=100'
-      <!--For further instructions and advice on configuring the bonding module and to view the list of bonding parameters, see the <citetitle pubwork="book">&MAJOROSVER; System Administrator's Reference Guide</citetitle>.-->
 BRIDGE=brbond0</programlisting>
+      For further instructions and advice on configuring the bonding module and to view the list of bonding parameters, see <xref linkend="sec-Using_Channel_Bonding"/>.
       </para>
       <para>
       Create or edit one interface configuration file, <filename>/etc/sysconfig/network-scripts/ifcfg-brbond0</filename>, as follows:
@@ -369,8 +372,21 @@ PREFIX=24</programlisting>
 
       <para>We now have two or more interface configuration files with the <option>MASTER=bond0</option> directive. These point to the configuration file named <filename>/etc/sysconfig/network-scripts/ifcfg-bond0</filename>, which contains the <option>DEVICE=bond0</option> directive. This <filename>ifcfg-bond0</filename> in turn points to the <filename>/etc/sysconfig/network-scripts/ifcfg-brbond0</filename> configuration file, which contains the <systemitem class="protocol">IP</systemitem> address, and acts as an interface to the virtual networks inside the host.</para>
       <para>
-      Restart the networking service, in order for the changes to take effect. As <systemitem class="username">root</systemitem> issue the following command:</para>
-<screen>~]#&nbsp;<command>systemctl network restart</command></screen>
+        To bring up the new or recently configured interfaces, issue a command as <systemitem class="username">root</systemitem> in the following format:
+        <synopsis><command>ifup <replaceable>device</replaceable></command></synopsis>
+        This command will detect if <application>NetworkManager</application> is running and call <command>nmcli con load <replaceable>UUID</replaceable></command> and then call <command>nmcli con up <replaceable>UUID</replaceable></command>.
+      </para>
+
+         <para>
+     Alternatively, to reload all interfaces, issue the following command as <systemitem class="username">root</systemitem>:
+<screen>~]#&nbsp;<command>systemctl restart network</command></screen>
+This command will stop the network service, start the network service, and then call <command>ifup</command> for all ifcfg files with <command>ONBOOT=yes</command>.</para>
+
+<note>
+<para>
+     The default behavior is for <application>NetworkManager</application> not to be aware of changes to ifcfg files and to continue using the old configuration data until the interface is next brought up. The is set by the <option>monitor-connection-files</option> option in the <filename>NetworkManager.conf</filename> file. See the <filename>NetworkManager.conf(5)</filename> manual page for more information.
+   </para>
+   </note>
       </section>