From owner-freebsd-doc@FreeBSD.ORG Thu Aug 4 20:28:53 2011 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C522A106566B; Thu, 4 Aug 2011 20:28:53 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-7.mit.edu (DMZ-MAILSEC-SCANNER-7.MIT.EDU [18.7.68.36]) by mx1.freebsd.org (Postfix) with ESMTP id 64A178FC18; Thu, 4 Aug 2011 20:28:53 +0000 (UTC) X-AuditID: 12074424-b7b0fae000000a08-3b-4e3b011f4ca5 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP id 01.05.02568.F110B3E4; Thu, 4 Aug 2011 16:29:19 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id p74KSqTr023109; Thu, 4 Aug 2011 16:28:52 -0400 Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id p74KSoex002182 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 4 Aug 2011 16:28:51 -0400 (EDT) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id p74KSoCi002072; Thu, 4 Aug 2011 16:28:50 -0400 (EDT) Date: Thu, 4 Aug 2011 16:28:50 -0400 (EDT) From: Benjamin Kaduk To: Karli SjXberg In-Reply-To: <201108020551.p725pwKM051602@red.freebsd.org> Message-ID: References: <201108020551.p725pwKM051602@red.freebsd.org> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrHIsWRmVeSWpSXmKPExsUixCmqrSvPaO1nsOikjMWpM12sFi1PVrNb 3Ng2ic2B2WPGp/ksHjtn3WUPYIrisklJzcksSy3St0vgypi47A9bwWHRivnb3rI3MM4R7GLk 5JAQMJE4u/8LI4QtJnHh3nq2LkYuDiGBfYwSk2+2M0I46xklfnz6BeXsZ5JY2/yIBaRFSKBe Yu6LH8wgNouAlsSak2tZQWw2ARWJmW82soHYIgLaEpP/zACrZxawldgz4QlYvbBAmMSSt91g NZwCVhKPGqaDncEr4CBxYMsGZoj5lhIdZx4ygdiiAjoSq/dPYYGoEZQ4OfMJ1ExLiX9rf7FO YBSchSQ1C0lqASPTKkbZlNwq3dzEzJzi1GTd4uTEvLzUIl1zvdzMEr3UlNJNjKCgZXdR2cHY fEjpEKMAB6MSD++fXVZ+QqyJZcWVuYcYJTmYlER5+Ris/YT4kvJTKjMSizPii0pzUosPMUpw MCuJ8FaC5HhTEiurUovyYVLSHCxK4ryl3v99hQTSE0tSs1NTC1KLYLIyHBxKErx9II2CRanp qRVpmTklCGkmDk6Q4TxAw8EW8xYXJOYWZ6ZD5E8x6nKs/vvxKKMQS15+XqqUOG8mSJEASFFG aR7cHFiyecUoDvSWMG87SBUPMFHBTXoFtIQJaMn/9xYgS0oSEVJSDYy8ntX2NRUKT+a+7bdd tu7zEcHn/a/1/kS16P5bXXzpvVKakdt3LtNgo8mVemV+9o4dMZfiNt7at6pceNnGSrmUZ4tU jfoSlm5/L3Lrp/4Zi8xJNw0PzOjM6d11w+/i6x3LWDKar2kvvh/CKpZdmjAnnvHPtZWHuN/s 9eqYoufhsl8qI0D79TslluKMREMt5qLiRAAcNA63EQMAAA== Cc: freebsd-doc@freebsd.org, freebsd-gnats-submit@freebsd.org Subject: Re: docs/159374: Difficulty following guide on configuring link aggregation X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Aug 2011 20:28:53 -0000 Dear Karli, On Tue, 2 Aug 2011, Karli SjXberg wrote: > > > last week, it was the first time for me setting up a lagg interface with > a cisco switch and had this page from the handbook as a guide: > > Link Aggregation and Failover > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-aggregation.html > > I had troubles getting everything to work because the lagg interface > always showed "no carrier" as status and couldn?t get an address. After > much googling, I found the reason for this is because you have make the > laggports "up" before you create the lagg interface. > > The rest went off without a hitch and it was so cool to see everything > "just work". You really got double the perfomance and perfect failover! > > If this had been explained in the handbook, it would have saved me half a day?s worth of troubleshooting. > > Correct approach: > # ifconfig em0 up > # ifconfig em1 up > # ifconfig lagg0 create > # ifconfig lagg0 up laggproto lacp laggport em0 laggport em1 > This is standard behavior for manually configuring network interfaces -- the explicit setting of the interface as 'up' is needed when no other information about the interface is given (e.g. in rc.conf or wpa_supplicant.conf). So I do not think it is really appropriate to give particular emphasis to the need to "up" the interface, in this particular location in the text. It should be fine to include an explicit example of doing so for the LACP case, though. (Note that a later, non-LACP, example on that page does include the 'up' stage.) It may also be needed to mention the general need for setting interfaces as "up" elsewhere in the handbook, but I do not have time to check that right now. > /etc/rc.conf: > ifconfig_em0="up" > ifconfig_em1="up" > cloned_interfaces="lagg0" > ifconfig_lagg0="up laggproto lacp laggport em0 laggport em1 DHCP" Is the "up" really necessary for ifconfig_lagg0, here? I could mostly believe that it is needed for em[01], but my understanding is that it would not be needed for lagg0; the very last example on the page you link does not have it for the failover case, as well. If you could check and report back, that would be helpful. Thanks, Ben Kaduk > > I think it would make things much easier for other people in that > situation, if this was explained on that page. How does that sound? > > /Sebulon >> How-To-Repeat: > >> Fix: > > >> Release-Note: >> Audit-Trail: >> Unformatted: > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" >