Skip to content

Commit d47fa47

Browse files
committed
first draft
1 parent ad7df42 commit d47fa47

File tree

2 files changed

+5
-0
lines changed

2 files changed

+5
-0
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,8 @@ If you enable BGP on the VPN gateway, the gateway learns *On-premises 1* routes
3838

3939
> [!IMPORTANT]
4040
> Azure VPN gateway must be configured in [**active-active**](../vpn-gateway/vpn-gateway-activeactive-rm-powershell.md) mode and have the ASN set to 65515. It's not a requirement to have BGP enabled on the VPN gateway to communicate with the Route Server.
41+
>
42+
> In addition, the VPN gateway must be deployed in the same virtual network as Route Server in order for BGP peering to be successfully established.
4143
4244
:::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.":::
4345

articles/route-server/route-server-faq.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,9 @@ Azure Router Server needs to ensure connectivity to the backend service that man
4040

4141
No. We'll add IPv6 support in the future. If you have deployed an ExpressRoute virtual network gateway in a virtual network with an IPv6 address space and later deploy an Azure Route Server in the same virtual network, this will break ExpressRoute connectivity for IPv6 traffic.
4242

43+
> [!WARNING]
44+
> When you deploy an Azure Route Server in a virtual network with an IPv6 address space, this will also break IPv4 connectivity for existing ExpressRoute traffic. This issue will be fixed in our next release.
45+
4346
## Routing
4447

4548
### Does Azure Route Server route data traffic between my NVA and my VMs?

0 commit comments

Comments
 (0)