Hi,

sorry for PM.

On 19.02.2026 23:33, David Gwynne wrote:
On Thu, Feb 19, 2026 at 08:13:05PM +0100, Thomas Pries wrote:
... aggr0 interface stays offline.

In the mean time, I tried Ubuntu 24.04 to see, if the switch config and the 
host hardware is able to establish a LACP connection. This works out of the box.

I also switched to a new host and new network adapter (em{1,2,3} => ixl{2,3}) 
but the same behavior.

... 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.

Looks like there is nothing on aggr0:

aggr0:0:aggr-port:3
interface: ixl2
...
rx-lacp-pkts: 0 packets
...
aggr0:0:aggr-port:4
interface: ixl3
...
rx-lacp-pkts: 0 packets
...

... you should also be able to tcpdump on em1 or em2 or
em3 and see lacp packets.

But I see LACP packets on ixl{2,3}:
...
802.3 Slow protocols
    Slow Protocols subtype: LACP (0x01)
Link Aggregation Control Protocol
    LACP Version: 0x01
    TLV Type: Actor Information (0x01)
    TLV Length: 0x14
    Actor System Priority: 2000
    Actor System ID: AlliedTelesi_1a:6c:fa (e0:1a:ea:1a:6c:fa)
    Actor Key: 1
    Actor Port Priority: 32768
    Actor Port: 5052
    Actor State: 0x45, LACP Activity, Aggregation, Defaulted
        .... ...1 = LACP Activity: Active
        .... ..0. = LACP Timeout: Long Timeout
        .... .1.. = Aggregation: Aggregatable
        .... 0... = Synchronization: Out of Sync
        ...0 .... = Collecting: Disabled
        ..0. .... = Distributing: Disabled
        .1.. .... = Defaulted: Yes
        0... .... = Expired: No
    [Actor State Flags: *F***G*A]
    Reserved: 000000
    TLV Type: Partner Information (0x02)
    TLV Length: 0x14
    Partner System Priority: 32768
    Partner System: 00:00:00_00:00:00 (00:00:00:00:00:00)
    Partner Key: 0
    Partner Port Priority: 0
    Partner Port: 0
    Partner State: 0x44, Aggregation, Defaulted
        .... ...0 = LACP Activity: Passive
        .... ..0. = LACP Timeout: Long Timeout
        .... .1.. = Aggregation: Aggregatable
        .... 0... = Synchronization: Out of Sync
        ...0 .... = Collecting: Disabled
        ..0. .... = Distributing: Disabled
        .1.. .... = Defaulted: Yes
        0... .... = Expired: No
    [Partner State Flags: *F***G**]
    Reserved: 000000
    TLV Type: Collector Information (0x03)
    TLV Length: 0x10
    Collector Max Delay: 5
    Reserved: 000000000000000000000000
    TLV Type: Terminator (0x00)
    TLV Length: 0x00
    Pad: 
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

but there seems to be no answer from the host side.
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.

I enabled debug on ixl{2,3} and aggr0, but only messages when I pull off cables:

aggr0 ixl3 rxm: LACP_DISABLED (!port_enabled) -> PORT_DISABLED
aggr0 ixl3 rxm: PORT_DISABLED (port_enabled) -> LACP_DISABLED
aggr0 ixl2 rxm: LACP_DISABLED (!port_enabled) -> PORT_DISABLED
aggr0 ixl2 rxm: PORT_DISABLED (port_enabled) -> LACP_DISABLED


Kind regards
Thomas






Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to