Devices shown incorrectly - the never ending story

Solved
KarstenI
Kind of a big deal
Kind of a big deal

Devices shown incorrectly - the never ending story

Hi all,

 

I know this is an old thing and was discussed multiple times. But I don't get the actual state ... Can someone direct me?

 

I have multiple networks where clients are shown like this in the dashboard:

KarstenI_0-1694596945733.png

But no, they are not connected with a LAG to the core; the LAG goes to another Meraki stack.

What causes this and what was the solution, if any?

 

Have a great day, Karsten

If you found this post helpful, please give it Kudos. If my answer solves your problem, please click Accept as Solution so others can benefit from it.
1 Accepted Solution
RaphaelL
Kind of a big deal
Kind of a big deal

Do you have client sampling enabled on uplinks ?

View solution in original post

5 Replies 5
RaphaelL
Kind of a big deal
Kind of a big deal

Do you have client sampling enabled on uplinks ?

JacekJ
Building a reputation

Exactly, @KarstenI here you have everything explained:

https://documentation.meraki.com/MS/Monitoring_and_Reporting/MS_Client_Sampling_on_Uplink_Configurat...

the new, default setting is way better, no client jumping between interfaces.

KarstenI
Kind of a big deal
Kind of a big deal

Yes, I disabled the sampling, and now the clients show up correctly. I didn't remember this feature ... Now I have to find out why on some networks it is enabled and on some it is disabled.

If you found this post helpful, please give it Kudos. If my answer solves your problem, please click Accept as Solution so others can benefit from it.
JacekJ
Building a reputation

Because its a fairly new thing.

Old networks will have the "Sample all interfaces" option chosen, only new networks will have the default option picked 🙂

RaphaelL
Kind of a big deal
Kind of a big deal

Not only that , but the default behavior for templates and standalone networks is different.

 

That means you have to check every single network and templates to make sure that it is disabled. This used to be a backend option 🙂

Get notified when there are additional replies to this discussion.