Repository :
http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
---------------------------------------------------------------
commit 68c40617b2db36fabe4c74ddd9c4d9cb693cd864
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Thu Dec 18 21:01:22 2014 +0100
Add warning about direct cable connections
---------------------------------------------------------------
en-US/Configure_Network_Bonding.xml | 12 ++++++++++++
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/en-US/Configure_Network_Bonding.xml b/en-US/Configure_Network_Bonding.xml
index 8a2588c..3fb5f37 100644
--- a/en-US/Configure_Network_Bonding.xml
+++ b/en-US/Configure_Network_Bonding.xml
@@ -10,6 +10,18 @@
Fedora allows administrators to bind multiple network interfaces together into a
single, bonded, channel. Channel bonding enables two or more network interfaces to act as
one, simultaneously increasing the bandwidth and providing redundancy.
</para>
+ <warning>
+ <para>
+ The use of direct cable connections without network switches is not supported for
bonding. 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...
<filename>bonding.txt</filename> file in the
<package>kernel-doc</package> package (see <xref
linkend="sec-Configure_Network_Bonding-docs-installable"/>)-->
+ </para>
+ </note>
+
<section
id="sec-Bond-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces">
<title>Understanding the Default Behavior of Master and Slave
Interfaces</title>
<para>