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/route-server/anycast.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,8 +6,7 @@ author: halkazwini
6
6
ms.author: halkazwini
7
7
ms.service: azure-route-server
8
8
ms.topic: concept-article
9
-
ms.date: 02/07/2024
10
-
#CustomerIntent: As a <type of user>, I want <what?> so that <why?>.
9
+
ms.date: 02/10/2025
11
10
---
12
11
13
12
# Anycast routing with Azure Route Server
@@ -24,10 +23,10 @@ In the design of this scenario, the same IP address is advertised from virtual n
24
23
25
24
:::image type="content" source="./media/anycast/anycast.png" alt-text="Diagram shows an example of using IP anycast with Azure Route Server.":::
26
25
27
-
The decision of which of the available regions is selected is entirely based on routing attributes. If the routes from both regions are identical, the on-premises network typically uses equal-cost multi-path (ECMP) routing to send each application flow to each region. It's possible as well to modify the advertisements generated by each NVA in Azure to make one of the regions preferred. For example, using BGP AS Path prepending to establish a deterministic path from on-premises to the Azure workload.
26
+
The selection of a region among the available options is determined entirely by routing attributes. If the routes from both regions are identical, the on-premises network typically employs equal-cost multi-path (ECMP) routing to distribute application flows evenly across both regions. Additionally, you can adjust the route advertisements generated by each NVA in Azure to prioritize one region over the other. For instance, you can use BGP AS Path prepending to establish a preferred path from the on-premises network to the Azure workload.
28
27
29
28
> [!IMPORTANT]
30
-
> The NVAs advertising the routes should include some health check mechanism to stop advertising the route when the application is not available in their respective regions, to avoid blackholing traffic.
29
+
> The NVAs advertising the routes should include some health check mechanism to stop advertising the route when the application isn't available in their respective regions, to avoid blackholing traffic.
31
30
32
31
## Return traffic
33
32
@@ -37,5 +36,5 @@ Otherwise, traffic arriving to the application is still sourced from the origina
37
36
38
37
## Related content
39
38
40
-
*[Learn how Azure Route Server works with ExpressRoute](expressroute-vpn-support.md).
41
-
*[Learn how to peer Azure Route Server with a network virtual appliance (NVA)](tutorial-configure-route-server-with-quagga.md).
39
+
-[Learn how Azure Route Server works with ExpressRoute](expressroute-vpn-support.md)
40
+
-[Learn how to peer Azure Route Server with a network virtual appliance (NVA)](tutorial-configure-route-server-with-quagga.md)
0 commit comments