About KarbonX1

KarbonX1 · ‎08-06-2019

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)

KarbonX1 · ‎04-24-2018

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?

KarbonX1 · ‎03-21-2018

@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?

KarbonX1 · ‎03-19-2018

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.

KarbonX1 · ‎10-31-2017

**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.

KarbonX1 · ‎10-31-2017

Brandon_Fox, you need the license to add the vMX. Then you can get the Auth keys.

KarbonX1 · ‎10-31-2017

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.

KarbonX1 · ‎10-16-2017

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.

KarbonX1 · ‎10-16-2017

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.

KarbonX1 · ‎09-21-2017

Yeah, I'm working with the engineering team to get the IP forwarding issue worked out.

KarbonX1 · ‎09-21-2017

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.

KarbonX1

Community Record

Badges

Re: L3 firewall vs group-policy L3 firewal

Re: Meraki Insight

Re: Meraki Logs into Office 365 Cloud App Security

Re: Removing Windows devices from SM........they keep coming back

Re: vMX100 Azure Cloud

Re: vMX100 Azure Cloud

Re: vMX100 Azure Cloud

Re: vMX100 Azure Cloud

Re: vMX100 Azure Cloud

Re: vMX100 Azure Cloud

Re: vMX100 Azure Cloud

Re: Removing Windows devices from SM........they keep coming back

Re: Removing Windows devices from SM........they keep coming back

Re: vMX100 Azure Cloud