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
+1-11Lines changed: 1 addition & 11 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: 10/13/2023
7
+
ms.date: 2/23/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
@@ -182,16 +182,6 @@ sections:
182
182
- question: Can an existing ExpressRoute Gateway be used to connect to Azure VMware Solution?
183
183
answer: Yes. Use an existing ExpressRoute Gateway to connect to Azure VMware Solution as long as it doesn't exceed the limit of four ExpressRoute circuits per virtual network. To access Azure VMware Solution from on-premises through ExpressRoute, you must have ExpressRoute Global Reach since the ExpressRoute Gateway doesn't provide transitive routing between its connected circuits.
184
184
185
-
- question: Why does Azure VMware Solution use a Public 4-byte Autonomous System Number (ASN)?
186
-
answer: Azure VMware Solution uses the officially registered Public 4-byte ASNs to ensure there is never a conflict with your on-premises use of Private ASNs in the customer's routing path to Azure VMware Solution.
187
-
188
-
- question: How can I use ExpressRoute to connect to Azure VMware Solution if the on-premises ExpressRoute-carrier partners/ISPs don't support 4-byte ASN?
189
-
answer: |
190
-
The only way to connect to Azure VMware Solution through ExpressRoute is for your environment and the on-premises ExpressRoute-carrier partners/ISPs support 4-byte ASN or have backward compatibility from 4-byte to 2-byte ASN in the BGP prefix ASN path advertisement.
191
-
192
-
> [!NOTE]
193
-
> Currently, private ASN (64512 - 65534) prepending from a customer on-premises environment isn't supported by Azure VMware Solution. This scenario might lead to intermittent connection drops from on-premises to Azure VMware Solution. Also design your traffic path for private ASNs after the public ASN to be honored by Azure VMware Solution. The Azure VMware Solution ExpressRoute circuit doesn't strip any private ASNs that exist in the path after the public ASN is processed.
194
-
195
185
- question: What network IP address planning is required to incorporate private clouds with on-premises environments?
196
186
answer: A private network /22 address space is required to deploy an Azure VMware Solution private cloud. This private address space shouldn't overlap with other virtual networks in a subscription or with on-premises networks.
0 commit comments