Track Bad/Good Roaming using the API calls

[Ajay-Chandrasekaran]

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?

[aleabrahao]

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/

[Ajay-Chandrasekaran]

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?

[aleabrahao]

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.

[Ajay-Chandrasekaran]

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 ?

[aleabrahao]

No, filtering only .11r events and treating denied as bad roaming is not valid. A denied .11r FT attempt does not indicate roaming quality, and Meraki classifies roams as good or bad using roaming time + RSSI, not the .11r status.

[Ajay-Chandrasekaran]

You were talking about syslog right? can you please help with any sample logs received via syslog for roaming and supporting document if available. I was not able to find roaming events as part of syslog supported logs.