Different behavior of ping via Meraki dashboard compared to similar API call

[IgorIris]

Hi All,

I am working with a customer networks connected via Site to Site VPN. 

If I run ping tool from MX device  tools screen in one of the spoke sites to any of the 4 available hubs' devices it works nicely, i.e shows the ping results (both loss and latency). Similarly I've used this tool to ping locally connected device in the same spoke site, this works fine too.

When I am performing  similar operations using this API  /devices/{serial}/liveTools/ping/{id}

I see following behavior:

- Local clients pinged via API are responding nicely

- Most of the devices I've seen responding OK via Meraki Dashboard screen return odd payload <=> a whole section describing each ping latency is missing. See example of a  payload with missing values:

{
"pingId": "3664804196773537673",
"url": "/devices/Q2XN-FWBN-FTK3/liveTools/ping/3664804196773537673",
"request": {
   "serial": "Q2XN-FWBN-FTK3",
   "target": "12.229.54.60",
   "count": "5"
},
"status": "complete",
"results": {
   "sent": 5,
   "received": 5,
   "loss": {"percentage": 0}
 }
}

same IP from the same MX via UI 

a response part I'm missing 

"replies":[
  {
    "sequenceId": 0,
    "size": 64,
    "latency": 0.169
  },
  {
    "sequenceId": 1,
    "size": 64,
    "latency": 0.295
  },
  {
    "sequenceId": 2,
    "size": 64,
    "latency": 0.177
  },
  {
    "sequenceId": 3,
    "size": 64,
    "latency": 0.152
  },
  {
    "sequenceId": 4,
    "size": 64,
    "latency": 0.14
  }
]

Any suggestion what can I do differently to test the device connectivity through site to site VPN via API ?

Thanks 

[PhilipDAth]

I don't know the answer.

Does specifying the source interface make any difference?

[IgorIris]

I which I had this option, it's missing in the API .
I wrote a post about that https://community.meraki.com/t5/Security-SD-WAN/Ping-API-missing-quot-Source-IP-Address-quot-paramet...