Fluke Networks: Eliminate the culprit of excessive network traffic

On a sunny Sunday morning, your network may have enough capacity and efficiency just like a great highway. Just like this highway with low traffic, your network traffic is very smooth and there is no bottleneck. You can easily avoid obstacles and rarely bypass the road, even if occasional traffic concentration occurs, it can also be easily mitigated.
But what will happen when there are faulty vehicles on the highway? They may block some lanes. Although the expressway is well designed, when a vehicle fails or its performance is not good enough to occupy Multiple lanes, the speed of the whole expressway will decrease.
Useless network traffic may come from different sources, which usually results in redundant processing of devices, thus affecting users in the entire network.
For example:
Too much broadcast traffic affects Terminal sites that need to determine whether the traffic is related.
Unnecessary protocols may indicate outdated or incorrect device configurations.
Using the default vswitch port setting may cause a large amount of useless traffic, resulting in poor intermittent network performance.
Finding the source that causes excessive network traffic and taking measures to correct or eliminate the root cause can improve network performance and help you avoid potential problems in the future, however, if you do not use the correct tools and troubleshooting techniques, this will be a very time-consuming task.
The EtherScopeTM ES network of fluke Networks Helps you quickly identify excess network traffic and the devices that cause this problem. Elasticsearch provides statistical data to help you understand the impact of elasticsearch on the network and test whether configuration changes can achieve the expected results.
Excessive Broadcast
Broadcast traffic is an essential part of the network. However, as each terminal site that receives a broadcast packet may handle it, it is necessary to reduce the overall broadcast traffic of the network. Excessive broadcast may also indicate hardware or configuration problems, or even Potential Malicious network behavior. In a typical network, the broadcast traffic may be small, or may cause network overload. The first step is to measure the broadcast traffic and determine whether it is too large.

Elasticsearch allows you to track network traffic based on the type and MAC address. You can quickly see which devices are generating a large amount of broadcast traffic. Through the automatic device search capability, the elasticsearch network can associate the source device with the received network traffic to create a "most connected" view. Select broadcast in this view to view the source with the most broadcast traffic.