70
edits
Investigate Network Load: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
Open the web interface via a browser. | Open the web interface via a browser. | ||
[[File: | [[File:Investigate_network_load_dash.png|1000px|Allegro Network Multimeter Dashboard]] | ||
== Time Selection == | == Time Selection == | ||
| Line 16: | Line 16: | ||
{| | {| | ||
| [[File: | | [[File:Investigate_network_load_time_select.png|300px|thumb|right]] | ||
|} | |} | ||
In this case, we are looking for events from this morning | In this case, we are looking for events from this morning. Now select the time period in which the users have reported | ||
problems by selecting (click 'n drag) such section with the mouse: | problems by selecting (click 'n drag) such section with the mouse: | ||
{| | {| | ||
| [[File: | | [[File:Investigate_network_load_spike_select.png|600px|thumb|right]] | ||
|} | |} | ||
| Line 37: | Line 36: | ||
* Is there extremely low or no network traffic during this period? This may indicate link problems such as no connection to the Internet or to another network node. | * Is there extremely low or no network traffic during this period? This may indicate link problems such as no connection to the Internet or to another network node. | ||
In our example, | {| | ||
By clicking on | | [[File:Investigate_network_load_top_statistics.png|800px|thumb|right]] | ||
traffic: | |} | ||
Let’s check by clicking on ‘Top protocols during selected interval’ for the cause of the slow connection.<br> | |||
In our example, ‘WindowsUpdate’ showed up as one of the culprits. | |||
{| | |||
| [[File:Investigate_network_load_L7.png|800px|thumb|right]] | |||
|} | |||
By clicking on ‘WindowsUpdate’ under ‘Protocol’ you can easily see an overview of who triggered this traffic: | |||
{| | {| | ||
| [[File: | | [[File:Investigate_network_load_protocol_winupdate.png|800px|thumb|right]] | ||
|} | |} | ||
Here, the | Here, the machines ‘adguard.intra.allegro-packets.com’ and ‘archlinux‘ generated spikes with both uploads and downloads, which can lead to user disruption.<br> | ||
By clicking on an IP address (in our example ‘10.41.16.110’), you can further investigate the causes and even look into the IP’s connections: | |||
{| | |||
| [[File:Investigate_network_load_ip_statistics.png|800px|thumb|right]] | |||
|} | |||
Under the ‘Connections’ tab you will find all connections the selected IP has made in the selected timeframe and you can even see the amount of TCP retransmissions that have been made<br> | |||
(to see the TCP retransmissions you might have to enable this option in your filter). | |||
{| | {| | ||
| | | [[File:Investigate_network_load_ip_connections.png|800px|thumb|right]] | ||
[[File: | |||
|} | |} | ||
You can use the number of retransmission to estimate if there was a bottleneck | You can use the number of retransmission to estimate if there was a bottleneck between the Allegro Network Multimeter and the recipient and if more packets had to be retransmitted.<br> | ||
between the Allegro Network Multimeter and the recipient and if more packets had to be retransmitted. | If you need a even more detailed analysis, you can use the pcap button to extract the connection packets.<br> | ||
{| | |||
| [[File:Investigate_network_load_pcap_download.png|800px|thumb|right]] | |||
|} | |||