From owner-svn-doc-all@FreeBSD.ORG Thu Feb 13 21:03:02 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C641D5E6; Thu, 13 Feb 2014 21:03:02 +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 B14BE13C1; Thu, 13 Feb 2014 21:03:02 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s1DL32Ae058487; Thu, 13 Feb 2014 21:03:02 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s1DL32Vp058486; Thu, 13 Feb 2014 21:03:02 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201402132103.s1DL32Vp058486@svn.freebsd.org> From: Dru Lavigne Date: Thu, 13 Feb 2014 21:03:02 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43905 - 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-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2014 21:03:02 -0000 Author: dru Date: Thu Feb 13 21:03:02 2014 New Revision: 43905 URL: http://svnweb.freebsd.org/changeset/doc/43905 Log: White space fix only. Translators can ignore. 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:49:58 2014 (r43904) +++ head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Thu Feb 13 21:03:02 2014 (r43905) @@ -3398,30 +3398,29 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefault roundrobin &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 - LACP, as this protocol distributes traffic - bi-directionally while responding to the failure of individual - links. + 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 LACP, as this + protocol distributes traffic bi-directionally while responding + to the failure of individual links. 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;: + whether or not a specific port accepts incoming traffic. The + following protocols are supported by &man.lagg.4;: failover - 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 + 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. @@ -3432,10 +3431,10 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefault &cisco; Fast ðerchannel; (FEC) 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 LACP, that - should be used instead. + static setup and does not negotiate aggregation with the + peer or exchange frames to monitor the link. If the + switch supports LACP, that should be + used instead. @@ -3446,13 +3445,13 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefault (LACP) negotiates a set of 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 - is balanced across the ports in the + LAG is composed of ports of the same + speed, set to full-duplex operation, and traffic is + balanced across the ports in the LAG with the greatest total speed. - Typically, there is only one - LAG which contains all the ports. In - the event of changes in physical connectivity, + Typically, there is only one LAG + which contains all the ports. In the event of changes + in physical connectivity, LACP will quickly converge to a new configuration. @@ -3461,27 +3460,27 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefault information and accepts incoming traffic from any active port. The hash includes the Ethernet source and destination address and, if available, the - VLAN tag, and the IPv4 or - IPv6 source and destination - address. + VLAN tag, and the + IPv4 or IPv6 + source and destination address. roundrobin - 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. + 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. Configuration Examples - + This section demonstrates how to configure a &cisco; switch and a &os; system for LACP load balancing. It then shows how to configure two Ethernet @@ -3493,22 +3492,22 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefault <acronym>LACP</acronym> Aggregation with a &cisco; Switch - 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 - 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 the flows across the - available interfaces. + 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 + 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 the flows across the available + interfaces. On the &cisco; switch, add the FastEthernet0/1 and @@ -3523,8 +3522,9 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefault channel-group 1 mode active channel-protocol lacp - On the &os; system, create the &man.lagg.4; interface using - the physical interfaces fxp0 and + On the &os; system, create the &man.lagg.4; interface + using the physical interfaces + fxp0 and fxp1 and bring the interfaces up with an IP address of 10.0.0.3/24: @@ -3534,7 +3534,7 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefault &prompt.root; ifconfig lagg0 create &prompt.root; ifconfig lagg0 up laggproto lacp laggport fxp0 laggport fxp1 10.0.0.3/24 - Next, verify the status of the virtual interface: + Next, verify the status of the virtual interface: &prompt.root; ifconfig lagg0 lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 @@ -3547,11 +3547,11 @@ lagg0: flags=8843<UP,BROADCAST,RUNNIN 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 + 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: @@ -3587,13 +3587,13 @@ ifconfig_lagg0="laggp Failover Mode 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, fxp0 is the - master interface, fxp1 is - the secondary interface, and the virtual interface is assigned an IP - 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, fxp0 is the + master interface, fxp1 is the + secondary interface, and the virtual interface is assigned + an IP address of 10.0.0.15/24: &prompt.root; ifconfig fxp0 up @@ -3637,28 +3637,26 @@ ifconfig_lagg0="laggp Interfaces 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. + prefers the Ethernet connection for both performance and + security reasons, while maintaining the ability to transfer + data over the wireless connection. This is achieved by overriding the physical wireless - interface's MAC address with that - of the Ethernet - interface. + interface's MAC address with that of the + Ethernet interface. In this example, the Ethernet interface, bge0, is the master and the wireless interface, wlan0, is - the failover. The - wlan0 device was created from - iwn0 wireless interface, which will be configured - with the MAC address of the Ethernet interface. - First, determine the MAC - address of the Ethernet interface: + the failover. The wlan0 device + was created from iwn0 wireless + interface, which will be configured with the + MAC address of the Ethernet interface. + First, determine the MAC address of the + Ethernet interface: &prompt.root; ifconfig bge0 bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 @@ -3670,11 +3668,11 @@ bge0: flags=8843<UP,BROADCAST,RUNNING status: active Replace bge0 to match the - system's Ethernet interface name. The ether - line will contain the MAC address of - the specified interface. Now, change the - MAC address of the underlying wireless - interface: + system's Ethernet interface name. The + ether line will contain the + MAC address of the specified interface. + Now, change the MAC address of the + underlying wireless interface: &prompt.root; ifconfig iwn0 ether 00:21:70:da:ae:37 @@ -3683,8 +3681,8 @@ bge0: flags=8843<UP,BROADCAST,RUNNING &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 + Make sure the bge0 interface + is up, then create the &man.lagg.4; interface with bge0 as master with failover to wlan0: @@ -3692,7 +3690,8 @@ bge0: flags=8843<UP,BROADCAST,RUNNING &prompt.root; ifconfig lagg0 create &prompt.root; ifconfig lagg0 up laggproto failover laggport bge0 laggport wlan0 - The virtual interface should look something like this: + The virtual interface should look something like + this: &prompt.root; ifconfig lagg0 lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500