Date: Wed, 4 Oct 2017 17:48:09 -0500 From: Dustin Marquess <dmarquess@gmail.com> To: Rainer Duffner <rainer@ultra-secure.de> Cc: freebsd-net@freebsd.org Subject: Re: lagg interface doesn't work Message-ID: <CAJpsHY6JMXimfofH=c2DXZqQ3nPkxoJECL1skV%2BQK_%2BgmR6nrw@mail.gmail.com> In-Reply-To: <F95A6802-8EC3-4027-8AA0-B38118F9A8D9@ultra-secure.de> References: <F95A6802-8EC3-4027-8AA0-B38118F9A8D9@ultra-secure.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 4, 2017 at 3:25 PM, Rainer Duffner <rainer@ultra-secure.de> wrote: > Hi, > > I’m trying to get a lagg(4) setup going. > > This has previously been a linux host, which had to be replace on short notice. > > I’ve rarely used lagg(4). > > > Basically, we have two trunk-ports with a bunch of clans that needs to go over two 10G interface (bxe(4)). > > The switch is a Cisco switch, I don’t know the exact firmware revision - I don’t configure the switches here, this a cut and paste from the admin. > > The previous Linux server used „passive“ mode - it seems FreeBSD does not do that? > > *** > > Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500e-UNIVERSALK9-M), > > ! > > ! > > interface Port-channel121 > description server-prod.front > switchport > switchport trunk allowed vlan 2000,2002,2004,2007,2012,2014 > switchport mode trunk > mtu 9170 > spanning-tree portfast trunk > end > > ! > > ! > > interface TenGigabitEthernet1/1/15 > description server-prod.front-1.1 > switchport trunk allowed vlan 2000,2002,2004,2007,2012,2014 > switchport mode trunk > mtu 9170 > channel-group 121 mode active > spanning-tree portfast trunk > end > > ! > > interface TenGigabitEthernet2/1/15 > description server-prod.front-2.1 > switchport trunk allowed vlan 2000,2002,2004,2007,2012,2014 > switchport mode trunk > mtu 9170 > channel-group 121 mode active > spanning-tree portfast trunk > end > > > On the FreeBSD-side (11.1-AMD64), I have: > (based on the excellent examples here: https://high5.nl/freebsd-lagg-vlan-ipfw-mini-howto) > > ifconfig_bxe0="up" > ifconfig_bxe1="up" > cloned_interfaces="lagg0 vlan2012 vlan2007 vlan2002 vlan2004" > #cloned_interfaces="lagg0 vlan2004" > ifconfig_lagg0="up laggproto lacp laggport bxe0 laggport bxe1" > > ifconfig_vlan2004="inet ip1 netmask 255.255.255.192 vlan 2004 vlandev lagg0" > ifconfig_vlan2012="inet ip2 netmask 255.255.255.192 vlan 2012 vlandev lagg0 " > ifconfig_vlan2007="inet ip3 netmask 255.255.255.240 vlan 2007 vlandev lagg0" > ifconfig_vlan2002="inet ip4 netmask 255.255.255.192 vlan 2002 vlandev lagg0" > > > in sysctl.conf, I added: > net.link.lagg.lacp.default_strict_mode=0 > > > Now, this works as long as I put one of the VLAN-interfaces into promiscuous mode. > > > When I stop tcpdump, I get messages like > > *** > Interface stopped DISTRIBUTING, possible flapping > *** > > and it really stops doing anything. > > > > Any ideas? You probably want: laggproto loadbalance lagghash l3,l4 Instead of: laggproto lacp It also looks like your switch ports are configured for Jumbo packets and on the FreeBSD side you're not increasing the mtu. -Dustin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJpsHY6JMXimfofH=c2DXZqQ3nPkxoJECL1skV%2BQK_%2BgmR6nrw>