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 KarbonX1
KarbonX1
Here to help
Member since Aug 23, 2017
06-19-2023
Community Record
19
Posts
8
Kudos
2
Solutions
Badges
01-25-2022
07:46 AM
I use 10.238.0.0/24 at home, so I worked the subnets around that: 10.224.0.0/13 10.232.0.0/14 10.236.0.0/15 10.238.1.0/24 10.238.2.0/23 I've given it time, connected twice, have "Allow local LAN" access enabled in the client, yet a route still gets added with higher priority pointing my subnet to the Anyconnect. 10.238.0.0 255.255.255.0 On-link 10.238.0.126 306 10.238.0.0 255.255.255.0 On-link 10.238.3.103 2 10.238.0.1 255.255.255.255 On-link 10.238.0.126 51 I could forcibly create a route with a higher priority, but wondering why its doing this at all. Am I missing something?
... View more
09-14-2020
07:14 AM
2 Kudos
For anyone curious, I spent a few hours troubleshooting over the weekend. I wrote a long post on my troubleshooting process that failed due to timeout, so this is the short version. Basically, I had a VPN firewall rule set to allow syslog traffic with everything else denied from many of my branches, as they don't need to access anything and its just for administration. But I stupidly set that to enable logging, so every time a flow message was sent, that then created another firewall allow message, and so on. This for some reason only affected the ones that had been on 15.x, but once I narrowed down the VPN as the source of the issue, I just had to identify what about the VPN was the issue. Once I turned off the logging, utilization went down to less than 10% after a couple hours, Yay! So, moral of the story is, don't enable logging on VPN firewall rules for allowing syslog traffic.
... View more
09-10-2020
01:08 PM
2 Kudos
I planned to downgrade but wanted to know if it was just bad reporting in the summary page, then support asked me not to downgrade so they can troubleshoot and get a differential. I'm not personally on site at these locations, but haven't had any complaints that the network is super slow. That's why I thought maybe it was a bug in the summary page reporting.
... View more
09-10-2020
01:06 PM
OK, that is good to know. Hopefully I don't have a bad batch of MX devices. Thanks for confirming!
... View more
09-10-2020
01:05 PM
1 Kudo
Honestly, I only upgraded due to having 3 different MX67 units that bricked when trying to bring up as a new adopted device, and support said that the factory firmware was conflicting with the default version at the time (14.42 at the time I think) when they would first come online. They said I should put all of them on a test network one by one and make them update to 15.x to make sure they wouldn't brick when sent out to the site. Then I wanted to keep them consistent so I upgraded some of the other sites that were on a 14.x version. I do not have HTTPS inspection turned on, at least that I know of. I've yet to see that exposed in the dashboard. I'll probably just downgrade to 14.53, but wanted to know if this was more widespread. I have noticed a lot of content filtering blocks lately from DNS over HTTPS (included in proxy avoidance and anonymizers) and wondered if that is part of the issue. Here is a comparison of two MXs with almost identical setup. The bottom one was upgraded to 15.33 on July 31st and nothing in the config was changed at that time.
... View more
09-10-2020
08:31 AM
I have about 15 MX67s currently on 15.35, and all of them show on the summary page at 100% utilization constantly. A few of them were on a 14.x firmware previously and as you can see, the utilization became pegged at 100% when going from 14.x to 15.33 on July 31st. No improvement to the issue on 15.34 or 15.35. Support claims this is not happening elsewhere, and is trying to say that my client count is too high, wants me to disable features, etc. At first they said it was not really at 100%, then came back and said it was. Is this happening to anyone else out there? I'd like to know if I need to escalate this to my SE or if I should just downgrade and hope they fix it at some point.
... View more
08-06-2019
12:53 PM
This thread is old, but figured I would post here anyways since it was in question. https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/Troubleshooting_Group_Policies Confirms it is in fact stateless (and is stupid IMHO)
... View more
04-24-2018
12:24 PM
I know this is an older thread, but just in case is there a reason you cant put a switch in between the MX and the modem so you can connect more than one device at a time?
... View more
03-21-2018
03:33 PM
@BRYANQ1234Did you just send the syslogs to a receiver and then export, and manually import into CAS, or did you setup the log receiver VM/docker image to handle the syslog directly?
... View more
03-19-2018
12:22 PM
2 Kudos
I have a workaround to that, but its not exactly what Meraki supports. Meraki says to uninstall the agent on the end device so that it doesn't attempt to connect any longer. My workaround is to create a new SM network in the dashboard called decommissioned, then move all decommissioned clients from the production SM network into the decommissioned SM network. Then you can delete the decommissioned SM network from the dashboard and the devices won't have a valid network to connect to anymore. Again not the best option, but seems to work for me.
... View more
10-31-2017
08:14 PM
**FYI to everyone** Do not upgrade the vMX to any 12.x or 13.x firmware. Apparently it is actually running a 14.x firmware, and so the upgrade will kill it. I had to redeploy mine to resolve.
... View more
10-31-2017
03:32 PM
Brandon_Fox, you need the license to add the vMX. Then you can get the Auth keys.
... View more
10-31-2017
03:30 PM
Needs a new resource group or one without any resources in it. Also, needs to be deployed in a subnet that is different than the VMs due to the way IP forwarding works so that all data passes through a layer 3 boundary and can be routed properly using the route table.
... View more
10-16-2017
07:50 AM
As an update for anyone wondering, we got the IP forwarding issue figured out and I am using the vMX successfully for the last few weeks now. Works just as expected.
... View more
10-16-2017
07:48 AM
Standard D2 v2 (2 vcpus, 7 GB memory) Its a managed virtual appliance, so there is no control over the sizing or any config at all. So there is some planning that has to go into deployment such as: - You cannot change DNS settings on NIC config, so has to use whatever vnet is set to. - Cannot shutdown from within azure - Can only delete entire resource group if you have to redelploy I am sure there was more, but those are what I can remember at the moment.
... View more
09-21-2017
01:38 PM
Yeah, I'm working with the engineering team to get the IP forwarding issue worked out.
... View more
09-21-2017
10:57 AM
1 Kudo
It's in beta now. I'm running it, but the S2S functionality isn't fully working yet so I can't truly test it until the MX team gets the fix done in Azure. They are a managed appliance, so you can't do anything to them except deploy as is.
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 4027 | 09-14-2020 07:14 AM | |
| 4312 | 03-19-2018 12:22 PM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 2 | 4027 | |
| 2 | 4113 | |
| 2 | 4312 | |
| 1 | 4115 | |
| 1 | 51130 |
