search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.28k stars 21.47k forks source link

Need a better definition on what is preferred for ExpressRoute/VPN when HUB routing is concerned. #93304

Closed brmarti116 closed 1 year ago

brmarti116 commented 2 years ago

From this section:

"How does the virtual hub in a virtual WAN select the best path for a route from multiple hubs? If a virtual hub learns the same route from multiple remote hubs, the order in which it decides is as follows:

1) Longest prefix match. 2) Local routes over interhub. 3) Static routes over BGP: This is in context to the decision being made by the virtual hub router. However, if the decision maker is the VPN gateway where a site advertises routes via BGP or provides static address prefixes, static routes may be preferred over BGP routes. 4) ExpressRoute (ER) over VPN: ER is preferred over VPN when the context is a local hub. Transit connectivity between ExpressRoute circuits is only available through Global Reach. Therefore, in scenarios where ExpressRoute circuit is connected to one hub and there is another ExpressRoute circuit connected to a different hub with VPN connection, VPN may be preferred for inter-hub scenarios. AS path length (Virtual hubs prepend routes with the AS path 65520-65520 when advertising routes to each other)."

For item 4, we are receiving volume due to "VPN may be preferred" and need that changed to "will be preferred" or "will not be preferred" or we need a more descriptive definition as to when this does or does not become preferred.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ChaitanyaNaykodi-MSFT commented 2 years ago

Thank you for your feedback! We have assigned this issue to the author to review further and take the next course of action.

cherylmc commented 1 year ago

reassign:cfields475

asudbring commented 1 year ago

Thank you for you dedication to our documentation.

Unfortunately, we have been unable to review this issue in a timely manner. We sincerely apologize for the delayed response. We are closing this issue. If you feel that the problem persists, please respond to this issue with additional information.

Please continue to provide feedback about the documentation. We appreciate your contributions to our community.

please-close