On Thu, Feb 19, 2026 at 08:13:05PM +0100, Thomas Pries wrote:
> Hi,
>
> I'm trying to set up a LACP trunk with thee links to connect to a switch. I followed the man page:
>
> bash-5.3# ifconfig aggr0 create
> bash-5.3# ifconfig aggr0 trunkport em1
> bash-5.3# ifconfig aggr0 trunkport em2
> bash-5.3# ifconfig aggr0 trunkport em3
> bash-5.3# ifconfig aggr0 192.168.241.42/24
> bash-5.3# ifconfig aggr0 up
>
> but the aggr0 interface stays offline.
>
> bash-5.3# ifconfig
> ...
> em1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
> lladdr fe:e1:ba:d0:c3:51
> index 2 priority 0 llprio 3
> trunk: trunkdev aggr0
> media: Ethernet autoselect (1000baseT full-duplex,master)
> status: active
> em2: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
> lladdr fe:e1:ba:d0:c3:51
> index 3 priority 0 llprio 3
> trunk: trunkdev aggr0
> media: Ethernet autoselect (1000baseT full-duplex,master)
> status: active
> em3: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
> lladdr fe:e1:ba:d0:c3:51
> index 4 priority 0 llprio 3
> trunk: trunkdev aggr0
> media: Ethernet autoselect (1000baseT full-duplex,master)
> status: active
> ...
> aggr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> lladdr fe:e1:ba:d0:c3:51
> index 11 priority 0 llprio 7
> trunk: trunkproto lacp
> trunk id: [(8000,fe:e1:ba:d0:c3:51,000B,0000,0000),
> (0000,00:00:00:00:00:00,0000,0000,0000)]
> em1 lacp actor system pri 0x8000 mac fe:e1:ba:d0:c3:51, key 0xb, port pri 0x8000 number 0x2
> em1 lacp actor state activity,aggregation,defaulted
> em1 lacp partner system pri 0x0 mac 00:00:00:00:00:00, key 0x0, port pri 0x0 number 0x0
> em1 lacp partner state activity,aggregation,sync
> em1 port disabled
> em2 lacp actor system pri 0x8000 mac fe:e1:ba:d0:c3:51, key 0xb, port pri 0x8000 number 0x3
> em2 lacp actor state activity,aggregation,defaulted
> em2 lacp partner system pri 0x0 mac 00:00:00:00:00:00, key 0x0, port pri 0x0 number 0x0
> em2 lacp partner state activity,aggregation,sync
> em2 port disabled
> em3 lacp actor system pri 0x8000 mac fe:e1:ba:d0:c3:51, key 0xb, port pri 0x8000 number 0x4
> em3 lacp actor state activity,aggregation,defaulted
> em3 lacp partner system pri 0x0 mac 00:00:00:00:00:00, key 0x0, port pri 0x0 number 0x0
> em3 lacp partner state activity,aggregation,sync
> em3 port disabled
> groups: aggr
> media: Ethernet autoselect
> status: no carrier
> inet 192.168.241.42 netmask 0xffffff00 broadcast 192.168.241.255
> ...
>
> I also tried with tunk interface but this was also not working.
>
> How can I find out, why the interface is not coming online?
the partner info being all zeros makes it look like the other end isn't
set up for LACP.
you should be able to see if you're getting lacp packets from the peer
by looking at the aggr-port kstats (ie, run kstat aggr-port) for
rx-lacp-pkts. you should also be able to tcpdump on em1 or em2 or
em3 and see lacp packets.
you can enable debug messages on aggr interfaces (ie, ifconfig aggr0
debug), which should give some info about what it's doing with the lacp
packets if it is receiving them. unfortunately the lacp protocol and
state machine are complicated, so understanding the debug messages can
be a challenge.
No comments:
Post a Comment