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-vmware/faq.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ metadata:
4
4
description: "Get answers to common questions about Azure VMware Solution."
5
5
ms.topic: faq
6
6
ms.service: azure-vmware
7
-
ms.date: 2/29/2024
7
+
ms.date: 5/24/2024
8
8
title: Common questions about Azure VMware Solution
9
9
summary: This article answers commonly asked questions about Azure VMware Solution.
10
10
@@ -235,7 +235,7 @@ sections:
235
235
236
236
- question: Why can't I reach the Azure VMware Solution vCenter Server Appliance and NSX Manager from on-premises or Azure Virtual Network?
237
237
answer: |
238
-
By design, you won't be able to reach NSX Manager and vCenter Server Appliance (vCSA) from on-premises when only 0.0.0.0/0 (default route) is being advertised over ExpressRoute Global Reach between Azure VMware Solution and your on-premises ExpressRoute or through Azure Virtual Network to Azure VMware Solution. You need to advertise specific networking routes/subnets to access NSX-T Manager and vCSA.
238
+
By design, you won't be able to reach NSX Manager and vCenter Server Appliance (vCSA) from on-premises when only 0.0.0.0/0 (default route) is being advertised over ExpressRoute Global Reach between Azure VMware Solution and your on-premises ExpressRoute or through Azure Virtual Network to Azure VMware Solution. You need to advertise specific networking routes/subnets to access NSX Manager and vCSA.
0 commit comments