 | 1 | initial version |
Wireshark can help you with analysis but you would need some special hardware to capture such traffic volumes.
What do you mean by switch overload is another question. I would look at port statistics of the switch at first. The switching fabric is designed to deal mostly with unicast traffic (one going between two ports of a switch) and only a small share is expected to be a native or enforced multicast. If your actual traffic contains too much multicast, you can exceed the fabric capacity, causing packets to be lost, or you can exceed the available bandwidth of the egress ports if the fabric handles more. If too much traffic, even unicast one, from several ingress ports is sent out via a single egress port, you'll get an overload (packet loss) of that port as well. And packet loss due to insufficient bandwidth should be visible in the port statistics.
So a mere ping between two connected devices should tell you whether you overload the switch (or at least one of its ports participating in the test) or not; to find out why that happens is a different story.
Some redundancy techniques build on the fact that a switch multicasts frames for a given MAC address until it gets a frame from that MAC address. Again, the switch should be able to tell you which MAC addresses have been seen which match no particular port; you can see from the MAC value whether it is a multicast one or whether it is one of those reserved for that redundancy techniques.
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
