We're testing out a vMX100 in Azure and so far everything seems good. The only issue I've ran into so far is that as of right now Azure is having a required maintenance to have all Azure VMs redeployed, and the vMX100 VM is on the list of impacted resources. The problem is, I can't redeploy the VM because of the application lock set on the resource group created with deployment, and that lock can't be deleted (even using PowerShell or Azure CLI) because it's controlled and owned by the system application.
Has anyone else ran into this issue? I'm curious if the planned maintenance even if left to be completed by Microsoft will allow the VM to be redeployed.
I think you'll have to open a case with Meraki support to get an answer to that one.
How has your experience been with the vMX in Azure? I'm considering it for use in an upcoming project. Did you ever get an answer to your original question? Terry
@Terry_Grant I've been very pleased with the vMX in Azure. Throughput has been great between our on-prem MX450's and the vMX. We run about $150/month in cost for the vMX.
The one thing I will note is that the documentation on initial Azure deployment is really lacking. You're better off following the info in this thread here: https://community.meraki.com/t5/Security-SD-WAN/vMX100-Azure-Cloud/m-p/1304#M281
I know this is an old thread however considering the documentation is still lacking / has missing steps I wanted to post the process here to save someone else hours for a 25-minute task.
The steps below are Azure specific, it'll be slightly different for AWS. There are also some notes about common errors that you may run into, along with some steps to correct them.
Hope this helps others save time and fills in the gaps.
Just an update as support seems to be using this tech note as the way to fix things. We updated the firmware on our vMX100 this morning and it fried it. When following the process above we ran into several issues.
In step 2/2 when we tried to stop the VM it was throwing a message about deny assignments. I finally just skipped this step.
In step 2/5, in order to delete the app you have to select the link for the app and then you will get a delete icon.
I would also suggest that you capture the config screen for your VM prior to going through this process so that you can remember some of the configuration items when you recreate the VM.
I hope this helps. Many thanks to James-VetaTek for the write up.