Track Bad/Good Roaming using the API calls

AJAY2
Getting noticed

Track Bad/Good Roaming using the API calls

Hi,


Has anyone implemented/studied on how to track bad/good roaming using the Meraki API calls? I cannot find a direct API available for same and also, under assurance --> Analytics --> Overview i see the roaming behavior so do we have any API calls for same?

4 Replies 4
alemabrahao
Kind of a big deal
Kind of a big deal

There is no direct Meraki API that returns the Roaming Health or Roaming Behavior data, but you can track good/bad/suboptimal roaming using existing Meraki API endpoints, mainly by consuming wireless client connectivity events, which do include roam‑related data.

 

 

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

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
AJAY2
Getting noticed

But this isn't scalable right? if there is a large site then how do expect to fire the API calls for 1000 of clients?

alemabrahao
Kind of a big deal
Kind of a big deal

Thinking about it that way, yes, in your case I would recommend using a Syslog, since you can obtain and send roaming events via syslog.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
AJAY2
Getting noticed

How about fetching the Network event logs per Network and filtering the .11r events alone and if the resp :"deny" then it means its a bad roaming ? is this logic fine ?

Get notified when there are additional replies to this discussion.