Alternatively, if you would like to add a vMX to your network, please add a vMX license to your org and visit this page again.Īs you can see, you need to add a license for a vMX.Īs soon as you did it, this message is different: If you add one we can help you configure it. There are no Meraki devices in this network. Please note: you cannot use a “combined” network for Azure vMX, you must use a “Security appliance” network only.Īt that point, you should have this message: Then click on “Create network” without adding any device. Click on: Organization > Create NetworkĮnter a network name and choose “Security appliance” as network type.
So, let’s see this step in details first:įirst, create an empty network on your Meraki Organization. To generate it, you first need to create the vMX into the Meraki dashboard. To be able to install the vMX100 VM into Azure, you will need an authentication token from the Meraki dashboard. I give more details on this point in the last part of this post. Client VPN is supported on the vMX, but you must use split-tunneling to access to the Internet with a connected client.Your branch or remote offices need to make split-tunneling VPN: Internet traffic go to the branch/remote office local Internet access, and only Azure remote networks are routed through the VPN. Full-tunnel site-to-site VPN mode is not possible.You cannot use the Meraki vMX as a gateway into Azure.The vMX can only play the role of VPN concentrator on Azure.
The Meraki vMX will work in one-armed concentrator mode only! No NAT mode available.Moreover, to deploy the vMX into Azure, you need the Meraki authentication token available through the Meraki dashboard only when the vMX is existing. The vMX is not available into the Meraki dashboard before you enter a Meraki license. You cannot test anything before entering the license. You need a Meraki valid license to deploy the Meraki vMX100.Here are some prerequisites and good points to know before starting with the Meraki vMX100 on Microsoft Azure cloud: Here are some tips and tricks to save you time. The setup process on Azure is relatively simple, however, I lost quite a lot of time on basic issues because the documentation provided by Cisco is not 100% accurate.
Recently, I was involved into a project where we had to deploy a Cisco Meraki vMX100 into Microsoft Azure cloud and build site-to-site and clients VPNs.
0 kommentar(er)
