| title | description | ms.topic | ms.author | ms.date |
|---|---|---|---|---|
Deploy and configure Azure VMware Solution |
Learn how to use the information gathered in the planning stage to deploy the Azure VMware Solution private cloud. |
tutorial |
tredavis |
10/02/2020 |
In this article, you'll use the information from the planning section to deploy Azure VMware Solution. If you haven't defined the information, go back to the planning section before continuing.
[!INCLUDE register-resource-provider-steps]
Use the information you gathered in the Planning the Azure VMware Solution deployment article:
Note
To deploy Azure VMware Solution, you must be at minimum contributor level in the subscription.
[!INCLUDE create-avs-private-cloud-azure-portal]
Note
For an end-to-end overview of this step, view the Azure VMware Solution: Deployment video.
Important
If you left the Virtual Network option blank during the initial provisioning step on the Create a Private Cloud screen, complete the Configure networking for your VMware private cloud tutorial before you proceed with this section.
After deploying Azure VMware Solution, you'll create the virtual network's jump box that connects to vCenter and NSX. Once you've configured ExpressRoute circuits and ExpressRoute Global Reach, the jump box isn't needed. But it's handy to reach vCenter and NSX in your Azure VMware Solution.
:::image type="content" source="media/pre-deployment/jump-box-diagram.png" alt-text="Create the Azure VMware Solution jump box" border="false" lightbox="media/pre-deployment/jump-box-diagram.png":::
To create a virtual machine (VM) in the virtual network you identified or created as part of the deployment process, follow these instructions:
[!INCLUDE create-avs-jump-box-steps]
If you didn't define a virtual network in the deployment step and your intent is to connect the Azure VMware Solution's ExpressRoute to an existing ExpressRoute Gateway, follow the steps below.
If you've already defined a virtual network in the deployment screen in Azure, then skip to the next section.
[!INCLUDE connect-expressroute-to-vnet]
The jump box is in the virtual network where Azure VMware Solution connects via its ExpressRoute circuit. In Azure, go to the jump box's network interface and view the effective routes.
In the effective routes list, you should see the networks created as part of the Azure VMware Solution deployment. You'll see multiple networks that were derived from the /22 network you defined during the deployment step earlier in this article.
:::image type="content" source="media/pre-deployment/azure-vmware-solution-effective-routes.png" alt-text="Verify network routes advertised from Azure VMware Solution to Azure Virtual Network" lightbox="media/pre-deployment/azure-vmware-solution-effective-routes.png":::
In this example, the 10.74.72.0/22 network was input during deployment derives the /24 networks. If you see something similar, you can connect to vCenter in Azure VMware Solution.
Log into the jump box you created in the earlier step. Once you've logged in, open a web browser and navigate to and log into both vCenter and NSX-T admin console.
You can identify the vCenter, and NSX-T admin console's IP addresses and credentials in the Azure portal. Select your private cloud and then in the Overview view, select Identity > Default.
You use NSX-T to create new network segments in your Azure VMware Solution environment. You defined the network(s) you want to create in the planning section. If you haven't defined them, go back to the planning section before proceeding.
Important
Make sure the CIDR network address block you defined doesn't overlap with anything in your Azure or on-premises environments.
Follow the Create an NSX-T network segment in Azure VMware Solution tutorial to create an NSX-T network segment in Azure VMware Solution.
Go back to the Verify network routes advertised step. You'll see an additional route(s) in the list representing the network segment(s) you created in the previous step.
For virtual machines, you'll assign the segment(s) you created in the Verify advertised NSX-T segment step.
Because DNS is required, identify what DNS server you want to use.
- If you have ExpressRoute Global Reach configured, use whatever DNS server you would use on-premises.
- If you have a DNS server in Azure, use that.
- If you don't have either, then use whatever DNS server your jump box is using.
Note
This step is to identify the DNS server, and no configurations are done in this step.
If you plan to use DHCP on your NSX-T segment(s), continue with this section. Otherwise, skip to the Add a VM on the NSX-T network segment section.
Now that you've created your NSX-T network segment, you can do ONE of the following ways:
- Use NSX-T as the DHCP server for the segment(s) created. For this option, you want to create a DHCP server in NSX-T and relay to that server.
- Relay DHCP requests from the NSX-T segment(s) to a DHCP server elsewhere in your environment. For this option, only do the relay configuration.
In your Azure VMware Solution vCenter, deploy a VM and use it to verify connectivity from your Azure VMware Solution network(s) to:
- The internet
- Azure Virtual Networks
- On-premises.
Deploy the VM as you would in any vSphere environment. Attach the VM to one of the network segment(s) you previously created in NSX-T.
Note
If you set up a DHCP server, you get your network configuration for the VM from it (don't forget to set up the scope). If you are going to configure statically, then configure as you normally would.
Log into the VM created in the previous step and verify connectivity;
- Ping an IP on the Internet.
- Go to an Internet site via a web browser.
- Ping the jump box that sits on the Azure Virtual Network.
Important
At this point, Azure VMware Solution is up and running, and you've successfully established connectivity to and from Azure Virtual Network and the internet.
In the next section, you'll connect Azure VMware Solution to your on-premises network via ExpressRoute.
[!div class="nextstepaction"] Connect Azure VMware Solution to your on-premises environment