From e69f29a66d593795d3790eb1383e922c9eeb3038 Mon Sep 17 00:00:00 2001 From: Dru Lavigne Date: Mon, 31 Mar 2014 13:57:12 +0000 Subject: [PATCH] As per discussion on freebsd-doc@, clarify wording of lagg definition. Sponsored by: iXsystems --- .../books/handbook/advanced-networking/chapter.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml index 8aecda4779..ddfb39d1ff 100644 --- a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml +++ b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml @@ -3329,8 +3329,8 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2 &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 LACP, as this protocol distributes traffic bi-directionally while responding to the failure of individual links.