Skip to content

Commit 88b60d0

Browse files
prmerger-automator[bot]prmerger-automator[bot]
authored
Merge pull request #276199 from rvandenbedem/patch-1
Update architecture-private-clouds.md
2 parents 22572b0 + 47ef015 commit 88b60d0

File tree

3 files changed

+30
-26
lines changed

3 files changed

+30
-26
lines changed

‎articles/azure-vmware/architecture-private-clouds.md

Lines changed: 21 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Architecture - Private clouds and clusters
33
description: Understand the key capabilities of Azure VMware Solution software-defined data centers and VMware vSphere clusters.
44
ms.topic: conceptual
55
ms.service: azure-vmware
6-
ms.date: 5/5/2024
6+
ms.date: 5/25/2024
77
ms.custom: engagement-fy23
88
---
99

@@ -59,30 +59,32 @@ The Multi-AZ capability for Azure VMware Solution Stretched Clusters is also tag
5959

6060
| Azure region | Availability Zone | SKU | Multi-AZ SDDC |
6161
| :--- | :---: | :---: | :---: |
62-
| Australia East | AZ01 | AV36P | Yes |
62+
| Australia East | AZ01 | AV36P, AV64 | Yes |
6363
| Australia East | AZ02 | AV36 | No |
64-
| Australia East | AZ03 | AV36P | Yes |
64+
| Australia East | AZ03 | AV36P, AV64 | Yes |
6565
| Australia South East | AZ01 | AV36 | No |
66-
| Brazil South | AZ02 | AV36 | No |
66+
| Brazil South | AZ02 | **AV36** | No |
6767
| Canada Central | AZ02 | AV36, **AV36P** | No |
6868
| Canada East | N/A | AV36 | No |
69+
| Central India | AZ03 | AV36P | No |
6970
| Central US | AZ01 | AV36P | No |
7071
| Central US | AZ02 | **AV36** | No |
7172
| Central US | AZ03 | AV36P | No |
7273
| East Asia | AZ01 | AV36 | No |
73-
| East US | AZ01 | AV36P | Yes |
74-
| East US | AZ02 | **AV36P** | Yes |
75-
| East US | AZ03 | AV36, AV36P, AV64 | Yes |
74+
| East US | AZ01 | **AV36P** | Yes |
75+
| East US | AZ02 | **AV36P**, AV64 | Yes |
76+
| East US | AZ03 | **AV36**, **AV36P**, AV64 | Yes |
7677
| East US 2 | AZ01 | **AV36**, AV64 | No |
7778
| East US 2 | AZ02 | AV36P, **AV52**, AV64 | No |
78-
| France Central | AZ01 | AV36 | No |
79+
| France Central | AZ01 | **AV36** | No |
7980
| Germany West Central | AZ01 | AV36P | Yes |
80-
| Germany West Central | AZ02 | AV36 | Yes |
81-
| Germany West Central | AZ03 | AV36, AV36P | Yes |
81+
| Germany West Central | AZ02 | **AV36** | Yes |
82+
| Germany West Central | AZ03 | AV36, **AV36P** | Yes |
83+
| Italy North | AZ03 | AV36P | No |
8284
| Japan East | AZ02 | **AV36** | No |
8385
| Japan West | AZ01 | **AV36** | No |
84-
| North Central US | AZ01 | **AV36** | No |
85-
| North Central US | AZ02 | AV36P | No |
86+
| North Central US | AZ01 | **AV36**, AV64 | No |
87+
| North Central US | AZ02 | AV36P, AV64 | No |
8688
| North Europe | AZ02 | AV36, AV64 | No |
8789
| Qatar Central | AZ03 | AV36P | No |
8890
| South Africa North | AZ03 | AV36 | No |
@@ -91,17 +93,19 @@ The Multi-AZ capability for Azure VMware Solution Stretched Clusters is also tag
9193
| South East Asia | AZ02 | **AV36** | No |
9294
| Sweden Central | AZ01 | AV36 | No |
9395
| Switzerland North | AZ01 | **AV36**, AV64 | No |
96+
| Switzerland North | AZ03 | AV36P | No |
9497
| Switzerland West | AZ01 | **AV36**, AV64 | No |
98+
| UAE North | AZ03 | AV36P | No |
9599
| UK South | AZ01 | AV36, AV36P, AV52, AV64 | Yes |
96100
| UK South | AZ02 | **AV36**, AV64 | Yes |
97101
| UK South | AZ03 | AV36P, AV64 | Yes |
98102
| UK West | AZ01 | AV36 | No |
99-
| West Europe | AZ01 | **AV36**, AV36P, AV52 | Yes |
100-
| West Europe | AZ02 | **AV36** | Yes |
103+
| West Europe | AZ01 | **AV36**, AV36P, AV52, AV64 | Yes |
104+
| West Europe | AZ02 | **AV36**, AV64 | Yes |
101105
| West Europe | AZ03 | AV36P, AV64 | Yes |
102106
| West US | AZ01 | AV36, AV36P | No |
103107
| West US 2 | AZ01 | AV36 | No |
104-
| West US 2 | AZ02 | **AV36P** | No |
108+
| West US 2 | AZ02 | AV36P | No |
105109
| West US 3 | AZ01 | **AV36P** | No |
106110
| US Gov Arizona | AZ02 | AV36P | No |
107111
| US Gov Virginia | AZ03 | AV36 | No |
@@ -126,7 +130,7 @@ Microsoft is a member of the VMware Metal-as-a-Service (MaaS) program and uses t
126130

