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
Copy file name to clipboardExpand all lines: articles/azure-arc/vmware-vsphere/support-matrix-for-arc-enabled-vmware-vsphere.md
+14-15Lines changed: 14 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,8 @@
1
1
---
2
2
title: Support matrix for Arc-enabled VMware vSphere (preview)
3
3
description: In this article, you'll learn about the support matrix for Arc-enabled VMware vSphere including vCenter Server versions supported, network requirements etc.
4
-
ms.topic: reference
5
-
ms.custom: references_regions
6
-
ms.date: 09/23/2022
4
+
ms.topic: how-to
5
+
ms.date: 09/30/2022
7
6
8
7
# Customer intent: As a VI admin, I want to understand the support matrix for Arc-enabled VMware vSphere.
9
8
---
@@ -12,7 +11,7 @@ ms.date: 09/23/2022
12
11
13
12
This article documents the prerequisites and support requirements for using the [Arc-enabled VMware vSphere (preview)](overview.md) to manage your VMware vSphere VMs through Azure Arc.
14
13
15
-
To use Arc-enabled VMware vSphere, you must deploy an Azure Arc Resource Bridge in your VMware vSphere environment. The Resource Bridge provides an ongoing connection between your VMware vCenter Server and Azure. Once you've connected your VMware vCenter Server to Azure, components on the Resource Bridge discover your vCenter inventory. You can enable them in Azure and start performing virtual hardware and guest OS operations on them using Azure Arc.
14
+
To use Arc-enabled VMware vSphere, you must deploy an Azure Arc resource bridge in your VMware vSphere environment. The resource bridge provides an ongoing connection between your VMware vCenter Server and Azure. Once you've connected your VMware vCenter Server to Azure, components on the resource bridge discover your vCenter inventory. You can enable them in Azure and start performing virtual hardware and guest OS operations on them using Azure Arc.
16
15
17
16
18
17
## VMware vSphere Requirements
@@ -27,31 +26,31 @@ You need a vSphere account that can:
27
26
- Read all inventory.
28
27
- Deploy and update VMs to all the resource pools (or clusters), networks, and VM templates that you want to use with Azure Arc.
29
28
30
-
This account is used for the ongoing operation of Azure Arc-enabled VMware vSphere (preview) and the deployment of the Azure Arc Resource Bridge (preview) VM.
29
+
This account is used for the ongoing operation of Azure Arc-enabled VMware vSphere (preview) and the deployment of the Azure Arc resource bridge (preview) VM.
31
30
32
-
### Resource Bridge resource requirements
31
+
### Resource bridge resource requirements
33
32
34
-
For Arc-enabled VMware vSphere, Resource Bridge has the following minimum virtual hardware requirements
33
+
For Arc-enabled VMware vSphere, resource bridge has the following minimum virtual hardware requirements
35
34
36
35
- 16 GB of memory
37
36
- 4 vCPUs
38
37
- An external virtual switch that can provide access to the internet directly or through a proxy. If internet access is through a proxy or firewall, ensure [these URLs](#resource-bridge-networking-requirements) are allow-listed.
39
38
40
-
### Resource Bridge networking requirements
39
+
### Resource bridge networking requirements
41
40
42
-
The following firewall URL exceptions are needed for the Azure Arc Resource Bridge VM:
41
+
The following firewall URL exceptions are needed for the Azure Arc resource bridge VM:
| Microsoft container registry | 443 |https://mcr.microsoft.com| Appliance VM IP and control plane endpoint need outbound connection. | Required to pull container images for installation. |
47
46
| Azure Arc Identity service | 443 | https://*.his.arc.azure.com | Appliance VM IP and control plane endpoint need outbound connection. | Manages identity and access control for Azure resources |
48
47
| Azure Arc configuration service | 443 | https://*.dp.kubernetesconfiguration.azure.com | Appliance VM IP and control plane endpoint need outbound connection. | Used for Kubernetes cluster configuration. |
49
-
| Cluster connect service | 443 | https://*.servicebus.windows.net | Appliance VM IP and control plane endpoint need outbound connection. | Provides cloud-enabled communication to connect on-premise resources with the cloud. |
50
-
| Guest Notification service | 443 |https://guestnotificationservice.azure.com| Appliance VM IP and control plane endpoint need outbound connection. | Used to connect on-premise resources to Azure. |
48
+
| Cluster connect service | 443 | https://*.servicebus.windows.net | Appliance VM IP and control plane endpoint need outbound connection. | Provides cloud-enabled communication to connect on-premises resources with the cloud. |
49
+
| Guest Notification service | 443 |https://guestnotificationservice.azure.com| Appliance VM IP and control plane endpoint need outbound connection. | Used to connect on-premises resources to Azure. |
51
50
| SFS API endpoint | 443 | msk8s.api.cdp.microsoft.com | Host machine, Appliance VM IP and control plane endpoint need outbound connection. | Used when downloading product catalog, product bits, and OS images from SFS. |
52
-
| Resource Bridge (appliance) Dataplane service | 443 | https://*.dp.prod.appliances.azure.com | Appliance VM IP and control plane endpoint need outbound connection. | Communicate with resource provider in Azure. |
53
-
| Resource Bridge (appliance) container image download | 443 |*.blob.core.windows.net, https://ecpacr.azurecr.io| Appliance VM IP and control plane endpoint need outbound connection. | Required to pull container images. |
54
-
| Resource Bridge (appliance) image download | 80 |*.dl.delivery.mp.microsoft.com | Host machine, Appliance VM IP and control plane endpoint need outbound connection. | Download the Arc Resource Bridge OS images. |
51
+
| Resource bridge (appliance) Dataplane service | 443 | https://*.dp.prod.appliances.azure.com | Appliance VM IP and control plane endpoint need outbound connection. | Communicate with resource provider in Azure. |
52
+
| Resource bridge (appliance) container image download | 443 |*.blob.core.windows.net, https://ecpacr.azurecr.io| Appliance VM IP and control plane endpoint need outbound connection. | Required to pull container images. |
53
+
| Resource bridge (appliance) image download | 80 |*.dl.delivery.mp.microsoft.com | Host machine, Appliance VM IP and control plane endpoint need outbound connection. | Download the Arc resource bridge OS images. |
55
54
| Azure Arc for K8s container image download | 443 |https://azurearcfork8sdev.azurecr.io| Appliance VM IP and control plane endpoint need outbound connection. | Required to pull container images. |
56
55
| ADHS telemetry service | 443 | adhs.events.data.microsoft.com | Appliance VM IP and control plane endpoint need outbound connection. Runs inside the appliance/mariner OS. | Used periodically to send Microsoft required diagnostic data from control plane nodes. Used when telemetry is coming off Mariner, which would mean any K8s control plane. |
57
56
| Microsoft events data service | 443 | v20.events.data.microsoft.com | Appliance VM IP and control plane endpoint need outbound connection. | Used periodically to send Microsoft required diagnostic data from the Azure Stack HCI or Windows Server host. Used when telemetry is coming off Windows like Windows Server or HCI. |
@@ -78,7 +77,7 @@ To enable guest management (install the Arc connected machine agent), ensure
78
77
79
78
- VM is powered on
80
79
- VM has VMware tools installed and running
81
-
- Resource Bridge has access to the host on which the VM is running
80
+
- Resource bridge has access to the host on which the VM is running
82
81
- VM is running a [supported operating system](#supported-operating-systems)
83
82
- VM has internet connectivity directly or through proxy. If the connection is through a proxy, ensure [these URLs](#networking-requirements) are allow-listed.
0 commit comments