From owner-svn-doc-head@FreeBSD.ORG Thu Feb 13 20:49:59 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9C905A5C; Thu, 13 Feb 2014 20:49:59 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7A69F122A; Thu, 13 Feb 2014 20:49:59 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s1DKnxAd051342; Thu, 13 Feb 2014 20:49:59 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s1DKnxgF051341; Thu, 13 Feb 2014 20:49:59 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201402132049.s1DKnxgF051341@svn.freebsd.org> From: Dru Lavigne Date: Thu, 13 Feb 2014 20:49:59 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43904 - head/en_US.ISO8859-1/books/handbook/advanced-networking X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2014 20:49:59 -0000 Author: dru Date: Thu Feb 13 20:49:58 2014 New Revision: 43904 URL: http://svnweb.freebsd.org/changeset/doc/43904 Log: Finish editorial review of this chapter. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Thu Feb 13 20:09:42 2014 (r43903) +++ head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Thu Feb 13 20:49:58 2014 (r43904) @@ -3399,17 +3399,18 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefault &os; provides the &man.lagg.4; interface which can be used to aggregate multiple - network interfaces into one virtual interface for the purpose of - providing fault tolerance and link aggregation. Link + 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 LACP, as this protocol distributes traffic bi-directionally while responding to the failure of individual links. - The operating modes supported by the lagg interface + 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 operating modes are supported by + traffic. The following protocols are supported by &man.lagg.4;: @@ -3443,7 +3444,7 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefault The &ieee; 802.3ad Link Aggregation Control Protocol (LACP) negotiates a set of - aggregable links with the peer in to one or more Link + aggregable links with the peer into one or more Link Aggregated Groups (LAGs). Each LAG is composed of ports of the same speed, set to full-duplex operation, and traffic @@ -3471,8 +3472,8 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefault This mode distributes outgoing traffic using a round-robin scheduler through all active ports and accepts incoming - traffic from any active port. This mode violates - Ethernet frame ordering and should be used with + traffic from any active port. Since this mode violates + Ethernet frame ordering, it should be used with caution. @@ -3492,15 +3493,21 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefault <acronym>LACP</acronym> Aggregation with a &cisco; Switch - This example connects two interfaces on a &os; machine - to the switch as a single load balanced and fault tolerant + 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. Frame ordering is mandatory on + and fault tolerance. Replace the names of the &cisco; ports, + Ethernet devices, channel group number, and + IP address shown in + the example to match the local configuration. + + 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 across the + distinguish different traffic flows and balance the flows across the available interfaces. On the &cisco; switch, add the @@ -3508,32 +3515,26 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefault FastEthernet0/2 interfaces to channel group 1: - interface FastEthernet0/1 - channel-group 1 mode active + interface FastEthernet0/1 + channel-group 1 mode active channel-protocol lacp ! -interface FastEthernet0/2 - channel-group 1 mode active +interface FastEthernet0/2 + channel-group 1 mode active channel-protocol lacp On the &os; system, create the &man.lagg.4; interface using the physical interfaces fxp0 and - fxp1, and bring the interfaces up + fxp1 and bring the interfaces up with an IP address of 10.0.0.3/24: - &prompt.root; ifconfig fxp0 up -&prompt.root; ifconfig fxp1 up + &prompt.root; ifconfig fxp0 up +&prompt.root; ifconfig fxp1 up &prompt.root; ifconfig lagg0 create -&prompt.root; ifconfig lagg0 up laggproto lacp laggport fxp0 laggport fxp1 10.0.0.3/24 +&prompt.root; ifconfig lagg0 up laggproto lacp laggport fxp0 laggport fxp1 10.0.0.3/24 - Next, verify the status of the virtual interface. Ports - marked as ACTIVE are part of - the active aggregation group that has been negotiated with - the remote switch. Traffic will be transmitted and - received through active ports. Use the verbose output of - &man.ifconfig.8; to view the LAG - identifiers. + Next, verify the status of the virtual interface: &prompt.root; ifconfig lagg0 lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 @@ -3545,6 +3546,14 @@ lagg0: flags=8843<UP,BROADCAST,RUNNIN laggport: fxp1 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING> laggport: fxp0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING> + Ports + marked as ACTIVE are part of + the LAG that has been negotiated with + the remote switch. Traffic will be transmitted and + received through these active ports. Add + to the above command to view the LAG + identifiers. + To see the port status on the &cisco; switch: switch# show lacp neighbor @@ -3579,7 +3588,7 @@ ifconfig_lagg0="laggp Failover mode can be used to switch over to a secondary interface if the link is lost on the master interface. - To configure failover mode, make sure that the underlying + To configure failover, make sure that the underlying physical interfaces are up, then create the &man.lagg.4; interface. In this example, fxp0 is the master interface, fxp1 is @@ -3587,10 +3596,10 @@ ifconfig_lagg0="laggp address of 10.0.0.15/24: - &prompt.root; ifconfig fxp0 up -&prompt.root; ifconfig fxp1 up + &prompt.root; ifconfig fxp0 up +&prompt.root; ifconfig fxp1 up &prompt.root; ifconfig lagg0 create -&prompt.root; ifconfig lagg0 up laggproto failover laggport fxp0 laggport fxp1 10.0.0.15/24 +&prompt.root; ifconfig lagg0 up laggproto failover laggport fxp0 laggport fxp1 10.0.0.15/24 The virtual interface should look something like this: @@ -3624,7 +3633,7 @@ ifconfig_lagg0="laggp - Failover Mode Between Wired and Wireless + <title>Failover Mode Between Ethernet and Wireless Interfaces For laptop users, it is usually desirable to configure @@ -3636,7 +3645,7 @@ ifconfig_lagg0="laggp maintaining the ability to transfer data over the wireless connection. - This is achieved by overriding the underlying wireless + This is achieved by overriding the physical wireless interface's MAC address with that of the Ethernet interface. @@ -3667,21 +3676,21 @@ bge0: flags=8843<UP,BROADCAST,RUNNING MAC address of the underlying wireless interface: - &prompt.root; ifconfig iwn0 ether 00:21:70:da:ae:37 + &prompt.root; ifconfig iwn0 ether 00:21:70:da:ae:37 Bring the wireless interface up, but do not set an IP address: - &prompt.root; ifconfig wlan0 create wlandev iwn0 ssid my_router up + &prompt.root; ifconfig wlan0 create wlandev iwn0 ssid my_router up Make sure the bge0 interface is up, then create the &man.lagg.4; interface with bge0 as master with failover to wlan0: - &prompt.root; ifconfig bge0 up + &prompt.root; ifconfig bge0 up &prompt.root; ifconfig lagg0 create -&prompt.root; ifconfig lagg0 up laggproto failover laggport bge0 laggport wlan0 +&prompt.root; ifconfig lagg0 up laggproto failover laggport bge0 laggport wlan0 The virtual interface should look something like this: @@ -3704,12 +3713,12 @@ lagg0: flags=8843<UP,BROADCAST,RUNNIN following entries to /etc/rc.conf: - ifconfig_bge0="up" -ifconfig_iwn0="ether 00:21:70:da:ae:37" -wlans_iwn0="wlan0" + ifconfig_bge0="up" +ifconfig_iwn0="ether 00:21:70:da:ae:37" +wlans_iwn0="wlan0" ifconfig_wlan0="WPA" cloned_interfaces="lagg0" -ifconfig_lagg0="laggproto failover laggport bge0 laggport wlan0 DHCP" +ifconfig_lagg0="laggproto failover laggport bge0 laggport wlan0 DHCP"