Path measurement: Difference between revisions

Path measurement (view source)

Revision as of 14:36, 7 May 2020

1,433 bytes added , 7 May 2020

→‎FAQ

Ralf

547

edits

@@ Line 197: / Line 197: @@
 # What can I do if I think the packet loss is wrong?
 #: You can contact [[Reaching Allegro Support|our support]] and if possible provide a small capture from both network sides that cover the same traffic. This will help us to find the reason for the shown packet loss.
+# How can I distinguish between real packet loss and reported packet loss due to packet modifications?
+#: Packet loss is reported when a packet checksum does not match any other checksum reported by the other side within the configured maximum packet delay timeout. Reasons for such an event are
+## Actual loss
+##: The packet have been seen on one side but not the other. In this event the loss graph is usually different between the master and remote device.
+## Packet modification
+##: Some component modifies the packet in some way. Since such a modification is usually done in both direction (sender and receiver), the packet loss is visible on both sides. Therefore the loss graph is symmetrical.
+## Overloaded management connection
+##: The management connection is used to get packet checksum from the remote device. If the connection is not fast enough to transmit the checksum within the configured maximum packet delay time, the packets are then reported as loss.
+##: This can be verified by looking at the debug graph '''Packet delay between local and remote packets'''. In this event, the time will always be at the top limit that is the maximum packet delay time.
+## Temporary network failure
+##: In this event the packets are really lost on both directions so the loss graph may also look similiar. However, since no packet can be transmitted to the other side, you will also see no entries in the two-way-latency graph.