I can't say it's the exact same as we never looked at DNS and just focused on speed via iperf tests but we did find a known bug involving MS130Xs in certain scenarios causing slow uplink speeds. Ours was an MS130X uplinked to an MX75, the interim workaround was putting an MS130 (not X) in between. ... View more

It's not in the known issues list last I saw but this is a bug per support. We had to roll back to 18.211.3. I'd open a case so you get attached to the bug and get notification when it's fixed and increase its visibility. ... View more

While your symptom is a bit odd, when I have issues with paging and multicast on meraki, I enable the IGMP snooping querier on the relevant vlan and leave IGMP snooping enabled for the vlan. You should only need actual multicast routing if your broadcast needs to cross subnets. Overview of settings: https://documentation.meraki.com/MS/Other_Topics/Multicast_Overview%2C_Configurations%2C_and_Best_Practices ... View more

There is generally a small lag, but I've not seen nor do I see at quick glance anything like that for me right now. Have you verified that the time zone of the network matches your PC? That would explain some discrepancy. If it does match, do relevant logs for the missing time show up eventually? My only suggestions to resolve would be reboots followed by support. Perhaps a firmware update if you lagging there. ... View more

Those look like valid logs. If your system isn't parsing them properly you would have to take that up with them.  The only note I see on that page about formats says timestamps are required and the entry above does have that. I will point out that documentation page is for Firewalls and doesn't mention any compatibility with wireless or switch logs. The example you've provided is wireless.  The system may not support things besides firewalls.   In general, Meraki doesn't offer formatting options for their syslogs so your tool has to be the one translating them into something user friendly. ... View more

Can you provide a sanitized example of what you are seeing and what api calls you are using? ... View more

If the same sim card works in another MX, have you tried to factory reset the firewalls in question? Something could be gummed up in the firmware or config and that should clear it out. Otherwise I'd suggest calling support, they may be able to see more detailed diagnostics on sim card detection. There could be a bug they can identify and tell you if a different release may work. ... View more

The auth category on access points in event logs includes Splash authentication. That's where I would start. If you are authenticating against a radius or ldap server, there should be logs on that end as well that you may need to correlate. ... View more

If you want to explore outside of downtown the weekend before or after I'd say yes, but not for the actual convention, many of the hotels are very walkable. They will also almost certainly have shuttle buses available for the further ones. ... View more

Based on all of that it sounds like general connectivity is there. What you've done by turning off firewalls/ips/etc. would be the basic things I would say from a network perspective you can do without involving Meraki support. You are getting into where you might need to compare a working and non working packet capture or enable additional client or server side debugs. Can you telnet to port 443 and 80 from the remote offices successfully? ... View more

Can you ping the server in question from the remote sites? Can you access other items on the same subnet from the remote sites? Have you verified DNS is returning the proper IP? Have you tested trying to access via IP address? Those are all things I would want to know when troubleshooting. Depending on the answers I or others may be able to provide some other things to check. ... View more

I don't use them myself, but based on the documentation I've read, I don't believe clients are part of them. You can always call support and verify the behavior you are seeing with them. They will be able to exactly see your dashboard and look at an example you provide them. ... View more

Nothing automatically syncs between networks unless you use templates. All networks just means all SSIDs in that specific Meraki Network ... View more

Clients and their white/blacklist status is a per network item. You would have to add/update the same mac in all 12 networks at once for it to be consistent  or keep some sort of primary network where you do the add/deletes and then config sync each time. ... View more

Each MX will only need 1 IP for each ISP and then the shared VIP IP between both. ... View more

Yes generally on most ISPs you will need a block of 5 or a /29 if talking in subnets. Some ISPs do sell them individually and you could get away with just 3. Generally that's smaller, rural ISPs, but it does exist. I always go with 5 so I have extras available for vendor needs. ... View more

The schedule upgrades tab current firmware column should show a firmware version matching the version on the device status pages.   The overview tab only shows every current version available it does not mean those versions have been applied to your networks.       If you are saying the schedule tab and the device status show different versions AND it's not an instance where the device doesn't support the latest version, then there is some sort of GUI bug and you should open a support ticket. ... View more

You'd setup a group policy with the appropriate firewall rules to apply to it and apply it to that VLAN on the MX. Whether you want to connect the cable directly to the MX or trunk it to your switch and put an access port there is more a physical design consideration. It only being on the MX does provide a slight bit more security as you can prevent the VLAN from existing on the switches. No matter what the vlan does have to have it's gateway be on the MX for this to work properly. It can't be a static route to a L3 switch for example.   Group Policy info: https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Creating_and_Applying_Group_Policies ... View more

I'm not sure where that URL is from (perhaps an older version of the api?) but the API to update radius for Wireless is this one: https://developer.cisco.com/meraki/api-v1/update-network-wireless-ssid/   You have to do it per SSID. Org Wide Radius does exist but only for wired devices at this point.   ... View more

I don't work in a lot of low bandwidth environments, so generally the default policies seem to suffice these days for me.  However I'm sure some others here will have thoughts. Here is an older thread on the subject: https://community.meraki.com/t5/Security-SD-WAN/QoS-for-Teams/m-p/102045#M25647 It's technically relating to MXs but many of the same ideas would apply   ... View more

I presume this also exists in AWS, but I know azure keeps stats on traffic utilization that may be helpful for calculating throughput used. ... View more

I've seen zero indications of new models coming, including as a partner. I would also add that the recent software changes have come with a goal of increasing the performance of the existing models and presumably extending their lifespan.   I would ask your account rep this question as its highly unlikely anyone who knows can comment on an open forum. Although I'm definitely all ears as well if someone would! ... View more

The 9800-40 is an older model for the previous generation of 9800s. 9800-40s are monitorable: https://documentation.meraki.com/Cloud_Monitoring_for_Catalyst/Getting_Started/Cloud_Monitoring_for_Catalyst_Wireless_Requirements The CW9800M is supposed to be monitorable per the Cisco Data Sheet: https://www.cisco.com/c/en/us/products/collateral/networking/wireless/wireless-lan-controllers/catalyst-cw9800m-wireless-controller-ds.html But as best I'm aware that feature is not live yet. You may be able to get info from your account team on an ETA. If you are looking at purchasing, I would definitely get the CW model and then just waiting to onboard to the dashboard once that's available. The 9800-40 has an announced End of Sale date and the CWs are the recommended migration path.   ... View more