Deployment of Azure VMware Solution

To deploy an Azure VMware Solution private cloud, you must have an Azure subscription associated with a Microsoft enterprise agreement.

I begin logged into the Azure Portal with access to such a subscription. As a first step, I will request AVS host quota be applied to my subscription, in the region into which I intend to deploy my private cloud.

AVS hosts are dedicated, bare-metal servers, and there are a finite number available at any given time. Requesting host quota registers my intent to consume a given number of these hosts. You are not billed for these hosts until they are deployed. It can take up to five business days for the hosts to be allocated, so it is important to plan accordingly.

Start the host quota request process with the following steps:

  1. In the Azure portal, expand the upper menu control ≡
  2. Select Help + Support
  1. Click Create a support request
  1. On the Basics tab, click in the Summary field
  1. Type “Need capacity
  2. Click the Issue type drop-down
  3. select Technical
  4. Next to Service, select All services
  5. Click the Service type drop-down
  6. Type “azure vmware solution
  7. Select Azure VMware Solution
  1. Click the Problem type drop-down
  2. select Capacity Management Issues
  3. Click the Problem subtype drop-down
  4. select Customer Request for Additional Host Quota/Capacity
  1. Click Next: Solutions >>
  1. Click Next: Details >>
  2. Click in the Description field
  3. Type “Production” and hit enter
  4. Type “West US” and hit enter
  5. Type “3 hosts
  6. Click Yes next to Share diagnostic information?
  7. Click the scroll bar to scroll down
  8. Next to Preferred contact method, click Email
  9. Click the scroll bar to scroll down
  10. Click Next: Review + create >>
  11. Click the scrollbar to scroll down and review the request
  12. Click Create

You will receive an email within five business days informing you that host quota has been assigned. We will proceed assuming this has been completed.

Next, we need to confirm that the Microsoft.AVS resource provider in registered in your subscription.

  1. Click Home
  2. Click on the AVS subscription
  3. Click the scroll bar in the Resource Menu to scroll down
  4. Click Settings > Resource providers
  5. Click the Filter by name bar
  6. Type “Microsoft.AVS” and hit enter

The view will filter. Note that the Microsoft.AVS provider is already registered. If status was “Unregistered,” we could register it by clicking on the Microsoft.AVS row, then clicking Register.

Next, we will create a new Azure resource group for our AVS private cloud and related objects.

  1. Click Home
  2. Click Create a resource
  3. Click in the Search services and marketplace box
  4. Type “Resource group” into the search bar
  5. Select the “Resource group” item
  6. Click Create
  1. The Subscription will be pre-populated. Click into the “Resource group” field
  2. Enter “<your resource group name>-RG” for the name
  3. Click the Region drop-down
  4. Click the scroll bar
  5. Select Location
  6. Click Review + create
  7. Click Create
  8. When prompted that the resource group has been created, click Go to resource group

Deploy the AVS private cloud

Now we will deploy the AVS private cloud.

  1. From the resource group view, click Create
  2. Click in the Search services and marketplace box
  3. Type “Azure VMware Solution” into the search bar
  4. Select the “Azure VMware Solution” item.
  5. Click Create
  1. The “Create a private cloud” wizard opens. The “Prerequisites” tab reminds us of the need to have host quota assigned and a /22 network available. Click the scroll bar to view the full content.
  1. Click Next: Basics >.
  2. Subscription and resource group will be pre-populated with the appropriate values. Click into the Resource name field
  3. Type “Resource Name
  4. Click the dropdown next to Location
  5. Select Location
  6. Click the dropdown next to Size of host
  7. Select AV36 Node

Leave Number of hosts set to 3

  1. Click the scroll bar to scroll down
  2. Click into Address block for private cloud field
  3. Enter “<IP>/22”
  4. Click Review + create
  1. Review the settings specified. Click the scroll bar to scroll down
  2. Click Create. The deployment process can take a few hours to complete. Through the magic of editing, we have reduced this somewhat.
  3. When the deployment is complete, click Go to resource

Connect the AVS private cloud to a new Azure virtual network

We can see now that our AVS Private cloud has been deployed. Now, we need to connect it to an Azure virtual network so that we can access vCenter and NSX Manager from a jumpbox that we will deploy into that virtual network. We will create a new Azure virtual network and connect our AVS private cloud to it with the Azure vNet Connect feature. We will assign non-overlapping IP space for this new virtual network and create three subnets within it.

  1. Under Manage, click Connectivity
  2. The Connectivity pane will open to the Azure vNet connect tab. Under the Virtual network dropdown, click Create new
  1. Leave the default VNet name but click on the pre-populated address range of<IP>/16 to edit it.
  2. Enter <IP>/24
  3. Click in the empty field under Subnet name
  4. Enter GatewaySubnet
  5. Click in the Address range field
  6. Enter <IP>/27. This subnet will be used by the Virtual Network Gateway that will be deployed to connect the new VNet to the ExpressRoute circuit supporting the AVS private cloud.
  7. Click in the empty field under GatewaySubnet
  8. Enter AzureBastionSubnet
  9. Click the Address range field
  10. Enter <IP>/27. This subnet will be used for Azure Bastion connectivity to a jumpbox VM.
  11. Click in the empty field under AzureBastionSubnet
  12. Enter Management
  13. Click the Address Range field
  14. Enter <IP>/27. This subnet will be used for the jumpbox VM we deploy later.
  15. Click OK
  16. Click Save
  17. The new VNet and supporting objects will be deployed. When deployment is complete, click the Resource group link to <your resource group name-RG>

