[networking-guide] master: Team prefers port rather than slave interface (6eec07f)

stephenw at fedoraproject.org stephenw at fedoraproject.org
Fri Jul 25 06:46:56 UTC 2014


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

On branch  : master

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

commit 6eec07fc77443d7240e378c23e795997b7dbbcf8
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Mon Jul 21 22:59:14 2014 +0200

    Team prefers port rather than slave interface


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

 en-US/Configure_Network_Teaming.xml |   16 ++++++++--------
 1 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/en-US/Configure_Network_Teaming.xml b/en-US/Configure_Network_Teaming.xml
index 2059436..4c4956a 100644
--- a/en-US/Configure_Network_Teaming.xml
+++ b/en-US/Configure_Network_Teaming.xml
@@ -319,41 +319,41 @@ From the available interfaces, determine which are suitable for adding to your n
 <section id="sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces">
 <title>Understanding the Default Behavior of Master and Slave Interfaces</title>
 <para>
-When controlling teamed slave interfaces using <systemitem class="daemon">NetworkManager</systemitem>, and especially when fault finding, keep the following in mind:
+When controlling teamed port interfaces using the <systemitem class="daemon">NetworkManager</systemitem> daemon, and especially when fault finding, keep the following in mind:
 <orderedlist>
   <listitem>
     <para>
-      Starting the master interface does not automatically start the slave interfaces.
+      Starting the master interface does not automatically start the port interfaces.
     </para>
   </listitem>
   <listitem>
     <para>
-      Starting a slave interface always starts the master interface.
+      Starting a port interface always starts the master interface.
     </para>
   </listitem>
   <listitem>
     <para>
-      Stopping the master interface also stops the slave interfaces.
+      Stopping the master interface also stops the port interfaces.
     </para>
   </listitem>
   <listitem>
     <para>
-      A master without slaves can start static <systemitem class="protocol">IP</systemitem> connections.
+      A master without ports can start static <systemitem class="protocol">IP</systemitem> connections.
     </para>
   </listitem>
   <listitem>
     <para>
-      A master without slaves waits for slaves when starting <systemitem class="protocol">DHCP</systemitem> connections.
+      A master without ports waits for ports when starting <systemitem class="protocol">DHCP</systemitem> connections.
     </para>
   </listitem>
   <listitem>
     <para>
-    A master with a <systemitem class="protocol">DHCP</systemitem> connection waiting for slaves completes when a slave with a carrier is added.
+    A master with a <systemitem class="protocol">DHCP</systemitem> connection waiting for ports completes when a port with a carrier is added.
     </para>
   </listitem>
   <listitem>
     <para>
-    A master with a <systemitem class="protocol">DHCP</systemitem> connection waiting for slaves continues waiting when a slave without a carrier is added.
+    A master with a <systemitem class="protocol">DHCP</systemitem> connection waiting for ports continues waiting when a port without a carrier is added.
     </para>
   </listitem>
 </orderedlist>



More information about the docs-commits mailing list