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