White space fix only. Translators can ignore.

Sponsored by: iXsystems
This commit is contained in:
Dru Lavigne 2014-02-13 21:03:02 +00:00
parent 56ba08f862
commit e875e1c36b
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=43905

View file

@ -3398,30 +3398,29 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2</screen>
<indexterm><primary>roundrobin</primary></indexterm> <indexterm><primary>roundrobin</primary></indexterm>
<para>&os; provides the &man.lagg.4; interface which can be used <para>&os; provides the &man.lagg.4; interface which can be used
to aggregate multiple to aggregate multiple network interfaces into one virtual
network interfaces into one virtual interface in order to interface in order to provide failover and link aggregation.
provide failover and link aggregation. Failover allows traffic Failover allows traffic to continue to flow even if an
to continue to flow even if an interface becomes available. Link interface becomes available. Link aggregation works best on
aggregation works best on switches which support switches which support <acronym>LACP</acronym>, as this
<acronym>LACP</acronym>, as this protocol distributes traffic protocol distributes traffic bi-directionally while responding
bi-directionally while responding to the failure of individual to the failure of individual links.</para>
links.</para>
<para>The aggregation protocols supported by the lagg interface <para>The aggregation protocols supported by the lagg interface
determine which ports are used for outgoing traffic and determine which ports are used for outgoing traffic and
whether or not a specific port accepts incoming whether or not a specific port accepts incoming traffic. The
traffic. The following protocols are supported by following protocols are supported by &man.lagg.4;:</para>
&man.lagg.4;:</para>
<variablelist> <variablelist>
<varlistentry> <varlistentry>
<term>failover</term> <term>failover</term>
<listitem> <listitem>
<para>This mode sends and receives traffic only through the master <para>This mode sends and receives traffic only through
port. If the master port becomes unavailable, the next the master port. If the master port becomes
active port is used. The first interface added to the virtual interface is the unavailable, the next active port is used. The first
master port and all subsequently added interfaces are used interface added to the virtual interface is the master
as failover devices. If failover to a non-master port port and all subsequently added interfaces are used as
failover devices. If failover to a non-master port
occurs, the original port becomes master once it occurs, the original port becomes master once it
becomes available again.</para> becomes available again.</para>
</listitem> </listitem>
@ -3432,10 +3431,10 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2</screen>
<listitem> <listitem>
<para>&cisco; Fast &etherchannel; (<acronym>FEC</acronym>) <para>&cisco; Fast &etherchannel; (<acronym>FEC</acronym>)
is found on older &cisco; switches. It provides a is found on older &cisco; switches. It provides a
static setup and does not negotiate aggregation static setup and does not negotiate aggregation with the
with the peer or exchange frames to monitor the link. peer or exchange frames to monitor the link. If the
If the switch supports <acronym>LACP</acronym>, that switch supports <acronym>LACP</acronym>, that should be
should be used instead.</para> used instead.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -3446,13 +3445,13 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2</screen>
(<acronym>LACP</acronym>) negotiates a set of (<acronym>LACP</acronym>) negotiates a set of
aggregable links with the peer into one or more Link aggregable links with the peer into one or more Link
Aggregated Groups (<acronym>LAG</acronym>s). Each Aggregated Groups (<acronym>LAG</acronym>s). Each
<acronym>LAG</acronym> is composed of ports of the <acronym>LAG</acronym> is composed of ports of the same
same speed, set to full-duplex operation, and traffic speed, set to full-duplex operation, and traffic is
is balanced across the ports in the balanced across the ports in the
<acronym>LAG</acronym> with the greatest total speed. <acronym>LAG</acronym> with the greatest total speed.
Typically, there is only one Typically, there is only one <acronym>LAG</acronym>
<acronym>LAG</acronym> which contains all the ports. In which contains all the ports. In the event of changes
the event of changes in physical connectivity, in physical connectivity,
<acronym>LACP</acronym> will quickly converge to a new <acronym>LACP</acronym> will quickly converge to a new
configuration.</para> configuration.</para>
@ -3461,27 +3460,27 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2</screen>
information and accepts incoming traffic from any active information and accepts incoming traffic from any active
port. The hash includes the Ethernet source and port. The hash includes the Ethernet source and
destination address and, if available, the destination address and, if available, the
<acronym>VLAN</acronym> tag, and the <acronym>IPv4</acronym> or <acronym>VLAN</acronym> tag, and the
<acronym>IPv6</acronym> source and destination <acronym>IPv4</acronym> or <acronym>IPv6</acronym>
address.</para> source and destination address.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term>roundrobin</term> <term>roundrobin</term>
<listitem> <listitem>
<para>This mode distributes outgoing traffic using a round-robin <para>This mode distributes outgoing traffic using a
scheduler through all active ports and accepts incoming round-robin scheduler through all active ports and
traffic from any active port. Since this mode violates accepts incoming traffic from any active port. Since
Ethernet frame ordering, it should be used with this mode violates Ethernet frame ordering, it should be
caution.</para> used with caution.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
</variablelist> </variablelist>
<sect2> <sect2>
<title>Configuration Examples</title> <title>Configuration Examples</title>
<para>This section demonstrates how to configure a &cisco; <para>This section demonstrates how to configure a &cisco;
switch and a &os; system for <acronym>LACP</acronym> load switch and a &os; system for <acronym>LACP</acronym> load
balancing. It then shows how to configure two Ethernet balancing. It then shows how to configure two Ethernet
@ -3493,22 +3492,22 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2</screen>
<title><acronym>LACP</acronym> Aggregation with a &cisco; <title><acronym>LACP</acronym> Aggregation with a &cisco;
Switch</title> Switch</title>
<para>This example connects two &man.fxp.4; Ethernet interfaces on a &os; machine <para>This example connects two &man.fxp.4; Ethernet
to the first two interfaces on a &os; machine to the first two Ethernet ports
Ethernet ports on a &cisco; switch as a single load balanced and fault tolerant on a &cisco; switch as a single load balanced and fault
link. More interfaces can be added to increase throughput tolerant link. More interfaces can be added to increase
and fault tolerance. Replace the names of the &cisco; ports, throughput and fault tolerance. Replace the names of the
Ethernet devices, channel group number, and &cisco; ports, Ethernet devices, channel group number, and
<acronym>IP</acronym> address shown in <acronym>IP</acronym> address shown in the example to match
the example to match the local configuration.</para> the local configuration.</para>
<para>Frame ordering is mandatory on <para>Frame ordering is mandatory on Ethernet links and any
Ethernet links and any traffic between two stations always traffic between two stations always flows over the same
flows over the same physical link, limiting the maximum physical link, limiting the maximum speed to that of one
speed to that of one interface. The transmit algorithm interface. The transmit algorithm attempts to use as much
attempts to use as much information as it can to information as it can to distinguish different traffic flows
distinguish different traffic flows and balance the flows across the and balance the flows across the available
available interfaces.</para> interfaces.</para>
<para>On the &cisco; switch, add the <para>On the &cisco; switch, add the
<replaceable>FastEthernet0/1</replaceable> and <replaceable>FastEthernet0/1</replaceable> and
@ -3523,8 +3522,9 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2</screen>
channel-group <replaceable>1</replaceable> mode active channel-group <replaceable>1</replaceable> mode active
channel-protocol lacp</userinput></screen> channel-protocol lacp</userinput></screen>
<para>On the &os; system, create the &man.lagg.4; interface using <para>On the &os; system, create the &man.lagg.4; interface
the physical interfaces <replaceable>fxp0</replaceable> and using the physical interfaces
<replaceable>fxp0</replaceable> and
<replaceable>fxp1</replaceable> and bring the interfaces up <replaceable>fxp1</replaceable> and bring the interfaces up
with an <acronym>IP</acronym> address of with an <acronym>IP</acronym> address of
<replaceable>10.0.0.3/24</replaceable>:</para> <replaceable>10.0.0.3/24</replaceable>:</para>
@ -3534,7 +3534,7 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2</screen>
&prompt.root; <userinput>ifconfig lagg0 create </userinput> &prompt.root; <userinput>ifconfig lagg0 create </userinput>
&prompt.root; <userinput>ifconfig lagg0 up laggproto lacp laggport <replaceable>fxp0</replaceable> laggport <replaceable>fxp1</replaceable> <replaceable>10.0.0.3/24</replaceable></userinput></screen> &prompt.root; <userinput>ifconfig lagg0 up laggproto lacp laggport <replaceable>fxp0</replaceable> laggport <replaceable>fxp1</replaceable> <replaceable>10.0.0.3/24</replaceable></userinput></screen>
<para>Next, verify the status of the virtual interface:</para> <para>Next, verify the status of the virtual interface:</para>
<screen>&prompt.root; <userinput>ifconfig lagg0</userinput> <screen>&prompt.root; <userinput>ifconfig lagg0</userinput>
lagg0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500 lagg0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
@ -3547,11 +3547,11 @@ lagg0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 150
laggport: fxp0 flags=1c&lt;ACTIVE,COLLECTING,DISTRIBUTING&gt;</screen> laggport: fxp0 flags=1c&lt;ACTIVE,COLLECTING,DISTRIBUTING&gt;</screen>
<para>Ports <para>Ports
marked as <literal>ACTIVE</literal> are part of marked as <literal>ACTIVE</literal> are part of the
the <acronym>LAG</acronym> that has been negotiated with <acronym>LAG</acronym> that has been negotiated with the
the remote switch. Traffic will be transmitted and remote switch. Traffic will be transmitted and received
received through these active ports. Add <option>-v</option> through these active ports. Add <option>-v</option> to the
to the above command to view the <acronym>LAG</acronym> above command to view the <acronym>LAG</acronym>
identifiers.</para> identifiers.</para>
<para>To see the port status on the &cisco; switch:</para> <para>To see the port status on the &cisco; switch:</para>
@ -3587,13 +3587,13 @@ ifconfig_<literal>lagg0</literal>="laggproto lacp laggport <replaceable>fxp0</re
<title>Failover Mode</title> <title>Failover Mode</title>
<para>Failover mode can be used to switch over to a secondary <para>Failover mode can be used to switch over to a secondary
interface if the link is lost on the master interface. interface if the link is lost on the master interface. To
To configure failover, make sure that the underlying configure failover, make sure that the underlying physical
physical interfaces are up, then create the &man.lagg.4; interfaces are up, then create the &man.lagg.4; interface.
interface. In this example, <replaceable>fxp0</replaceable> is the In this example, <replaceable>fxp0</replaceable> is the
master interface, <replaceable>fxp1</replaceable> is master interface, <replaceable>fxp1</replaceable> is the
the secondary interface, and the virtual interface is assigned an <acronym>IP</acronym> secondary interface, and the virtual interface is assigned
address of an <acronym>IP</acronym> address of
<replaceable>10.0.0.15/24</replaceable>:</para> <replaceable>10.0.0.15/24</replaceable>:</para>
<screen>&prompt.root; <userinput>ifconfig <replaceable>fxp0</replaceable> up</userinput> <screen>&prompt.root; <userinput>ifconfig <replaceable>fxp0</replaceable> up</userinput>
@ -3637,28 +3637,26 @@ ifconfig_<literal>lagg0</literal>="laggproto failover laggport <replaceable>fxp0
Interfaces</title> Interfaces</title>
<para>For laptop users, it is usually desirable to configure <para>For laptop users, it is usually desirable to configure
the wireless device as a secondary which is only used the wireless device as a secondary which is only used when
when the Ethernet connection is not available. With the Ethernet connection is not available. With
&man.lagg.4;, it is possible to configure a failover which &man.lagg.4;, it is possible to configure a failover which
prefers the Ethernet connection prefers the Ethernet connection for both performance and
for both performance and security reasons, while security reasons, while maintaining the ability to transfer
maintaining the ability to transfer data over the wireless data over the wireless connection.</para>
connection.</para>
<para>This is achieved by overriding the physical wireless <para>This is achieved by overriding the physical wireless
interface's <acronym>MAC</acronym> address with that interface's <acronym>MAC</acronym> address with that of the
of the Ethernet Ethernet interface.</para>
interface.</para>
<para>In this example, the Ethernet interface, <para>In this example, the Ethernet interface,
<replaceable>bge0</replaceable>, is the master and the <replaceable>bge0</replaceable>, is the master and the
wireless interface, <replaceable>wlan0</replaceable>, is wireless interface, <replaceable>wlan0</replaceable>, is
the failover. The the failover. The <replaceable>wlan0</replaceable> device
<replaceable>wlan0</replaceable> device was created from was created from <replaceable>iwn0</replaceable> wireless
<replaceable>iwn0</replaceable> wireless interface, which will be configured interface, which will be configured with the
with the <acronym>MAC</acronym> address of the Ethernet interface. <acronym>MAC</acronym> address of the Ethernet interface.
First, determine the <acronym>MAC</acronym> First, determine the <acronym>MAC</acronym> address of the
address of the Ethernet interface:</para> Ethernet interface:</para>
<screen>&prompt.root; <userinput>ifconfig <replaceable>bge0</replaceable></userinput> <screen>&prompt.root; <userinput>ifconfig <replaceable>bge0</replaceable></userinput>
bge0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500 bge0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
@ -3670,11 +3668,11 @@ bge0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
status: active</screen> status: active</screen>
<para>Replace <replaceable>bge0</replaceable> to match the <para>Replace <replaceable>bge0</replaceable> to match the
system's Ethernet interface name. The <literal>ether</literal> system's Ethernet interface name. The
line will contain the <acronym>MAC</acronym> address of <literal>ether</literal> line will contain the
the specified interface. Now, change the <acronym>MAC</acronym> address of the specified interface.
<acronym>MAC</acronym> address of the underlying wireless Now, change the <acronym>MAC</acronym> address of the
interface:</para> underlying wireless interface:</para>
<screen>&prompt.root; <userinput>ifconfig <replaceable>iwn0</replaceable> ether <replaceable>00:21:70:da:ae:37</replaceable></userinput></screen> <screen>&prompt.root; <userinput>ifconfig <replaceable>iwn0</replaceable> ether <replaceable>00:21:70:da:ae:37</replaceable></userinput></screen>
@ -3683,8 +3681,8 @@ bge0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
<screen>&prompt.root; <userinput>ifconfig wlan0 create wlandev <replaceable>iwn0</replaceable> ssid <replaceable>my_router</replaceable> up</userinput></screen> <screen>&prompt.root; <userinput>ifconfig wlan0 create wlandev <replaceable>iwn0</replaceable> ssid <replaceable>my_router</replaceable> up</userinput></screen>
<para>Make sure the <replaceable>bge0</replaceable> interface is up, then <para>Make sure the <replaceable>bge0</replaceable> interface
create the &man.lagg.4; interface with is up, then create the &man.lagg.4; interface with
<replaceable>bge0</replaceable> as master with failover to <replaceable>bge0</replaceable> as master with failover to
<replaceable>wlan0</replaceable>:</para> <replaceable>wlan0</replaceable>:</para>
@ -3692,7 +3690,8 @@ bge0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
&prompt.root; <userinput>ifconfig lagg0 create</userinput> &prompt.root; <userinput>ifconfig lagg0 create</userinput>
&prompt.root; <userinput>ifconfig lagg0 up laggproto failover laggport <replaceable>bge0</replaceable> laggport wlan0</userinput></screen> &prompt.root; <userinput>ifconfig lagg0 up laggproto failover laggport <replaceable>bge0</replaceable> laggport wlan0</userinput></screen>
<para>The virtual interface should look something like this:</para> <para>The virtual interface should look something like
this:</para>
<screen>&prompt.root; <userinput>ifconfig lagg0</userinput> <screen>&prompt.root; <userinput>ifconfig lagg0</userinput>
lagg0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500 lagg0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500