LACP is not working

[Julien]

Could you run

'sysctl -A | grep *your network card driver* - i.e. 'sysctl -A | grep em or igb'

Also 'sysctl -A | grep lacp' - lets see your lacp settings

And post output of each command, em or igb is the intel driver

eee is an energy efficient feature can cause issues on freebsd for nics. By setting 'hw.em.eee_setting = 0' in the tunables will turn this off for all nics.

Also what is your lagg settings on your opnsense? - have you tried loadbalance mode?

also on opnsense, lets see the lacp debugging

'sysctl net.link.lagg.lacp.debug=1' - then share the system log - 'clog /var/log/system.log'


IMAHO: It seems someone else has the same issue as you on pfsense - https://forum.netgate.com/topic/158534/lacp-not-working/79 - and thats a brocade switch.

thank you for your answer,
this the log on t he system.log

Code: [Select]

Dec  2 17:37:17 firewall /flowd_aggregate.py[18361]: vacuum src_addr_details_086400.sqlite
Dec  2 17:37:19 firewall /flowd_aggregate.py[18361]: vacuum src_addr_000300.sqlite
Dec  2 17:37:19 firewall /flowd_aggregate.py[18361]: vacuum src_addr_003600.sqlite
Dec  2 17:37:19 firewall /flowd_aggregate.py[18361]: vacuum src_addr_086400.sqlite
Dec  2 17:37:19 firewall /flowd_aggregate.py[18361]: vacuum dst_port_000300.sqlite
Dec  2 17:37:19 firewall /flowd_aggregate.py[18361]: vacuum dst_port_003600.sqlite
Dec  2 17:37:19 firewall /flowd_aggregate.py[18361]: vacuum dst_port_086400.sqlite
Dec  2 17:37:19 firewall /flowd_aggregate.py[18361]: vacuum interface_000030.sqlite
Dec  2 17:37:20 firewall /flowd_aggregate.py[18361]: vacuum interface_000300.sqlite
Dec  2 17:37:20 firewall /flowd_aggregate.py[18361]: vacuum interface_003600.sqlite
Dec  2 17:37:20 firewall /flowd_aggregate.py[18361]: vacuum interface_086400.sqlite

Code: [Select]

root@firewall:~ # sysctl -A | grep lacp
net.link.lagg.lacp.default_strict_mode: 1
net.link.lagg.lacp.debug: 0

I am not sure what to do here

Code: [Select]

'sysctl -A | grep *your network card driver* - i.e. 'sysctl -A | grep em or igb'
do. you mean to run sysctl -A | grep em or igb01 if the interface is igb01.
or you mean I have to run it on the lag interface?

like this ?

Code: [Select]

root@firewall:~ # sysctl -A | grep em3
irq267: em3:irq0:77 @cpu0(domain0): 76231

[Julien]

We have contacted the switch support team and the issue appear to be on the switch and the way it deal with the LACP.
They are aware of but not planning on changing anything in the near future as the switch is out of support.

[Julien]

I have configured the long timeout on the LAG interface but it not showing it on the interface.
anyway I can force that on the lag interface?

Code: [Select]

lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=800008<VLAN_MTU>
        ether e8:39:35:11:fa:ab
        inet6 fe80::ea39:35ff:fe11:faab%lagg0 prefixlen 64 scopeid 0xb
        inet 192.168.73.1 netmask 0xffffff00 broadcast 192.168.73.255
        laggproto lacp lagghash l2,l3,l4
        laggport: em2 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
        laggport: em3 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
        groups: lagg
        media: Ethernet autoselect
        status: active
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>