Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
commit 6e4c3a964c9daf2441c023fd94adbe509ba407d2 Author: Stephen Wadeley swadeley@redhat.com Date: Wed Sep 3 22:16:35 2014 +0200
Add: fail_over_mac
en-US/Configure_Network_Bonding.xml | 36 +++++++++++++++++++++++++++++++++++ 1 files changed, 36 insertions(+), 0 deletions(-)
diff --git a/en-US/Configure_Network_Bonding.xml b/en-US/Configure_Network_Bonding.xml index 7afe67e..8f7d6e6 100644 --- a/en-US/Configure_Network_Bonding.xml +++ b/en-US/Configure_Network_Bonding.xml @@ -660,6 +660,42 @@ bond0</screen> <para>Specifies (in milliseconds) how long to wait after link failure before disabling the link. The value must be a multiple of the value specified in the <literal>miimon</literal> parameter. The value is set to <userinput>0</userinput> by default, which disables it.</para> </listitem> </varlistentry> + + <varlistentry> + <term> + <literal>fail_over_mac=<replaceable><value></replaceable> + </literal> + </term> + <listitem> + <para>Specifies whether active-backup mode should set all slaves to the same MAC address at enslavement (the traditional behavior), or, when enabled, perform special handling of the bond's MAC address in accordance with the selected policy. Possible values are: + <itemizedlist> + <listitem> + <para> + <userinput>none</userinput> or <userinput>0</userinput> — Default setting. This setting disables <literal>fail_over_mac</literal>, and causes bonding to set all slaves of an active-backup bond to the same MAC address at enslavement time.</para> + </listitem> + <listitem> + <para> + <userinput>active</userinput> or <userinput>1</userinput> — The <quote>active</quote>> <literal>fail_over_mac</literal> policy indicates that the + MAC address of the bond should always be the MAC address of the currently active slave. The MAC address of the slaves is not changed; instead, the MAC address of the bond changes during a failover.</para> +<para> +This policy is useful for devices that cannot ever alter their MAC address, or for devices that refuse incoming broadcasts with their own source MAC (which interferes with the ARP monitor). The disadvantage of this policy is that every device on the network must be updated via gratuitous ARP, as opposed to the normal method of switches snooping incoming traffic to update their ARP tables. If the gratuitous ARP is lost, communication may be disrupted. +</para> +<para> + When this policy is used in conjunction with the MII monitor, devices which assert link up prior to being able to actually transmit and receive are particularly susceptible to loss of the gratuitous ARP, and an appropriate updelay setting may be required. + </para> + + </listitem> + + <listitem> + <para> + <userinput>follow</userinput> or <userinput>2</userinput> — The <quote>follow</quote> <literal>fail_over_mac</literal> policy causes the MAC address of the bond to be selected normally (normally the MAC address of the first slave added to the bond). However, the second and subsequent slaves are not set to this MAC address while they are in a backup role; a slave is programmed with the bond's MAC address at failover time (and the formerly active slave receives the newly active slave's MAC address).</para> + <para> + This policy is useful for multiport devices that either become confused or incur a performance penalty when multiple ports are programmed with the same MAC address.</para> + </listitem> + </itemizedlist></para> +</listitem> +</varlistentry> + <varlistentry> <term>lacp_rate=<replaceable><value></replaceable> </term>