I need to confirm the LACP control id coming off 2 interfaces in an aggregate, anyone know what to put into snoop?

system id*

i don't think snoop currently knows how to decode LACP (though I thought I put in a ticket for that back at joyent.. it's a category called 'slow' protocols)

Smithx10: perhaps use snoop to capture only 0x8809 EtherType data to a file and then open in wireshark

Smithx10: `snoop -rd <interface> -o lacp.pcap 'ethertype 0x8809'`

I think something like that would work

Yeah, that’s what I went with

Yeah, that's what I'd do.

hrm.. i wonder how horrible it'd be for awk to use 64-bit ints

you can also filter specific byte offsets with the `base[expr [:size]] = <id>` if you are looking to script something

(just had it overflow trying to sum things)

though you might need to `and` a few of those depending on how many bytes this ID is

jbk: yeh I've hit that, upstream has fixed a load of issues around that, but due to the way we manage our fork it's a pain to update :/

i just ended up dividing each value by 1MB so I could get a rough sum :)

→ BUG 15180: sync awk from upstream (New)

jbk: Yeah I'm used to how illumos (and FreeBSD) does things in terms of networking

[illumos-gate] 15609 crle: clean up warning gags -- Toomas Soome <tsoome⊙mc>

[illumos-gate] 15671 scsi: the comparison will always evaluate as 'true' -- Toomas Soome <tsoome⊙mc>

[illumos-gate] 15672 ibcm: the comparison will always evaluate as 'false' -- Toomas Soome <tsoome⊙mc>

[illumos-gate] 15681 overlay: the comparison will always evaluate as 'true' -- Toomas Soome <tsoome⊙mc>

[illumos-gate] 15674 ufs: the comparison will always evaluate as 'true' -- Toomas Soome <tsoome⊙mc>

hmmm jbk rzezeski bahamat ever see this happen? I'

The port remains 0mb unknown even after removing it from the aggr too

does dladm show-phys show it as link down?

i40e1 Ethernet down 0 unknown i40e1

that'd explain the 0Mb part.. i guess the question is if the corresponding port on the switch is disabled or not

(i.e. is it reporting down because of the port on the switch or lack of physical connection, or is some other state messed up)