127131
Azure VMware Solution continuously monitors the health of both the VMware components and underlay. When Azure VMware Solution detects a failure, it takes action to repair the failed components. When Azure VMware Solution detects a degradation or failure on an Azure VMware Solution node, it triggers the host remediation process.
128132

129-
Host remediation involves replacing the faulty node with a new healthy node in the cluster. Then, when possible, the faulty host is placed in VMware vSphere maintenance mode. VMware vMotion moves the VMs off the faulty host to other available servers in the cluster, potentially allowing zero downtime for live migration of workloads. If the faulty host can't be placed in maintenance mode, the host is removed from the cluster. Before the faulty host is removed, the customer workloads are migrated to a newly added host.
133+
Host remediation involves replacing the faulty node with a new healthy node in the cluster. Then, when possible, the faulty host is placed in VMware vSphere maintenance mode. VMware vSphere vMotion moves the VMs off the faulty host to other available servers in the cluster, potentially allowing zero downtime for live migration of workloads. If the faulty host can't be placed in maintenance mode, the host is removed from the cluster. Before the faulty host is removed, the customer workloads are migrated to a newly added host.
130134

131135
> [!TIP]
132136
> **Customer communication:** An email is sent to the customer's email address before the replacement is initiated and again after the replacement is successful.
@@ -153,7 +157,7 @@ Azure VMware Solution monitors the following conditions on the host:
153157
154158
## Backup and restore
155159

