Meraki

Community
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

About JGrantB

Re: vMX install in Azure fails

by in Security & SD-WAN
‎Mar 26 2024 7:45 AM
‎Mar 26 2024 7:45 AM
I had only tried the DNS setting on the 'DNS Servers' on the VNet blade in Azure and only added 8.8.8.8. Meraki support has passed this off as an Azure problem but I am going to try setting the DNS on the local status page and see what happens. I also spotted in the deployment guide under (Re)deployment failure: A few common fixes for (re)deployment failures could be: • updating the VNET DNS settings <-- Already tried this • removing any special characters in the name of the vMX <-- I do have dashes in my naming convention so this might be the smoking gun. Thank you both for the suggestions! ... View more

vMX install in Azure fails

by in Security & SD-WAN
‎Mar 22 2024 5:28 PM
‎Mar 22 2024 5:28 PM
I have already engaged Meraki support but thought I would ping on the community too!   I am using the vMX Setup Guide for Microsoft Azure for reference. I have tried 7 deployments and they all failed. On three of them, I tried fix suggestions from Reddit/Meraki community posts and those are:   #1 Set the zone field property to 'None' #2 Used the Azure 'preview' portal #3 Set the DNS servers property on the VNet to 8.8.8.8   The error is the same on all 7 attempts I have made today, "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'. (Code: ResourceDeploymentFailure)" AND specifically, "OS Provisioning for VM '[myvmname]' did not finish in the allotted time."   The time to failure is approximately 22 minutes after I start the deployment. The deployments are all to US East Azure region & I am owner on the subscription.   Is there an alternative way to deploy the vMX in Azure?   ... View more
© 2024 Cisco Systems, Inc.