more changes

Author: varunhari92

articles/azure-vmware/native-network-design-consideration.md

@@ -3,7 +3,7 @@ title: Azure VMware Solution Generation 2 private cloud design considerations
 description: Learn about Azure VMware Solution Generation 2 private cloud design considerations.
 ms.topic: concept-article
 ms.service: azure-vmware
-ms.date: 12/15/2025
+ms.date: 12/16/2025
 ms.custom:
   - build-2025
 # 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.
@@ -100,7 +100,7 @@ Example /22 CIDR network address block **10.31.0.0/22** is divided into the foll
 |Reserved | /27 | Reserved Space. | 10.31.0.192/27 |
 
 > [!Note]
-> For AVS Gen 2, customers must now allocate an additional /22 subnet for HCX management and uplink, in addition to the /22 entered during SDDC deployment. This is not required for Gen 1.
+> For Azure VMware Solution Gen 2 deployments, customers must now allocate an additional /22 subnet for HCX management and uplink, in addition to the /22 entered during SDDC deployment. This additional /22 is not required for Gen 1.
 
 ## Next steps
 

articles/azure-vmware/tutorial-network-checklist.md

@@ -3,7 +3,7 @@ title: Tutorial - Network planning checklist
 description: In this tutorial, learn about the network requirements for network connectivity and network ports on Azure VMware Solution.
 ms.topic: tutorial
 ms.service: azure-vmware
-ms.date: 5/15/2024
+ms.date: 12/16/2025
 ms.custom: engagement-fy23
 # Customer intent: As a network architect, I want to understand the network requirements for Azure VMware Solution, so that I can ensure proper connectivity and compliance for deploying a VMware private cloud environment.
 ---
@@ -101,6 +101,7 @@ The subnets:
 | Interconnect (HCX-IX)| L2C | TCP (HTTPS) | 443 | Send management instructions from Interconnect to L2C when L2C uses the same path as the Interconnect. |
 | HCX Manager, Interconnect (HCX-IX) | ESXi Hosts | TCP | 80,443,902 | Management and OVF deployment. |
 | Interconnect (HCX-IX), Network Extension (HCX-NE) at Source| Interconnect (HCX-IX), Network Extension (HCX-NE) at Destination| UDP | 4500 | Required for IPSEC<br>   Internet key exchange (IKEv2) to encapsulate workloads for the bidirectional tunnel. Supports Network Address Translation-Traversal (NAT-T). |
+| Interconnect (HCX-IX) / Network Extension (HCX-NE) | Remote Interconnect (HCX-IX) / Network Extension (HCX-NE) | TCP,UDP | 5201 | Required for Service Mesh diagnostics for the perftest uplink test. (Moved from port 4500 with HCX 4.8). |
 | On-premises Interconnect (HCX-IX) | Cloud Interconnect (HCX-IX) | UDP | 4500 | Required for IPSEC<br> Internet Key Exchange (ISAKMP) for the bidirectional tunnel. |
 | On-premises vCenter Server network | Private Cloud management network | TCP | 8000 |  vMotion of VMs from on-premises vCenter Server to Private Cloud vCenter Server   |
 | HCX Connector | connect.hcx.vmware.com<br> hybridity.depot.vmware.com | TCP | 443 | `connect` is needed to validate license key.<br> `hybridity` is needed for updates. |