{"id":777,"date":"2021-12-31T09:03:14","date_gmt":"2021-12-31T09:03:14","guid":{"rendered":"https:\/\/bogdanburuiana.com\/?p=777"},"modified":"2022-02-15T11:48:44","modified_gmt":"2022-02-15T11:48:44","slug":"deployment-of-azure-vmware-solution","status":"publish","type":"post","link":"https:\/\/bogdanburuiana.com\/index.php\/2021\/12\/31\/deployment-of-azure-vmware-solution\/","title":{"rendered":"Deployment of Azure VMware Solution"},"content":{"rendered":"\n

To deploy an Azure VMware Solution private cloud, you must have an Azure subscription associated with a Microsoft enterprise agreement, or you can deploy AVS within an Azure subscription managed by a CSP.<\/p>\n\n\n\n

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. <\/p>\n\n\n\n

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<\/strong>, so it is important to plan accordingly. <\/p>\n\n\n\n

Start the host quota request process with the following steps:<\/p>\n\n\n\n

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

                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.<\/p>\n\n\n\n

                \"\"<\/figure>\n\n\n\n

                Next, we need to confirm that the Microsoft.AVS resource provider in registered in your subscription.<\/p>\n\n\n\n

                1. Click Home<\/strong><\/li>
                2. Click on the AVS<\/strong> subscription<\/li>
                3. Click the scroll bar<\/strong> in the Resource Menu to scroll down<\/li>
                4. Click Settings > Resource providers<\/strong><\/li>
                5. Click the Filter by name<\/strong> bar<\/li>
                6. Type \u201cMicrosoft.AVS\u201d<\/strong> and hit enter<\/strong><\/li><\/ol>\n\n\n\n
                  \"\"<\/figure>\n\n\n\n

                  The view will filter. Note that the Microsoft.AVS<\/strong> provider is already registered. If status was \u201cUnregistered,\u201d we could register it by clicking on the Microsoft.AVS row, then clicking Register<\/strong>.<\/p>\n\n\n\n

                  Next, we will create a new Azure resource group for our AVS private cloud and related objects.<\/p>\n\n\n\n

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

                      Deploy the AVS private cloud<\/strong><\/h2>\n\n\n\n

                      Now we will deploy the AVS private cloud.<\/p>\n\n\n\n

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

                            Leave Number of hosts<\/strong> set to 3<\/p>\n\n\n\n

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

                                Connect the AVS private cloud to a new Azure virtual network<\/strong><\/h2>\n\n\n\n

                                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.<\/p>\n\n\n\n

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

                                    Access vCenter from the connected Azure VNet<\/strong><\/h2>\n\n\n\n

                                    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.<\/p>\n\n\n\n

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

                                              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.<\/p>\n\n\n\n

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

                                                  Connect an on-premises data<\/strong> center to the AVS private cloud<\/h2>\n\n\n\n

                                                  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.<\/p>\n\n\n\n

                                                  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.<\/p>\n\n\n\n

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

                                                      <\/p>\n","protected":false},"excerpt":{"rendered":"

                                                      To deploy an Azure VMware Solution private cloud, you must have an Azure subscription associated with a Microsoft enterprise agreement, or you can deploy AVS within an Azure subscription managed by a CSP. I begin logged into the Azure Portal with access to such a subscription. As a first step, I will request AVS host […]<\/p>\n","protected":false},"author":1,"featured_media":117,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,4],"tags":[],"_links":{"self":[{"href":"https:\/\/bogdanburuiana.com\/index.php\/wp-json\/wp\/v2\/posts\/777"}],"collection":[{"href":"https:\/\/bogdanburuiana.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bogdanburuiana.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bogdanburuiana.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/bogdanburuiana.com\/index.php\/wp-json\/wp\/v2\/comments?post=777"}],"version-history":[{"count":18,"href":"https:\/\/bogdanburuiana.com\/index.php\/wp-json\/wp\/v2\/posts\/777\/revisions"}],"predecessor-version":[{"id":831,"href":"https:\/\/bogdanburuiana.com\/index.php\/wp-json\/wp\/v2\/posts\/777\/revisions\/831"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/bogdanburuiana.com\/index.php\/wp-json\/wp\/v2\/media\/117"}],"wp:attachment":[{"href":"https:\/\/bogdanburuiana.com\/index.php\/wp-json\/wp\/v2\/media?parent=777"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bogdanburuiana.com\/index.php\/wp-json\/wp\/v2\/categories?post=777"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bogdanburuiana.com\/index.php\/wp-json\/wp\/v2\/tags?post=777"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}