12:42:43 I need to confirm the LACP control id coming off 2 interfaces in an aggregate, anyone know what to put into snoop? 12:43:36 system id* 13:18:26 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) 14:00:55 Smithx10: perhaps use snoop to capture only 0x8809 EtherType data to a file and then open in wireshark 14:01:04 Smithx10: `snoop -rd -o lacp.pcap 'ethertype 0x8809'` 14:01:09 I think something like that would work 14:01:29 Yeah, that’s what I went with 14:01:39 Yeah, that's what I'd do. 14:05:01 hrm.. i wonder how horrible it'd be for awk to use 64-bit ints 14:05:03 you can also filter specific byte offsets with the `base[expr [:size]] = ` if you are looking to script something 14:05:08 (just had it overflow trying to sum things) 14:05:24 though you might need to `and` a few of those depending on how many bytes this ID is 14:32:14 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 :/ 14:33:46 i just ended up dividing each value by 1MB so I could get a rough sum :) 14:34:03 https://www.illumos.org/issues/15180 14:34:04 → BUG 15180: sync awk from upstream (New) 16:15:47 jbk: Yeah I'm used to how illumos (and FreeBSD) does things in terms of networking 16:47:55 [illumos-gate] 15609 crle: clean up warning gags -- Toomas Soome 17:32:45 [illumos-gate] 15671 scsi: the comparison will always evaluate as 'true' -- Toomas Soome 17:34:57 [illumos-gate] 15672 ibcm: the comparison will always evaluate as 'false' -- Toomas Soome 17:39:54 [illumos-gate] 15681 overlay: the comparison will always evaluate as 'true' -- Toomas Soome 17:48:27 [illumos-gate] 15674 ufs: the comparison will always evaluate as 'true' -- Toomas Soome 19:20:42 hmmm jbk rzezeski bahamat ever see this happen? I' 19:20:45 https://gist.github.com/Smithx10/16afee943f54e0166e3d87245fefd97b 19:24:46 The port remains 0mb unknown even after removing it from the aggr too 19:30:11 does dladm show-phys show it as link down? 19:30:22 i40e1 Ethernet down 0 unknown i40e1 19:31:02 that'd explain the 0Mb part.. i guess the question is if the corresponding port on the switch is disabled or not 19:31:34 (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)