Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About murdz112
murdz112
Comes here often
Member since Feb 20, 2020
Mar 15 2020
Community Record
6
Posts
0
Kudos
0
Solutions
Badges
Feb 21 2020
2:10 PM
Hi Philip, Everything was blown away. I set it up as you said. It didn't work. You can not create the resource group without adding a vNET. When launching the managed app you can not associate the app to an existing resource group with a VNET defined. This is explained quite clearly in the Meraki instructions. Which will post again as it contravenes what you're trying to tell me. Azure Setup Before You Begin You must have the following before you begin: An Azure virtual network and virtual subnet on a resource groups separate from the resource group you will be creating to host the vMX. To find more information about this, please click here. Note: Your virtual network must be in a separate resource group from the one hosting your vMX. If you assign the vMX to a resource group that already contains a virtual network/virtual subnet, you will not be able to deploy the vMX. Is anyone who is running a vMX successfully in Azure able to chime in?
... View more
Feb 20 2020
8:00 PM
Hi Philip, See below screenshots. Tried wiping azure config all away. Created new Resource Group with a VNET inside then provisioning vMX100 to be apart of that resource group. No dice gives an error. Your thoughts?
... View more
Feb 20 2020
5:25 PM
Hi Philip, So you suggest deleting the vMX managed app. When redeploying what resource group should I put it into?
... View more
Feb 20 2020
1:48 PM
But following the Meraki documentation it explicitly states you can't have the vMX on the same VNET as your Servers VNET. I have tried putting them in the same VNET and azure errors out (I think the managed app locks down the VNET it deploys so you can't make any changes to it)
... View more
Feb 20 2020
12:43 PM
From the Meraki article. I took it that the vMX and server had to be on different vNETS infact I tried creating them on the same and the managed app won't allow this. Azure Setup Before You Begin You must have the following before you begin: An Azure virtual network and virtual subnet on a resource groups separate from the resource group you will be creating to host the vMX. To find more information about this, please click here. Note: Your virtual network must be in a separate resource group from the one hosting your vMX. If you assign the vMX to a resource group that already contains a virtual network/virtual subnet, you will not be able to deploy the vMX.
... View more
Feb 20 2020
4:33 AM
Hi Team, I have used the vMX100 Setup Guide for Microsoft Azure found below on the Meraki website: https://documentation.meraki.com/MX/Installation_Guides/vMX100_Setup_Guide_for_Microsoft_Azure Been bashing my head against a wall trying to get connectivity from my DC in the Sydney branch office to the DC in Azure. My network configuration is as follows: Sydney Branch Office Network MX100 192.168.0.0/24 - Office LAN 192.168.0.8 - SydneyDC vMX100 VNET vMX100 10.10.0.0/16 - Supernet 10.10.0.0/24 - vMX100 Subnet 10.10.0.4 - vMX LAN IP Infrastructure VNET 10.100.0.0/16 - Supernet 10.100.0.0/24 - Infrastructure Subnet 10.100.0.4 - AzureDC IP I have the below networks set as "Local Networks" in the VPN settings of the vMX in Azure: 10.100.0.0/16 10.10.0.0/24 On the MX100 in Sydney, I can see it has 10.100.0.0/16 in the route table as well as 10.10.0.0/24. I can ping the vMX100 IP 10.10.0.4 from the MX100 appliance without any issues. So the site-to-site VPN is working fine. I have created a route table in Azure with the following settings: Route: 192.168.0.0/24 Next Hop IP: 10.10.0.4 Subnet: 10.100.0.0/24 The route table is associated with the resource group in which the AzureDC resides. Below are some screenshots of my config in Azure. Meraki support are no help at all. Have tried a myriad of combinations and other 3rd party documentation online to no avail. Is anyone able to assist in getting connectivity to the AzureDC host from my sydney branch office?
... View more
© 2024 Cisco Systems, Inc.
