Repository :
http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
---------------------------------------------------------------
commit 5cf266191afae65cef9b5ec117356c7e3274b4b3
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Thu Oct 15 23:25:50 2015 +0200
teaming will not work without a switch
---------------------------------------------------------------
en-US/Configure_Network_Teaming.xml | 17 +++++++++++++++++
1 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/en-US/Configure_Network_Teaming.xml b/en-US/Configure_Network_Teaming.xml
index 720b0e7..c04e3a4 100644
--- a/en-US/Configure_Network_Teaming.xml
+++ b/en-US/Configure_Network_Teaming.xml
@@ -5,6 +5,23 @@
]>
<chapter id="ch-Configure_Network_Teaming">
<title>Configure Network Teaming</title>
+
+
+ <warning>
+ <para>
+ The use of direct cable connections without network switches is not supported for
teaming. The failover mechanisms described here will not work as expected without the
presence of network switches.
+ </para>
+</warning>
+
+ <note>
+ <para>
+ The active-backup, balance-tlb and balance-alb modes do not require any specific
configuration of the switch. Other bonding modes require configuring the switch to
aggregate the links. For example, a Cisco switch requires EtherChannel for Modes 0, 2, and
3, but for Mode 4 LACP and EtherChannel are required. See the documentation supplied with
your switch and see <ulink
url="https://www.kernel.org/doc/Documentation/networking/bonding.txt...;.
+ </para>
+ <para>
+ Unlike bonding, if a team interface is configured to use link aggregation but LACP is
not correctly configured and working on the network switch, no routable connection will be
formed.
+ </para>
+ </note>
+
<!-- Topics, Concepts:-->
<section id="sec-Understanding_Network_Teaming">
<title>Understanding Network Teaming</title>