I am troubleshooting a PCoIP issue at one site. I have 2 IPSLA responders at this site.
The problem appears to be "out of sequence" UDP packets arriving at the thin-client devices.
Looking at my shadow router in the HQ building I can see IPSLA stats on the router for out of sequence packets.
Can we get Orion VNQM to report this statistic as well?
| Round Trip Time (RTT) for | Index 40008 |
| Latest RTT: 32 milliseconds |
Latest operation start time: 22:27:01.373 GMT Wed Apr 2 2014
Latest operation return code: OK
RTT Values:
| Number Of RTT: 100 | RTT Min/Avg/Max: 31/32/33 milliseconds |
Latency one-way time:
| Number of Latency one-way Samples: 100 | |
| Source to Destination Latency one way Min/Avg/Max: 17/17/19 milliseconds | |
| Destination to Source Latency one way Min/Avg/Max: 13/14/15 milliseconds |
Jitter Time:
| Number of Jitter Samples: 99 | |
| Source to Destination Jitter Min/Avg/Max: 1/1/1 milliseconds | |
| Destination to Source Jitter Min/Avg/Max: 1/1/1 milliseconds |
Packet Loss Values:
| Loss Source to Destination: 0 | Loss Destination to Source: 0 | ||
| Out Of Sequence: 0 | Tail Drop: 0 | Packet Late Arrival: 0 |
Voice Score Values:
| Calculated Planning Impairment Factor (ICPIF): 1 |
MOS score: 4.34
Number of successes: 2
Number of failures: 0
Operation time to live: Forever
Actually everything in the Packet Loss Values section would be helpful to display in Orion.
Each ICMP packet includes a sequence number in its header that is used to count the number of packets received out of sequence on the sender. Both the sequence number and the receive timestamps can be used to calculate out-of-sequence packets on the source-to-destination path. If the receive time stamp for a packet is greater than that of the next packet, the first packet was delivered out of order on the source-to-destination path. For the destination-to-source path, the same method can be applied. Note that if the packet is out of order on the source-to-destination path, it should be returned out of order to the sender unless there is also misordering on the destination-to-source path