 | 1 | initial version |
Yes you are right, the CPU-acknowledges are queued in the network (my best guess is somewhere on the LACP). You can see it in the CPU trace that the packets are sent out immediately, but on the client trace the came in after a delay. It is by coincidence, that they came with the alarm message.
So I would try to have a deeper look at the statistics of the switches, that you might find a indication of queuing. Maybe you can tune your QOS-buffers.
Root-cause could be Microburst or an issue in LACP handling.
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
