Merge pull request #291392 from rvandenbedem/patch-3

Update architecture-stretched-clusters.md

Author: v-ccolin

articles/azure-vmware/architecture-stretched-clusters.md

@@ -3,7 +3,7 @@ title: Architecture - Design considerations for vSAN stretched clusters
 description: Learn about how to use stretched clusters for Azure VMware Solution.
 ms.topic: concept-article
 ms.service: azure-vmware
-ms.date: 6/4/2024
+ms.date: 12/4/2024
 ms.custom: references_regions, engagement-fy24
 ---
 
@@ -31,6 +31,10 @@ The following diagram depicts a vSAN cluster stretched across two AZs.
 
 :::image type="content" source="media/stretch-clusters/diagram-1-vsan-witness-third-availability-zone.png" alt-text="Diagram shows a managed vSAN stretched cluster created in a third Availability Zone with the data being copied to all three of them." border="false" lightbox="media/stretch-clusters/diagram-1-vsan-witness-third-availability-zone.png":::
 
+The following diagram depicts the normal flow of network traffic within a vSAN cluster stretched across two AZs. 
+
+:::image type="content" source="media/stretch-clusters/diagram-5-normal-traffic-flow.png" alt-text="Diagram shows VMware NSX traffic flows for a managed vSAN stretched cluster." border="false" lightbox="media/stretch-clusters/diagram-5-normal-traffic-flow.png":::
+
 In summary, stretched clusters simplify protection needs by providing the same trusted controls and capabilities in addition to the scale and flexibility of the Azure infrastructure.
 
 It's important to understand that stretched cluster private clouds only offer an extra layer of resiliency, and they don't address all failure scenarios. For example, stretched cluster private clouds:
@@ -42,15 +46,18 @@ It's important to understand that stretched cluster private clouds only offer an
 
         :::image type="content" source="media/stretch-clusters/diagram-2-secondary-site-power-off-workload.png" alt-text="Diagram shows vSphere high availability powering off the workload virtual machines on the secondary site." border="false" lightbox="media/stretch-clusters/diagram-2-secondary-site-power-off-workload.png":::
 
-    - If the secondary site partitioning progressed into the failure of the primary site instead, or resulted in a complete partitioning, vSphere HA would attempt to restart the workload VMs on the secondary site. If vSphere HA attempted to restart the workload VMs on the secondary site, it would put the workload VMs in an unsteady state. 
-    
+    - If the secondary site partitioning progressed into the failure of the primary site instead, or resulted in a complete partitioning, vSphere HA would attempt to restart the workload VMs on the secondary site. If vSphere HA attempted to restart the workload VMs on the secondary site, it would put the workload VMs in an unsteady state.   
 
         The following diagrams show the preferred site failure and complete network partitioning scenarios.
 
         :::image type="content" source="media/stretch-clusters/diagram-3-restart-workload-secondary-site.png" alt-text="Diagram shows vSphere high availability trying to restart the workload virtual machines on the secondary site when preferred site failure occurs." border="false" lightbox="media/stretch-clusters/diagram-3-restart-workload-secondary-site.png":::
 
         :::image type="content" source="media/stretch-clusters/diagram-4-restart-workload-secondary-site.png" alt-text="Diagram shows vSphere high availability trying to restart the workload virtual machines on the secondary site when complete network isolation occurs." border="false" lightbox="media/stretch-clusters/diagram-4-restart-workload-secondary-site.png":::
 
+        The following diagram shows the flow of network traffic within a vSAN cluster stretched during a complete site failure.
+
+        :::image type="content" source="media/stretch-clusters/diagram-6-site-failure-traffic-flow.png" alt-text="Diagram shows VMware NSX traffic flows for a managed vSAN stretched cluster during a complete site failure." border="false" lightbox="media/stretch-clusters/diagram-6-site-failure-traffic-flow.png":::
+
 It should be noted that these types of failures, although rare, fall outside the scope of the protection offered by a stretched cluster private cloud. Because of those types of rare failures, a stretched cluster solution should be regarded as a multi-AZ high availability solution reliant upon vSphere HA. It's important you understand that a stretched cluster solution isn't meant to replace a comprehensive multi-region Disaster Recovery strategy that can be employed to ensure application availability. The reason is because a Disaster Recovery solution typically has separate management and control planes in separate Azure regions. Azure VMware Solution stretched clusters have a single management and control plane stretched across two availability zones within the same Azure region. For example, one vCenter Server, one NSX Manager cluster, one NSX Edge VM pair.
 
 ## Stretched clusters region availability

articles/azure-vmware/deploy-vsan-stretched-clusters.md

@@ -3,7 +3,7 @@ title: Deploy vSAN stretched clusters
 description: Learn how to deploy vSAN stretched clusters.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 3/22/2024
+ms.date: 12/4/2024
 ms.custom: references_regions, engagement-fy23 
 ---
 
@@ -19,7 +19,7 @@ Follow the [Request Host Quota](/azure/azure-vmware/request-host-quota-azure-vmw
 - Point of contact: email
 - Subscription ID: a new, separate subscription is required
 - Type of private cloud: "Stretched Cluster"
-- Region requested: UK South, West Europe, Germany West Central, or Australia East
+- Region requested: East US, UK South, West Europe, Germany West Central, or Australia East
 - Number of nodes in first stretched cluster: minimum 6, maximum 16 - in multiples of two
 - Estimated expansion plan