Date: Thu, 05 Jul 2007 12:44:53 +0100 From: Pete French <petefrench@ticketswitch.com> To: thompsa@FreeBSD.org Cc: stable@freebsd.org Subject: Re: should if_lagg balance outbound traffic on an lacp connection ? Message-ID: <E1I6PlV-0007W1-Rl@dilbert.ticketswitch.com> In-Reply-To: <20070704181903.GA26719@heff.fud.org.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
> bce1 is a concern here as it is not in the ACTIVE state. On your switch > have a look at the lacp stats, here is an example from mine with a 4 > port aggregation. I have to admit that I did not setup the switch and have never looked into this part of the network before. So it's been 24 hours of 'teach yourself cisco'. But whilst researching the lagg stuff on the net I came across an OpenBSD thread which says that you can only use lagg's LACP implementation to aggregate ports connected to the same physical switch. In this case the networking company who installed the switches have installed a pair, and each machine has one port connected to each switch. The pair of switches is allegedly configured to act as a single switch, so I should just be able to aggregate ports between them. Indeed we have one solitary windows box connected the same whayy which does this quite happily. But I do not know if this is possible under FreeBSD > c2950#sh lacp neighbor .... > Port Flags State Priority Key Key Number State > Fa0/11 SA bndl 32768 0x1 0x1 0xB 0x3D > > As you can see all ports are in 'bndl' state which means they have been negoiated. O.K., trying this on each switch I get the following: Port Flags Priority Dev ID Age Key Number State Gi0/2 SA 32768 0019.bb24.0422 25s 0x90 0x1 0x3D and Port Flags Priority Dev ID Age Key Number State Gi0/2 SA 32768 0019.bb24.0422 23s 0x90 0x2 0x3D So I dont have your first 'State' column in the output! But I do have the final one (is the first one simply an english readable alterantive to the hex?). So my ports are in 0x3D as are yours. > And all ports here are ACTIVE. I have been meaning to add IOCTLS to > display more lacp stats to help debug this sort of thing. I still only have one ACTIVE port. I am going to try using 'failover' mode on lagg instead, but it is a shame :-( Do you think this has anything to do with this being two switches ? Thanks for the help, -pcf.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1I6PlV-0007W1-Rl>