Skip to content

Commit ff30ad5

Browse files
committed
freshness
1 parent fcb78fd commit ff30ad5

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

articles/route-server/anycast.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,7 @@ author: halkazwini
66
ms.author: halkazwini
77
ms.service: azure-route-server
88
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
1110
---
1211

1312
# 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
2423

2524
:::image type="content" source="./media/anycast/anycast.png" alt-text="Diagram shows an example of using IP anycast with Azure Route Server.":::
2625

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.
2827

2928
> [!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.
3130
3231
## Return traffic
3332

@@ -37,5 +36,5 @@ Otherwise, traffic arriving to the application is still sourced from the origina
3736

3837
## Related content
3938

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

Comments
 (0)