You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Learn how to set up and enable Arc for your Azure VMware Solution private cloud.
4
4
ms.topic: how-to
5
5
ms.service: azure-vmware
6
-
ms.date: 04/11/2022
6
+
ms.date: 08/28/2023
7
7
ms.custom: references_regions
8
8
---
9
9
@@ -16,7 +16,7 @@ Before you begin checking off the prerequisites, verify the following actions ha
16
16
17
17
- You deployed an Azure VMware Solution private cluster.
18
18
- You have a connection to the Azure VMware Solution private cloud through your on-premises environment or your native Azure Virtual Network.
19
-
- There should be an isolated NSX-T Data Center segment for deploying the Arc for Azure VMware Solution Open Virtualization Appliance (OVA). If an isolated NSX-T Data Center segment doesn't exist, one will be created.
19
+
- There should be an isolated NSX-T Data Center network segment for deploying the Arc for Azure VMware Solution Open Virtualization Appliance (OVA). If an isolated NSX-T Data Center network segment doesn't exist, one will be created.
20
20
21
21
## Prerequisites
22
22
@@ -30,7 +30,7 @@ The following items are needed to ensure you're set up to begin the onboarding p
30
30
- Verify that your vCenter Server version is 6.7 or higher.
31
31
- A resource pool with minimum-free capacity of 16 GB of RAM, 4 vCPUs.
32
32
- A datastore with minimum 100 GB of free disk space that is available through the resource pool.
33
-
- On the vCenter Server, allow inbound connections on TCP port 443, so that the Arc resource bridge and VMware cluster extension can communicate with the vCenter server.
33
+
- On the vCenter Server, allow inbound connections on TCP port 443, so that the Arc resource bridge and VMware vSphere cluster extension can communicate with the vCenter Server.
34
34
- Please validate the regional support before starting the onboarding. Arc for Azure VMware Solution is supported in all regions where Arc for VMware vSphere on-premises is supported. For more details, see [Azure Arc-enabled VMware vSphere](https://learn.microsoft.com/azure/azure-arc/vmware-vsphere/overview).
35
35
- The firewall and proxy URLs below must be allowlisted in order to enable communication from the management machine, Appliance VM, and Control Plane IP to the required Arc resource bridge URLs.
@@ -66,7 +66,7 @@ az feature show --name AzureArcForAVS --namespace Microsoft.AVS
66
66
67
67
## Onboard process to deploy Azure Arc
68
68
69
-
Use the following steps to guide you through the process to onboard in Arc for Azure VMware Solution (Preview).
69
+
Use the following steps to guide you through the process to onboard Azure Arc for Azure VMware Solution (Preview).
70
70
71
71
1. Sign into the jumpbox VM and extract the contents from the compressed file from the following [location](https://github.com/Azure/ArcOnAVS/releases/latest). The extracted file contains the scripts to install the preview software.
72
72
1. Open the 'config_avs.json' file and populate all the variables.
@@ -139,7 +139,7 @@ Use the following steps to guide you through the process to onboard in Arc for A
139
139
> [!IMPORTANT]
140
140
> You can't create the resources in a separate resource group. Make sure you use the same resource group from where the Azure VMware Solution private cloud was created to create the resources.
141
141
142
-
## Discover and project your VMware infrastructure resources to Azure
142
+
## Discover and project your VMware vSphere infrastructure resources to Azure
143
143
144
144
When Arc appliance is successfully deployed on your private cloud, you can do the following actions.
145
145
@@ -177,7 +177,7 @@ After the private cloud is Arc-enabled, vCenter resources should appear under **
177
177
178
178
### Manage access to VMware resources through Azure Role-Based Access Control
179
179
180
-
After your Azure VMware Solution vCenter resources have been enabled for access through Azure, there's one final step in setting up a self-service experience for your teams. You'll need to provide your teams with access to: compute, storage, networking, and other vCenter Server resources used to configure VMs.
180
+
After your Azure VMware Solution vCenter Server resources have been enabled for access through Azure, there's one final step in setting up a self-service experience for your teams. You'll need to provide your teams with access to: compute, storage, networking, and other vCenter Server resources used to configure VMs.
181
181
182
182
This section will demonstrate how to use custom roles to manage granular access to VMware vSphere resources through Azure.
183
183
@@ -309,7 +309,7 @@ When the extension installation steps are completed, they trigger deployment and
309
309
310
310
## Change Arc appliance credential
311
311
312
-
When **cloud admin** credentials are updated, use the following steps to update the credentials in the appliance store.
312
+
When **cloudadmin** credentials are updated, use the following steps to update the credentials in the appliance store.
313
313
314
314
1. Log in to the jumpbox VM from where onboarding was performed. Change the directory to **onboarding directory**.
315
315
1. Run the following command for Windows-based jumpbox VM.
@@ -391,7 +391,7 @@ When you activate Arc-enabled Azure VMware Solution resources in Azure, a repres
391
391
1. Repeat steps 2, 3 and 4 for **Resourcespools/clusters/hosts**, **Templates**, **Networks**, and **Datastores**.
392
392
1. When the deletion completes, select **Overview**.
393
393
1. Note the Custom location and the Azure Arc Resource bridge resources in the Essentials section.
394
-
1. Select **Remove from Azure** to remove the vCenter resource from Azure.
394
+
1. Select **Remove from Azure** to remove the vCenter Server resource from Azure.
395
395
1. Go to vCenter Server resource in Azure and delete it.
396
396
1. Go to the Custom location resource and select **Delete**.
397
397
1. Go to the Azure Arc Resource bridge resources and select **Delete**.
@@ -400,7 +400,7 @@ At this point, all of your Arc-enabled VMware vSphere resources have been remove
400
400
401
401
## Delete Arc resources from vCenter Server
402
402
403
-
For the final step, you'll need to delete the resource bridge VM and the VM template that were created during the onboarding process. Login to vCenter and delete resource bridge VM and the VM template from inside the arc-folder. Once that step is done, Arc won't work on the Azure VMware Solution SDDC. When you delete Arc resources from vCenter, it won't affect the Azure VMware Solution private cloud for the customer.
403
+
For the final step, you'll need to delete the resource bridge VM and the VM template that were created during the onboarding process. Login to vCenter Server and delete resource bridge VM and the VM template from inside the arc-folder. Once that step is done, Arc won't work on the Azure VMware Solution private cloud. When you delete Arc resources from vCenter Server, it won't affect the Azure VMware Solution private cloud for the customer.
404
404
405
405
## Preview FAQ
406
406
@@ -412,20 +412,17 @@ Arc for Azure VMware Solution is supported in all regions where Arc for VMware v
412
412
413
413
Standard support process for Azure VMware Solution has been enabled to support customers.
414
414
415
-
**Does Arc for Azure VMware Solution support private end point?**
415
+
**Does Arc for Azure VMware Solution support private endpoint?**
416
416
417
-
Yes. Arc for Azure VMware Solution will support private end point for general audience. However, it's not currently supported.
417
+
Private endpoint is currently not supported.
418
418
419
419
**Is enabling internet the only option to enable Arc for Azure VMware Solution?**
420
420
421
-
Yes
421
+
Yes, the Azure VMware Solution private cloud and jumpbox VM must have internet access for Arc to function.
422
422
423
423
**Is DHCP support available?**
424
424
425
-
DHCP support isn't available to customers at this time, we only support static IP.
426
-
427
-
>[!NOTE]
428
-
> This is Azure VMware Solution 2.0 only. It's not available for Azure VMware Solution by Cloudsimple.
425
+
DHCP support isn't available to customers at this time, we only support static IP addresses.
429
426
430
427
## Debugging tips for known issues
431
428
@@ -459,7 +456,7 @@ Use the following tips as a self-help guide.
459
456
**I'm unable to install extensions on my virtual machine.**
460
457
461
458
- Check that **guest management** has been successfully installed.
462
-
- **VMtools** should be installed on the VM.
459
+
- **VMware Tools** should be installed on the VM.
463
460
464
461
**I'm facing Network related issues during on-boarding.**
0 commit comments