Path measurement: Difference between revisions

Path measurement (view source)

Revision as of 06:50, 23 April 2020

10 bytes added , 23 April 2020

no edit summary

Soumar

1,775

edits

@@ Line 106: / Line 106: @@
-. System capture overload: If multiple captures are running in parallel, the CPU might be overloaded. Check the '''All''' tab in the Capture page to see how many captures are running.
+'''1.''' System capture overload: If multiple captures are running in parallel, the CPU might be overloaded. Check the '''All''' tab in the Capture page to see how many captures are running.  In best case there is only the one capturing connection to the master device.
-In best case there is only the one capturing connection to the master device.
+'''2.''' The capturing connection is encrypted with SSL. The small Allegro 200 has a limited encryption capacity so for large traffic this can be a bottleneck. The only solution is to use a more powerful Multimeter.
-. The capturing connection is encrypted with SSL. The small Allegro 200 has a limited encryption capacity so for large traffic this can be a bottleneck. The only solution is to use a more powerful Multimeter.
+'''3.''' Capture drops can also occur if the network connection is not capable of transferring the data fast enough. Rule of thumb is that approximately 5% of the total traffic is used for the measurement connection. For example, if the traffic is 500 MBit/s, the measurement requires ~25 MBit/s of bandwidth on the management port.
-. Capture drops can also occur if the network connection is not capable of transferring the data fast enough.
+The fourth graph shows all packets that are monitored for the path measurement. This will cover all connections that have been seen on both devices.
-Rule of thumb is that approximately 5% of the total traffic is used for the measurement connection. For example, if the traffic is 500 MBit/s, the measurement requires ~25 MBit/s of bandwidth on the management port.
-The fourth graph shows all packets that are monitored for the path measurement.
-This will cover all connections that have been seen on both devices.
 ''' 3- IP statistics '''
-The second tab shows packet loss information for each pair of IP addresses.
+The second tab shows packet loss information for each pair of IP addresses. This statistic covers all IP connections that has been seen on both measurement sides. The table shows the number of packets that have been counted for each communication pair. Additionally the number of packets seen on the master device and the corresponding packet loss is shown. The same statistics are shown for the client device too. You can click on the IP address to go to the detailed statistics of the IP module to check which kind of traffic was happening for that IP. Two graphs are shown for each IP pair which shows the packet loss for both direction on one graph and the total packets in the second graph.
-This statistic covers all IP connections that has been seen on both measurement sides.
+There is also a capture button to capture traffic for the IP pair.  The captured traffic is only the traffic seen on the master device, it will not contain any packet from the client device as the master device does not have the packet data information available. To capture traffic from the client device, you have to go to the web interface of the client device and start a capture on that device.
-The table shows the number of packets that have been counted for each communication pair.
-Additionally the number of packets seen on the master device and the corresponding packet loss is shown.
-The same statistics are shown for the client device too.
-You can click on the IP address to go to the detailed statistics of the IP module to check which kind of traffic was happening for that IP.
-Two graphs are shown for each IP pair which shows the packet loss for both direction on one graph and the total packets in the second graph.
-There is also a capture button to capture traffic for the IP pair.
-The captured traffic is only the traffic seen on the master device, it will not contain any packet from the client device as the master device does not have the packet data information available.
-To capture traffic from the client device, you have to go to the web interface of the client device and start a capture on that device.
 ''' 4- Switching graph modes '''
-The toggle buttons above the graphs allow to switch the graph modes from absolute values to relative values.
+The toggle buttons above the graphs allow to switch the graph modes from absolute values to relative values. This setting will show the lost packets in relation to the total (monitored) traffic.  The second option allows to show mbit/s throughput instead of the packet rate.
-This setting will show the lost packets in relation to the total (monitored) traffic.
-The second option allows to show mbit/s throughput instead of the packet rate.
 ==== Limitations ====