156-
Azure VMware Solution private cloud vCenter Server and HCX Manager (if enabled) configurations are on a daily backup schedule and NSX configuration is on hourly backup schedule. The backups are retained for a minimum of three days.Open a [support request](https://rc.portal.azure.com/#create/Microsoft.Support) in the Azure portal to request restoration.
160+
Azure VMware Solution private cloud vCenter Server and HCX Manager (if enabled) configurations are on a daily backup schedule and NSX configuration has an hourly backup schedule. The backups are retained for a minimum of three days. Open a [support request](https://rc.portal.azure.com/#create/Microsoft.Support) in the Azure portal to request restoration.
157161

158162
> [!NOTE]
159163
> Restorations are intended for catastrophic situations only.

‎articles/azure-vmware/includes/azure-vmware-solutions-limits.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Azure VMware Solution limits
33
description: Azure VMware Solution limits.
44
ms.topic: include
55
ms.service: azure-vmware
6-
ms.date: 4/12/2024
6+
ms.date: 5/25/2024
77
author: suzizuber
88
ms.author: v-szuber
99
ms.custom: engagement-fy23
@@ -24,7 +24,7 @@ The following table describes the maximum limits for Azure VMware Solution.
2424
| Maximum number of HCX service meshes | 10 (any edition) |
2525
| Maximum number of Azure VMware Solution ExpressRoute linked private clouds from a single location to a single Virtual Network Gateway | 4<br />The virtual network gateway used determines the actual max linked private clouds. For more information, see [About ExpressRoute virtual network gateways](../../expressroute/expressroute-about-virtual-network-gateways.md)<br />If you exceed this threshold use [Azure VMware Solution Interconnect](../connect-multiple-private-clouds-same-region.md) to aggregate private cloud connectivity within the Azure region. |
2626
| Maximum Azure VMware Solution ExpressRoute port speed | 10 Gbps (use Ultra Performance Gateway SKU with FastPath enabled)<br />The virtual network gateway used determines the actual bandwidth. For more information, see [About ExpressRoute virtual network gateways](../../expressroute/expressroute-about-virtual-network-gateways.md) |
27-
| Maximum number of Azure Public IPv4 addresses assigned to NSX-T Data Center | 2,000 |
27+
| Maximum number of Azure Public IPv4 addresses assigned to NSX | 2,000 |
2828
| Maximum number of Azure VMware Solution Interconnects per private cloud | 10 |
2929
| Maximum number of Azure ExpressRoute Global Reach connections per Azure VMware Solution private cloud | 8 |
3030
| vSAN capacity limits | 75% of total usable (keep 25% available for SLA) |

‎articles/azure-vmware/includes/vmware-software-update-frequency.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,34 +3,34 @@ title: VMware software update frequency
33
description: Supported VMware software update frequency for Azure VMware Solution.
44
ms.topic: include
55
ms.service: azure-vmware
6-
ms.date: 01/05/2024
6+
ms.date: 5/25/2024
77
author: suzizuber
88
ms.author: v-szuber
99
ms.custom: engagement-fy23
1010
---
1111

1212
<!-- Used in faq.md and concepts-private-clouds-clusters.md -->
1313

14-
One benefit of Azure VMware Solution private clouds is that the platform is maintained for you. Microsoft is responsible for the lifecycle management of VMware software (ESXi, vCenter Server, and vSAN) and NSX-T Data Center appliances. Microsoft is also responsible for bootstrapping the network configuration, like creating the Tier-0 gateway and enabling North-South routing. You’re responsible for the NSX-T Data Center SDN configuration: network segments, distributed firewall rules, Tier 1 gateways, and load balancers.
14+
One benefit of Azure VMware Solution private clouds is that the platform is maintained for you. Microsoft is responsible for the lifecycle management of VMware software (ESXi, vCenter Server, and vSAN) and NSX appliances. Microsoft is also responsible for bootstrapping the network configuration, like creating the Tier-0 gateway and enabling North-South routing. You’re responsible for the NSX SDN configuration: network segments, distributed firewall rules, Tier 1 gateways, and load balancers.
1515

1616
> [!NOTE]
17-
> A T0 gateway is created and configured as part of a private cloud deployment. Any modification to that logical router or the NSX-T Data Center edge node VMs could affect connectivity to your private cloud and should be avoided.
17+
> A T0 gateway is created and configured as part of a private cloud deployment. Any modification to that logical router or the NSX edge node VMs could affect connectivity to your private cloud and should be avoided.
1818
19-
Microsoft is responsible for applying any patches, updates, or upgrades to ESXi, vCenter Server, vSAN, and NSX-T Data Center in your private cloud. The impact of patches, updates, and upgrades on ESXi, vCenter Server, and NSX-T Data Center has the following considerations:
19+
Microsoft is responsible for applying any patches, updates, or upgrades to ESXi, vCenter Server, vSAN, and NSX in your private cloud. The impact of patches, updates, and upgrades on ESXi, vCenter Server, and NSX has the following considerations:
2020

21-
- **ESXi** - There's no impact to workloads running in your private cloud. Access to vCenter Server and NSX-T Data Center isn't blocked during this time. During this time, we recommend you don't plan other activities like: scaling up private cloud, scheduling or initiating active HCX migrations, making HCX configuration changes, and so on, in your private cloud.
21+
- **ESXi** - There's no impact to workloads running in your private cloud. Access to vCenter Server and NSX isn't blocked during this time. During this time, we recommend you don't plan other activities like: scaling up private cloud, scheduling or initiating active HCX migrations, making HCX configuration changes, and so on, in your private cloud.
2222

2323
- **vCenter Server** - There's no impact to workloads running in your private cloud. During this time, vCenter Server is unavailable and you can't manage VMs (stop, start, create, or delete). We recommend you don't plan other activities like scaling up private cloud, creating new networks, and so on, in your private cloud. When you use VMware Site Recovery Manager or vSphere Replication user interfaces, we recommend you don't do either of the actions: configure vSphere Replication, and configure or execute site recovery plans during the vCenter Server upgrade.
2424

25-
- **NSX-T Data Center** - The workload is impacted. When a particular host is being upgraded, the VMs on that host might lose connectivity from 2 seconds to 1 minute with any of the following symptoms:
25+
- **NSX** - The workload is impacted. When a particular host is being upgraded, the VMs on that host might lose connectivity from 2 seconds to 1 minute with any of the following symptoms:
2626

2727
- Ping errors
2828

2929
- Packet loss
3030

3131
- Error messages (for example, *Destination Host Unreachable* and *Net unreachable*)
3232

33-
During this upgrade window, all access to the NSX-T Data Center management plane is blocked. You can't make configuration changes to the NSX-T Data Center environment for the duration. Your workloads continue to run as normal, subject to the upgrade impact previously detailed.
33+
During this upgrade window, all access to the NSX management plane is blocked. You can't make configuration changes to the NSX environment for the duration. Your workloads continue to run as normal, subject to the upgrade impact previously detailed.
3434

3535
During the upgrade time, we recommend you don't plan other activities like, scaling up private cloud, and so on, in your private cloud. Other activities can prevent the upgrade from starting or could have adverse impacts on the upgrade and the environment.
3636

0 commit comments

Comments
 (0)