Date: Mon, 31 Mar 2014 13:57:12 +0000 (UTC) From: Dru Lavigne <dru@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44394 - head/en_US.ISO8859-1/books/handbook/advanced-networking Message-ID: <201403311357.s2VDvCLU007069@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: dru Date: Mon Mar 31 13:57:12 2014 New Revision: 44394 URL: http://svnweb.freebsd.org/changeset/doc/44394 Log: As per discussion on freebsd-doc@, clarify wording of lagg definition. 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 Mon Mar 31 00:32:09 2014 (r44393) +++ head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Mon Mar 31 13:57:12 2014 (r44394) @@ -3329,8 +3329,8 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefault <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 + Failover allows traffic to continue to flow as long as at least one + aggregated network interface has an established link. 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>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201403311357.s2VDvCLU007069>