Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About Lonestarr
Lonestarr
Here to help
Member since Feb 17, 2021
Jul 1 2022
Community Record
7
Posts
0
Kudos
0
Solutions
Badges
I get that. That's essentially what Meraki support told us before. Problem is that we were having the issue at several sites every couple days for a couple weeks, then support suggested using Google DNS. We set some of the sites to use google and left the rest on Umbrella, expecting it to happen again and then we could determine if that was the solution (ie, if the Umbrella sites went down but the Google sites did not). But then it didn't happen again at all for about 2 months, so for the sake of maintaining consistency across our networks we changed them all back to Umbrella. Today was the first time since then that it's happened, and it was only one site. We have 160+ sites, and only about 10-15 or so use AT&T fiber. All 160+ use Umbrella for DNS, but only the AT&T fiber sites have had this issue. That's why I'm thinking it's more something to do with AT&T's modem/router than with the Umbrella DNS settings, but of coarse AT&T tech support is no help if you can even get ahold of someone who understands what you're trying to tell them.
... View more
I'm not exactly sure how to answer that. The WAN link on the MX is set to dynamic, so that uses whatever DNS is assigned by the ISP - in the case of these AT&T sites that seems to be the provided modem/router, since the WAN IP address is public but the DNS address is 192.168.1.254. The MX acts as a router and gateway and DHCP server for each vlan - data, voice, secure wifi, management - and each of these is configured to use Umbrella for DNS.
... View more
The MRs show the same DNS issue at the same time as the switches, and yes they are on the same management vlan. The MX remains up and green and never shows the DNS issue.
... View more
We have 160+ offices around the country, all using the same basic setup - MX with MS switch(es) and MR AP(s). No other hardware anywhere on our network, and every site is built using the same template so only the subnet info is different. We are finding a persistent issue that only seems to be affecting sites using AT&T fiber as the ISP (we use several different ISP's based on whatever is available in the area). Every once in a while, seemingly random, the switch will go into Disabled switch (bad DNS) state. This tends to happen overnight when the office is closed, so it's not due to any kind of traffic or changes on the network. It will stay like this until we reboot the MX - that's the only thing we've found that fixes it but it does fix it every time. We've discussed this with Meraki support and their suggestion was to change our management vlan settings to use Google DNS (we currently use Umbrella). The problem appears randomly so we can't reproduce it, but it did happen today and changing to Google DNS did not fix it. The modem at these sites is the BGW320-505. It does not allow a true bridge mode, but we have disabled packet filtering and enabled IP passthrough mode. Even so, the DNS it gives the MX is 192.168.1.254 and apparently this cannot be changed on this modem. Maybe this is causing an issue? Has anyone seen this issue? Is this a known problem with these AT&T modems, and if so is there a solution? This tends to happen overnight so there's no users generating traffic that could be triggering the error state, and the same configuration at 100+ other offices never results in this problem, it is only the offices with AT&T fiber.
... View more
May 26 2022
7:01 AM
Has Meraki produced documentation for this yet? We just turned on a number of alerts for our network and are tweaking them to see what works for us. I read this thread earlier and we decided to get weekly alerts. For this week we have 3 alerts at 3 different offices. One is here at our HQ and I was able to find who it is and verify there was no issue. But the other two are clear across the country, and one of them is on wifi so I can't cycle the port as suggested above. How do we troubleshoot these alerts to determine whether it's a false positive or a legit concern, without physically going to the device and looking for vmware (which shouldn't be on it based on group policies anyway)?
... View more
Feb 17 2021
9:34 AM
Good non-answer from Meraki 😕 I've been using the dashboard for months and this only started recently. There's no way it's all from cache data, especially when we are clearing our cache and it happens again not long after. And they recommend using Chrome, that's what I'm using and having issues with - and I'm generally only having issues with the Switches page. Oddly enough, shift+F5 works for me as well. I just don't see how this became an issue only recently when I've been using the dashboard for months without a problem.
... View more
Feb 17 2021
7:18 AM
I've been noticing the same thing for at least a couple weeks now. Doesn't matter what browser I use. For me it seems it's usually the Switches page that goes blank, though once or twice the entire dashboard went blank. Refreshing the page doesn't help, but clearing the cache usually does. Or just open a different browser. I have about 200 networks to monitor so I'm in the dashboard all day every day, and it gets quite annoying. I'm hoping they are noticing and working on fixing it.
... View more
© 2024 Cisco Systems, Inc.
