Ok, thanks for the info ... View more

I don't believe this to be due to TLS version compatibility as the TLS handshake wouldn't complete and thus wouldn't have an expectation any payload, partial or otherwise, would be delivered from the server. This can be easily verified in a Wireshark packet capture. Image attached illustrates this where the client sends an API request with TLSv1.1 and the server responds with a descriptive error followed by the termination of the TCP session.   ... View more

1) Yes thats right , I was referring to the the org level call - https://developer.cisco.com/meraki/api-v1/#!get-organization-appliance-uplinks-usage-by-network . So the Org level call always shows the active Interface but the values will be aggregated ? The network level call gives the data for each interface separately.   2) Thanks , I think from the monitoring standpoint considering all the endpoints available or known to us, this is the best approach. Agreed that Cellular limits are not guaranteed.  We do collect the loss and latency and now adding the bandwidth , all at a 5 min polling interval .    3)So the circuit availability could be inferred from the uplink status calls  . We do collect that information.   Thanks @sungod  ... View more

Okay, thanks John.  ... View more