Impacted clients and failure type

yaakov-netop
Conversationalist

Impacted clients and failure type

In Assurance > Overview there is a section of the clients. When I choose the Wireless, and then select one of Association, Authentication or IP address, I can see the Impacted clients and their Failure type.

(more details on this page is here: https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Meraki_Assurance_Over...)

 

What is the API that can give me the Impacted clients and their Failure type?

 

Thanks!

3 Replies 3
sungod
Kind of a big deal
Kind of a big deal

I'd think you would need to use a series of calls, for instance...

 

get list of networks in org

 

iterate over list of networks with...

https://developer.cisco.com/meraki/api-v1/get-network-wireless-clients-health-scores/ 

...to get clients, there could be a LOT

 

select the ones with a imperfect score, and iterate over that list with...

https://developer.cisco.com/meraki/api-v1/get-network-wireless-client-connectivity-events/

 

yaakov-netop
Conversationalist

@sungod What if there is an issue in the network, and because of that, all the APs in the network have bad score? 

We have a rate limit of 10 requests per second per organization, so it will take a lot of time to achieve this data.

 

Is there an API to get the summary of the top issues like this?

(not per client, but per network or organization)

 

yaakovnetop_0-1736948609057.png

 

sungod
Kind of a big deal
Kind of a big deal

Best is to read through the API documentation, there are several endpoints for this sort of info, I use getNetworkWirelessDevicesConnectionStats to get network wide details, and use that to determine the different failure types to present in summary form.

 

In the instance you mention of a network-wide issue, that is something you would need to detect and manage - one AP showing issue == it's the AP, all APs showing the issue == it's the network/other necessary service like DNS, RADIUS etc.

 

If you use the Meraki Python library async I/O calls, you can speed things up a lot, even with hundreds of sites and thousands of APs you can gather the data pretty fast using the call I mentioned.

Get notified when there are additional replies to this discussion.