Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About MerakiJason
MerakiJason
Here to help
Member since Jan 12, 2021
May 6 2022
Community Record
13
Posts
2
Kudos
0
Solutions
Badges
May 6 2022
6:57 AM
Sadly no, I have asked again and again for logs to be taken and sent console logs but as far as I know they have not looked at them. Just kept getting the run around. Finally I insisted we be downgraded to 15.44 since I saw here it fixed the issues for several people and that's what finally stabilized the MX250. Now I still have issues I'm dealing with on MT switches so will probably have to downgrade those as well. I have mostly MX65 and MX68 in my Org and all those are running 16x with no issues at all. But everything that has been loaded in the 16x and 17x on my MX250 has caused nothing but problems. I suspect that is why all these bugs are not getting the attention by the development team since they apparently only affect some models. I think support is just downgrading people to get them stable again and the case closed and the bugs never get resolved, maybe that's why the same issues continue to appear in 17x. I'm not really sure.
... View more
May 5 2022
12:04 PM
16.16 proved to be extremely unstable for us on an MX250. Also had the same problems with 17.6 and I believe 16.5? Constant disconnects from the cloud. Would completely go out to lunch and have to be factory reset. We are finally stable after support locked us back to 15.44. I've been through 3 new RMA MX250s and done countless factory resets. What a mess. I have a bunch of MX65 and MX68 running 16x and they work fine but no way on earth I'd load this on a 250 after the last 3 weeks of problems I've been dealing with.
... View more
May 5 2022
12:03 PM
After all the same issues, we were finally able to get the MX250 unit to stay connected to the cloud long enough to download 15.44 and the MX seems to be stable now. Still having all kinds of DNS miscommunication errors on the various MT switches so we might be rolling back switch FW as well.
... View more
May 5 2022
12:00 PM
1 Kudo
16.16 proved to be extremely unstable for us on an MX250. Also had the same problems with 17.3 and I believe 16.5? Constant disconnects from the cloud. Woudl completely go out to lunch and have to be factory reset. We are finally stable after support locked us back to 15.44. I've been through 3 new RMA MX250s and done countless factory resets. What a mess. I have a bunch of MX65 and MX68 running 16x and they work fine but no way on earth I'd load this on a 250 after the last 3 weeks of problems I've been dealing with.
... View more
May 2 2022
6:46 PM
For me, I am using Meraki Optical SFPs to connect WAN and the switches to the MX250. I have all the same issues when plugged directly into he MX250 though. Having issues with MX16.16, 16.16.1 and 17.6. At this point spent quite a bit of time with Meraki TAC assistance, had 2 MX250RMAs and having the same issues. Very frustrating. Does Meraki not have the ability to enable some advanced debugging on the MX to figure out the issue? They told me they did but not seeing anything happen.
... View more
Apr 28 2022
5:44 PM
I just noticed 17.6 is available as a Stable Candidate so I'll push that now and see what happens. I don't recall what SFP I have in the WAN interface but its a 10GB Optical SM/MM SFP. Its an "official" Meraki SFP though
... View more
Apr 28 2022
4:08 PM
Interesting, I'm having what sound like similar issues with a new MX250 running MX16.16. I made a separate post because mine mostly is related to DNS errors but the MX250 also just looses connectivity to the dashboard. Any word on a bug yet?
... View more
Apr 28 2022
4:05 PM
I have had multiple Meraki Networks for a number of years but I recently got and MX250 for a larger site. First MX250. I'm having all kinds of issues that seem to be related to DNS and in addition the Appliance just goes off line for no reason even though you can still access and configure switches attached to the MX250 while its in this state so the internet connections fine. Got it hooked directly to a DIA Ethernet circuit. In addition to the MX250 going off line randomly, I get a DNS misconfigured message that cycles through the 5 switches attached. Clients on the network cannot resolve DNS requests but can get to the internet. Using google DNS at this point. My first one would just not connect back to the cloud so they send me a replacement. Replacement is doing the same thing a week later and they are sending me another replacement. This seems like a software bug and a bad one at that. Running MX16.16. No one has actually identified it as a bug so I'm hoping someone else is having these problems who can offer some advice.
... View more
Labels:
- Labels:
-
Other
Jan 14 2021
1:15 PM
Thanks for your assistance! Your solution was what I ended up going with.
... View more
Jan 14 2021
1:10 PM
1 Kudo
Thanks for all the help and advice! In the end I had to do the following- Organization>Create Network Templates 1-Create a new combined network Template named anything you want 2-Split the New Network Template I just created which then made 5 separate Appliance, Wireless, Switch, Cellular, Environmental templates appear 3-Delete Appliance and Wireless Templates (since I already had those attributes in my template) 4-Select Switch, Cellular, Environmental templates and the Existing Legacy Template 5-Select Combine Network Templates and use same name as used before. Save The root issue was that the existing template was created before Environmental existed so it did not contain that attribute. I also went ahead and added Switch and Cellular just to have them in there if I ever need them. Now all I do is unbind the network in question, assign the sensor then go back in and bind that network to the template again and it works.
... View more
Jan 13 2021
5:29 AM
Thanks for all the replies so far. The Template is already set to Network Type combined and I'm still unable to add the site back, even if I remove the sensor from the network. I've got 2 cases open with Meraki support now and I'm being told different things, neither of which work. I'd tend to agree the Templates seem to be overly complicated but I have 30 sites so it makes it easy if I need to change wireless settings or make firewall changes. I'm in a pinch because for whatever reason, when you remove a Network from a template it does not keep all the attributes it inherited from the template so I have a site now that is impacted.
... View more
Jan 12 2021
12:37 PM
All of my networks are bound to a template. I recently got some MT sensors for a couple sites. meraki support told me to unbind the network from the template, add the sensor then bind it back to the template. I was able to complete the first 2 steps but it will not allow me to bind the network back to the template. I get an error stating "'Network X' cannot be bound to 'Template name Z' because they have incompatible network types.". Even if I remove the sensor and try to bind back I get the same error. Any ideas? Nothing from Meraki support. Thanks
... View more
My Top Kudoed Posts
© 2024 Cisco Systems, Inc.
