Here are some questions that I would like Meraki to address: For the purpose of displaying clients on the dashboard, why does Meraki place a higher weight on cryptic MDNS names rather than easily identifiable names? I’ve been using Meraki for over 6 years now and not until June of 2019 had I ever even seen an MDNS name for a client in the dashboard. If MDNS names have always had the highest priority why are they just now all of a sudden showing up for everybody when they never have before? So far it seems like Meraki’s stance on this issue is “Well this is how it’s always been and this is expected behavior.” Does that mean for all these years that the dashboard has been displaying easily identifiable names instead of MDNS names that it was exhibiting unexpected behavior? Why is Meraki not looking into why this admittedly widespread problem came about in the first place and help us find a solution to the root cause of this change in behavior on the dashboard? And I don’t mean come up with workarounds. I mean find out what actually broke or changed in the first place and fix it.
... View more
I recently deployed MR33 APs on a network using Cisco 2960X PoE switches. I set the SmartPort role of the ports connected to the APs to the "Access Point" role. The switch periodically checks to make sure the proper roles are applied to match the connected device. The SmartPort function of these switches is seeing the APs advertised as a switch and is recommending to apply the "switch" SmartPort role to the port the AP is connected to. Has anyone else using Meraki APs connected to Cisco switches seen this? Just trying to figure out if this is a bug in the SmartPort detection algorithm or a bug in the LLDP advertisement of the AP. I have 20 MR33 APs connected across 3 switch stacks made up of these 2960X 48-port switches. Seeing the same behavior on all of them.
... View more