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
# customer intent: As a cloud administrator, I want to learn about Azure VMware Solution Generation 2 private cloud design considerations so that I can make informed decisions about my Azure VMware Solution deployment.
This article outlines key design considerations for Azure VMware Solution Generation 2 (Gen 2) private clouds. It explains the capabilities this generation brings to VMware-based private cloud environments, enabling access for your applications from both on-premises infrastructure and Azure-based resources. There are several considerations to review before you set up your Azure VMware Solution Gen 2 private cloud. This article provides solutions for use cases that you might encounter when you're using the private cloud type.
13
13
@@ -20,22 +20,22 @@ The following functionality is limited during this time. These limitations will
20
20
21
21
- You cannot delete your Resource Group, which contains your Private Cloud.
22
22
- You can only deploy **1 Private Cloud per Azure Virtual Network**.
23
-
- You can only create **1 SDDC per Resource Group**. Multiple Private Clouds in a single Resource Group are not supported.
23
+
- You can only create **1 Private Cloud per Resource Group**. Multiple Private Clouds in a single Resource Group are not supported.
24
24
- Your Private Cloud and Virtual Network for your Private Cloud must be in the *same* Resource Group.
25
25
- You cannot move your Private Cloud from one Resource Group to another after the Private Cloud is created.
26
26
- Virtual Network Service Endpoints direct connectivity from Azure VMware Solution workloads is not supported.
27
27
-**vCloud Director** using Private Endpoints is supported. However, vCloud Director using Public Endpoints is not supported.
28
28
-**vSAN Stretched Clusters** is not supported.
29
-
- Public IP down to the NSX Microsoft Edge for configuring internet will not be supported.
29
+
- Public IP down to the VMware NSX Microsoft Edge for configuring internet will not be supported.
30
30
- Support for **AzCLI**, **PowerShell**, and **.NET SDK** are not available during Public Preview.
31
31
-**Run Commands** interacting with customer segments aren't supported including run commands interacting with Zerto, Jetstream, and other 3rd-party integrations.
32
32
33
33
## Unsupported integrations during Public Preview
34
34
35
35
The following 1st-party and 3rd-party integrations won't be available during Public Preview:
36
-
-**ElasticSAN**
37
-
-**Zerto**
38
-
-**Jetstream**
36
+
-**Azure Elastic SAN**
37
+
-**Zerto DR**
38
+
-**Jetstream DR**
39
39
40
40
## Routing and subnet considerations
41
41
@@ -46,7 +46,7 @@ The private cloud connects to your Azure virtual network using standard Azure ne
46
46
> [!Note]
47
47
> Permitted ranges for your address block are the RFC 1918 private address spaces (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), except for 172.17.0.0/16. Replication network is not applicable to AV64 nodes and is planned for general deprecation at a future date.
48
48
49
-
Avoid using the following IP schemas reserved for NSX usage:
49
+
Avoid using the following IP schemas reserved for VMware NSX usage:
50
50
51
51
- 169.254.0.0/24 - used for internal transit network
52
52
- 169.254.2.0/23 - used for inter-VRF transit network
| esx-cust-fdc | /27 | The management appliances (vCenter and NSX manager) are behind the "esx-cust-fdc” subnet, programmed as secondary IP ranges on this subnet. | 10.31.0.64/27 |
65
-
| cust-fds | /27 | Used by Azure VMware Solution to program routes created in NSX into the virtual network. | 10.31.0.96/27 |
66
-
| services | /27 | Used for Azure VMware Solution provider services. Also used to configure private DNS resolution for your private cloud. | 10.31.0.160/27 |
67
-
| esx-lrnsxuplink, esx-lrnsxuplink-1 | /28 | Subnets off each of the T0s per edge. These subnets are used to program NSX network segments as secondary IPs addresses. | 10.31.0.224/28, 10.31.0.240/28 |
| esx-cust-fdc | /27 | The management appliances (vCenter Server and NSX manager) are behind the "esx-cust-fdc” subnet, programmed as secondary IP ranges on this subnet. | 10.31.0.64/27 |
65
+
| cust-fds | /27 | Used by Azure VMware Solution Gen 2 to program routes created in VMware NSX into the virtual network. | 10.31.0.96/27 |
66
+
| services | /27 | Used for Azure VMware Solution Gen 2 provider services. Also used to configure private DNS resolution for your private cloud. | 10.31.0.160/27 |
67
+
| esx-lrnsxuplink, esx-lrnsxuplink-1 | /28 | Subnets off each of the T0 Gateways per edge. These subnets are used to program VMware NSX network segments as secondary IPs addresses. | 10.31.0.224/28, 10.31.0.240/28 |
68
68
| esx-cust-vmk1 | /24 | vmk1 is the management interface used by customers to access the host. IPs from the vmk1 interface come from these subnets. All of the vmk1 traffic for all hosts comes from this subnet range. | 10.31.1.0/24 |
- Get started with configuring your Azure VMware Solution service principal as a prerequisite. To learn how, see the [Enabling Azure VMware Solution service principal](native-first-party-principle-security.md) quickstart.
0 commit comments