IN the PCAP, 1 of the LACP states is out of sync, not sure why

Also.... took a few pcaps from a working aggregate and noticed on a few my servers that the actor key is the same 1001... i didnt pcap the other aggregate so maybe we start at 1000 and increment per server?

Fun.... the Partner Key is different for the 2 interfaces that are making my aggregate

I believe that is a *problem*

@Smithx10 is one partner keys (the "bad" one) that increment-by-one value? Or is it some junk value?

(DEBUG kernels may help you here.)

[illumos-gate] 14735 Users with a large group sidlist cause performance problems in SMB -- Matt Barden <mbarden⊙tc>

danmcd: they were cross connected of course

Doh!

errr

and you were cross as a result no doubt

:)

Evidently, tho we have this situation gist.github.com/Smithx10/459c5bd563229ed019db522157d45386

when I did a dladm remove-aggr for the interface that mac address we used as the lacp system id ... the aggregation changed systemids to the only remaining member

The ToR really didn't like this.... the "vpc consistency-parameters" got angry because the local value didnt match the per value after I added it back in

I'm wondering what behavior is correct

Should the Cisco switch side just accept the new systemid being advertised by the LACP PDUs ?

Strangely it allows the i40e3 interface to continue to function lol

When creating a port channel, LACP does its due diligence and compares a few values. The first is the System ID. This is a unique value on each switch. It is a 64-bit value which can be manually assigned or automatically generated. Auto assignment comes from the system priority and the System MAC address. The second value is an identifier for the LAG, such as the port-channel ID. These four values (two at each end) create a LAGID (Link

Aggregation Group Identifier). All ports in a port-channel must have the same LAGID. If there is a mismatch, the ports are excluded or the LAG stays down, depending on the implementation.

Because our system ID changed out from under the switch, it keeps i40e1 "hibernated" or suspended

lol, aggregates are gross

long live the aggregate

people who like reading about system calls will find a bunch of updates to the section 2 man pages for Solaris in: gist.github.com/alanc/b4659167c33c40e159c16b9d048ea2ed

people who like fixing typos in illumos man pages will find a todo list in: pastebin.com/U8b9qXpW

oh wow