RTT discrepancies between nPing and ping from within the cEdge

Meng Li · ‎08-05-2021

I'm trying to figure out how exactly nPing works under vManage GUI> Network > Troubleshooting and why RTT shown from its ping output and what the managed router tells me is completely different.

I noticed this when I tried to test ping from one of its managed cEdge to a Microsoft Azure IP. The MS IP is configured to locally breakout (DIA) so below the RTT from the cEdge ping test is expected, it exits from the local Internet and should have had a low latency etc.

<cEdge router>#ping vrf 1 52.113.194.132 so lo0 size 1300 re 30

Type escape sequence to abort.

Sending 30, 1300-byte ICMP Echos to 52.113.194.132, timeout is 2 seconds:

Packet sent with a source address of 10.31.112.49

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Success rate is 100 percent (30/30), round-trip min/avg/max = 1/2/5 ms

However, when I ran the same test from vManage GUI> Network > Troubleshooting, I got a completely different RTT as if the ping did not come from the cEdge/send directly to the destination MS IP. No packet was seen to lost which seems suggests it's still accurate. But I don't understand why RTT was so high where DIA is configured and its actual value should be what the CLI ping displayed?

Or is the 'rapid' ping in the GUI the one that we actually use in CLI PING?