Access vCenter from the connected Azure VNet

Next, we will deploy Azure Bastion and a Windows 10 VM to use as an administrative jumpbox, then log into the Windows 10 VM with Bastion to access vCenter.

  1. From the resource group view, click Create
  2. Click in the Search services and marketplace box
  3. Type “Bastion” into the search bar
  4. Select the Bastion item.
  5. Click Create
  1. Subscription and resource group will be pre-populated with the appropriate values. Click the Name field
  2. Enter “<name-Bastion>
  3. Click the Region dropdown
  4. Click the scroll bar to scroll down
  5. Select Region
  6. Click the Tier dropdown
  7. Select Basic
  8. Click the Virtual network dropdown
  9. Select <name-vnet>
  10. The Subnet value will auto-populate with AzureBastionSubnet. Click the scroll bar to scroll down.
  11. Click Review + create
  1. Review the settings specified and click Create
  2. When deployment is complete, click the Resource group link to <name-RG>.
  3. Click Create
  4. Click in the Search services and marketplace box
  5. Type “Windows 10” into the search bar
  6. Select the Microsoft Windows 10 item.
  7. Click Create
  1. On the Basics tab, Subscription and Resource group will be pre-populated. Click in the Virtual machine name filed
  2. Enter “<name-Jumpbox>
  3. Click the Region dropdown
  4. Click the scroll bar to scroll down
  5. Select Region
  6. Click the scroll bar to scroll down
  7. Click in the Username field
  8. Enter “avsadmin
  9. Click in the Password field
  10. Enter “********”
  11. Click into the Confirm Password field
  12. Enter “********”
  13. Next to Public inbound ports, select None. We will use Azure Bastion to connect to the VM.
  14. Click the scroll bar again to scroll down
  15. Check the box next to “I confirm I have an eligible Windows 10 license with multi-tenant hosting rights.”
  16. Click the scroll bar to scroll back to the top
  17. Click the Networking tab
  18. Click the Public IP drop-down
  19. Select None
  1. Click Review + create
  2. Scroll down to review settings.
  3. Click Create
  4. When deployment is complete, click Go to resource
  5. Click Connect
  6. Select Bastion
  7. Click Use Bastion
  8. Click the Username field
  9. Enter “avsadmin
  10. Click the Password field
  11. Enter “********
  12. Click Connect

A new tab will open, and the Windows VM desktop will render in that open tab. We have skipped the first-time setup wizard and skipped to an open Edge tab.

  1. Click the browser tab to switch back to the Azure Portal tab
  2. Click Home
  3. Click AVS Private Cloud name
  4. Click Manage > Identity
  5. Click the Copy to Clipboard button next to the vCenter credentials > Web client URL field
  1. Click the browser tab <name-Jumpbox> to switch back to your Windows 10 desktop
  2. Right-click into the address bar
  3. Click Paste
  4. Press Enter
  5. Click Advanced
  6. Click Continue to IP (unsafe)
  7. Click LAUNCH VSPHERE CLIENT (HTML5)
  8. Click Advanced
  9. Click Continue to (vSphere hostname)
  10. Click the browser tab to switch back to the Azure portal
  11. Click the Copy to Clipboard button next to vCenter credentials > Admin password
  12. Click the browser tab <name-Jumpbox> to switch back to your Windows 10 desktop
  13. Click in the username field
  14. Type “cloudadmin@vsphere.local
  15. Right-click in the Password field
  16. Click Paste
  17. Click Login
  18. Click to expand SDDC-Datacenter
  19. Click to expand Cluster-1
  20. Click on the first ESXi host to review summary

Connect an on-premises data center to the AVS private cloud

Now we have confirmed that AVS private cloud components were successfully deployed, and that we can access vCenter from our connected VNet. Next, we will step through the configuration of ExpressRoute Global Reach to allow connectivity to AVS resources from our on-premises data center.

The following steps assume that you have an existing ExpressRoute circuit connecting your on-premises datacenter to Azure, and that the party responsible for that ExpressRoute circuit can provide you with the Resource ID and an authentication key.

  1. Return to the tab open to the Azure portal
  2. click Manage > Connectivity
  3. Click the ExpressRoute Global Reach tab
  4. Click Add
  5. Right-click into the Enter an ExpressRoute circuit ID field
  6. Select Paste to paste in the ExpressRoute Resource ID
  7. Right-click in the Authorization key field
  8. Select Paste to paste in the Authorization key.
  9. Click Create
  1. When the cloud connection completes successfully, click Manage > Identity. We will log into vCenter again, this time from our on-premises VM.
  2. Click the Copy to Clipboard button next to the vCenter credentials > Web client URL field
  3. Click + to open a new Edge tab
  4. Right-click in the address bar
  5. Select Paste
  6. Hit Enter
  7. Click Advanced
  8. Click Continue to IP (unsafe)
  9. Click LAUNCH VSPHERE CLIENT (HTML5)
  10. Click Advanced
  11. Click Continue to (vSphere hostname)
  12. Click in the Username field
  13. Enter “cloudadmin@vsphere.local
  14. Click to switch back to the AVS Identity tab
  15. Click the Copy to Clipboard button next to vCenter credentials > Admin password
  16. Click back to the vCenter client tab
  17. Right-click the Password field
  18. Click Paste
  19. Click Login
  20. Click to expand SDDC-Datacenter
  21. Click to expand Cluster-1 and review cluster summary

Author: bogdan.buruiana

Leave a Reply

Your email address will not be published. Required fields are marked *