Skip to content

Commit eaee23c

Browse files
Merge pull request #266573 from halkazwini/rs-er
Add a note about ER to ER connectivity
2 parents d52e589 + 975ab53 commit eaee23c

File tree

1 file changed

+15
-10
lines changed

1 file changed

+15
-10
lines changed

articles/route-server/expressroute-vpn-support.md

Lines changed: 15 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6,24 +6,29 @@ author: halkazwini
66
ms.author: halkazwini
77
ms.service: route-server
88
ms.topic: concept-article
9-
ms.date: 08/15/2023
9+
ms.date: 02/16/2024
10+
11+
#CustomerIntent: As an Azure administrator, I want to deploy Azure Route Server with ExpressRoute and Azure VPN so that routes can be exchanged between the two on-premises networks.
1012
---
1113

1214
# Azure Route Server support for ExpressRoute and Azure VPN
1315

14-
Azure Route Server supports not only third-party network virtual appliances (NVA) running on Azure but also seamlessly integrates with ExpressRoute and Azure VPN gateways. You don’t need to configure or manage the BGP peering between the gateway and Azure Route Server. You can enable route exchange between the gateways and Azure Route Server by enabling [branch-to-branch](quickstart-configure-route-server-portal.md#configure-route-exchange) in Azure portal. If you prefer, you can use [Azure PowerShell](quickstart-configure-route-server-powershell.md#route-exchange) or [Azure CLI](quickstart-configure-route-server-cli.md#configure-route-exchange) to enable the route exchange with the Route Server.
16+
Azure Route Server supports not only third-party network virtual appliances (NVA) in Azure but also seamlessly integrates with ExpressRoute and Azure VPN gateways. You don’t need to configure or manage the BGP peering between the gateway and Azure Route Server. You can enable route exchange between the gateways and Azure Route Server by enabling [branch-to-branch](quickstart-configure-route-server-portal.md#configure-route-exchange) in Azure portal. If you prefer, you can use [Azure PowerShell](quickstart-configure-route-server-powershell.md#route-exchange) or [Azure CLI](quickstart-configure-route-server-cli.md#configure-route-exchange) to enable the route exchange with the Route Server.
1517

1618
[!INCLUDE [downtime note](../../includes/route-server-note-vng-downtime.md)]
1719

1820
## How does it work?
1921

2022
When you deploy an Azure Route Server along with a virtual network gateway and an NVA in a virtual network, by default Azure Route Server doesn’t propagate the routes it receives from the NVA and virtual network gateway between each other. Once you enable **branch-to-branch** in Route Server, the virtual network gateway and the NVA exchange their routes.
2123

22-
For example, in the following diagram:
24+
> [!IMPORTANT]
25+
> ExpressRoute branch-to-branch connectivity is not supported. If you have two (or more) ExpressRoute circuits connected to the same ExpressRoute virtual network gateway, routes from one circuit are not advertised to the other. If you want to enable on-premises to on-premises connectivity over ExpressRoute, consider configuring ExpressRoute Global Reach. For more information, see [About Azure ExpressRoute Global Reach](../expressroute/expressroute-global-reach.md).
26+
27+
The following diagram shows an example of using Route Server to exchange routes between an ExpressRoute and SDWAN appliance:
2328

24-
* The SDWAN appliance receives from Azure Route Server the route of *On-premises 2*, which is connected to ExpressRoute circuit, along with the route of the virtual network.
29+
- The SDWAN appliance receives from Azure Route Server the route of *On-premises 2*, which is connected to ExpressRoute circuit, along with the route of the virtual network.
2530

26-
* The ExpressRoute gateway receives from Azure Route Server the route of *On-premises 1*, which is connected to the SDWAN appliance, along with the route of the virtual network.
31+
- The ExpressRoute gateway receives from Azure Route Server the route of *On-premises 1*, which is connected to the SDWAN appliance, along with the route of the virtual network.
2732

2833
:::image type="content" source="./media/expressroute-vpn-support/expressroute-with-route-server.png" alt-text="Diagram showing ExpressRoute gateway and SDWAN NVA exchanging routes through Azure Route Server.":::
2934

@@ -37,10 +42,10 @@ If you enable BGP on the VPN gateway, the gateway learns *On-premises 1* routes
3742
:::image type="content" source="./media/expressroute-vpn-support/expressroute-and-vpn-with-route-server.png" alt-text="Diagram showing ExpressRoute and VPN gateways exchanging routes through Azure Route Server.":::
3843

3944
> [!NOTE]
40-
> When the same route is learned over ExpressRoute, Azure VPN or an SDWAN appliance, the ExpressRoute network will be preferred.
45+
> When the same route is learned over ExpressRoute, Azure VPN or an SDWAN appliance, the ExpressRoute network will be preferred by default. You can configure routing preference to influence Route Server route selection. For more information, see [Routing preference (preview)](hub-routing-preference.md).
4146
42-
## Next steps
47+
## Related content
4348

44-
- Learn more about [Azure Route Server](route-server-faq.md).
45-
- Learn how to [configure Azure Route Server](quickstart-configure-route-server-powershell.md).
46-
- Learn more about [Azure ExpressRoute and Azure VPN coexistence](../expressroute/how-to-configure-coexisting-gateway-portal.md).
49+
- [Azure Route Server frequently asked questions (FAQ)](route-server-faq.md).
50+
- [Configure Azure Route Server](quickstart-configure-route-server-powershell.md).
51+
- [Azure ExpressRoute and Azure VPN coexistence](../expressroute/how-to-configure-coexisting-gateway-portal.md?toc=/azure/route-server/toc.json).

0 commit comments

Comments
 (0)