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/route-server-faq.md
+31-26Lines changed: 31 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,76 +1,77 @@
1
1
---
2
-
title: Azure Route Server frequently asked questions (FAQs)
2
+
title: Azure Route Server frequently asked questions (FAQ)
3
3
description: Find answers to frequently asked questions about Azure Route Server.
4
4
services: route-server
5
5
author: halkazwini
6
6
ms.service: route-server
7
7
ms.topic: conceptual
8
-
ms.date: 12/06/2022
8
+
ms.date: 02/23/2023
9
9
ms.author: halkazwini
10
-
ms.custom: template-concept
10
+
ms.custom: template-concept, engagement-fy23
11
11
---
12
12
13
-
# Azure Route Server frequently asked questions (FAQs)
13
+
# Azure Route Server frequently asked questions (FAQ)
14
14
15
15
## What is Azure Route Server?
16
16
17
17
Azure Route Server is a fully managed service that allows you to easily manage routing between your network virtual appliance (NVA) and your virtual network.
18
18
19
-
### Is Azure Route Server just a VM?
19
+
### Is Azure Route Server just a virtual machine?
20
20
21
-
No. Azure Route Server is a service designed with high availability. If it's deployed in an Azure region that supports [Availability Zones](../availability-zones/az-overview.md), it will have zone-level redundancy.
21
+
No. Azure Route Server is a service designed with high availability. Your route server has zone-level redundancy if you deploy it in an Azure region that supports [Availability Zones](../availability-zones/az-overview.md).
22
22
23
-
### How many Azure Route Servers can I create in a virtual network?
23
+
### How many route servers can I create in a virtual network?
24
24
25
-
You can create only one route server in a virtual network. It must be deployed in a dedicated subnet called *RouteServerSubnet*.
25
+
You can create only one route server in a virtual network. You must deploy the route server in a dedicated subnet called *RouteServerSubnet*.
26
26
27
27
### Does Azure Route Server support virtual network peering?
28
28
29
-
Yes, if you peer a virtual network hosting the Azure Route Server to another virtual network and you enable Use Remote Gateway on the second virtual network, Azure Route Server will learn the address spaces of that virtual network and send them to all the peered NVAs. It will also program the routes from the NVAs into the routing table of the VMs in the peered virtual network.
29
+
Yes, if you peer a virtual network hosting the Azure Route Server to another virtual network and you enable **Use the remote virtual network's gateway or Route Server**on the second virtual network, Azure Route Server learns the address spaces of the peered virtual network and send them to all the peered network virtual appliances (NVAs). It also programs the routes from the NVAs into the route table of the virtual machines in the peered virtual network.
30
30
31
31
32
32
### <aname = "protocol"></a>What routing protocols does Azure Route Server support?
33
33
34
-
Azure Route Server supports Border Gateway Protocol (BGP) only. Your NVA needs to support multi-hop external BGP because you’ll need to deploy Azure Route Server in a dedicated subnet in your virtual network. The [ASN](https://en.wikipedia.org/wiki/Autonomous_system_(Internet)) you choose must be different from the one Azure Route Server uses when you configure the BGP on your NVA.
34
+
Azure Route Server supports only Border Gateway (BGP) Protocol. Your network virtual appliance (NVA) must support multi-hop external BGP because you need to deploy the Route Server in a dedicated subnet in your virtual network. When you configure the BGP on your NVA, the ASN you choose must be different from the Route Server ASN.
35
35
36
36
### Does Azure Route Server route data traffic between my NVA and my VMs?
37
37
38
-
No. Azure Route Server only exchanges BGP routes with your NVA. The data traffic goes directly from the NVA to the destination VM and directly from the VM to the NVA.
38
+
No. Azure Route Server only exchanges BGP routes with your network virtual appliance (NVA). The data traffic goes directly from the NVA to the destination virtual machine (VM) and directly from the VM to the NVA.
39
39
40
40
### Does Azure Route Server store customer data?
41
-
No. Azure Route Server only exchanges BGP routes with your NVA and then propagates them to your virtual network.
41
+
42
+
No. Azure Route Server only exchanges BGP routes with your network virtual appliance (NVA) and then propagates them to your virtual network.
42
43
43
44
### Why does Azure Route Server require a public IP address?
44
45
45
-
Azure Router Server needs to ensure connectivity to the backend service that manages the Route Server configuration, as such a public IP address is required. This public IP address doesn't constitute a security exposure of your virtual network.
46
+
Azure Router Server needs to ensure connectivity to the backend service that manages the Route Server configuration, that's why it needs the public IP address. This public IP address doesn't constitute a security exposure of your virtual network.
46
47
47
48
### Does Azure Route Server support IPv6?
48
49
49
50
No. We'll add IPv6 support in the future.
50
51
51
52
### If Azure Route Server receives the same route from more than one NVA, how does it handle them?
52
53
53
-
If the route has the same AS path length, Azure Route Server will program multiple copies of the route, each with a different next hop, to the VMs in the virtual network. When the VMs send traffic to the destination of this route, the VM hosts will do Equal-Cost Multi-Path (ECMP) routing. However, if one NVA sends the route with a shorter AS path length than other NVAs, Azure Route Server will only program the route that has the next hop set to this NVA to the VMs in the virtual network.
54
+
If the route has the same AS path length, Azure Route Server will program multiple copies of the route, each with a different next hop, to the virtual machines (VMs) in the virtual network. When a VM sends traffic to the destination of this route, the VM host uses Equal-Cost Multi-Path (ECMP) routing. However, if one NVA sends the route with a shorter AS path length than other NVAs, Azure Route Server will only program the route that has the next hop set to this NVA to the VMs in the virtual network.
54
55
55
56
### Does Azure Route Server preserve the BGP AS Path of the route it receives?
56
57
57
58
Yes, Azure Route Server propagates the route with the BGP AS Path intact.
58
59
59
-
### Do I need to peer each NVA with both Route Server instances?
60
-
Yes, to ensure that VNet routes are successfully advertised over the target NVA connections, and to configure High Availability, we recommend peering each NVA instances with both instances of Route Server.
60
+
### Do I need to peer each NVA with both Azure Route Server instances?
61
+
62
+
Yes, to ensure that virtual network routes are successfully advertised over the target NVA connections, and to configure High Availability, we recommend peering each NVA instance with both instances of Route Server.
61
63
62
64
### Does Azure Route Server preserve the BGP communities of the route it receives?
63
65
64
66
Yes, Azure Route Server propagates the route with the BGP communities as is.
65
67
66
68
### What is the BGP timer setting of Azure Route Server?
67
69
68
-
The Keep-alive timer is set to 60 seconds and the Hold-down timer 180 seconds.
70
+
Azure Route Server Keepalive timer is 60 seconds and the Hold timer is 180 seconds.
69
71
70
72
### What Autonomous System Numbers (ASNs) can I use?
71
73
72
-
You can use your own public ASNs or private ASNs in your network virtual appliance. You can't use the ranges reserved by Azure or IANA.
73
-
The following ASNs are reserved by Azure or IANA:
74
+
You can use your own public ASNs or private ASNs in your network virtual appliance (NVA). You can't use ASNs reserved by Azure or IANA.
74
75
75
76
* ASNs reserved by Azure:
76
77
* Public ASNs: 8074, 8075, 12076
@@ -82,11 +83,11 @@ The following ASNs are reserved by Azure or IANA:
82
83
83
84
No, Azure Route Server supports only 16-bit (2 bytes) ASNs.
84
85
85
-
### Can I associate a User Defined Route (UDR) to the RouteServerSubnet?
86
+
### Can I associate a UDR to the *RouteServerSubnet*?
86
87
87
-
No, Azure Route Server doesn't support configuring a UDR on the RouteServerSubnet. It should be noted that Azure Route Server doesn't route any data traffic between NVAs and VMs.
88
+
No, Azure Route Server doesn't support configuring a user defined route (UDR) on the *RouteServerSubnet*. Azure Route Server doesn't route any data traffic between network virtual appliances (NVAs) and virtual machines (VMs).
88
89
89
-
### Can I associate a Network Security group (NSG) to the RouteServerSubnet?
90
+
### Can I associate a network security group (NSG) to the RouteServerSubnet?
90
91
91
92
No, Azure Route Server doesn't support NSG association to the RouteServerSubnet.
92
93
@@ -102,15 +103,19 @@ No, Azure Route Server doesn't forward data traffic. To enable transit connectiv
102
103
103
104
### Can I use Azure Route Server to direct traffic between subnets in the same virtual network to flow inter-subnet traffic through the NVA?
104
105
105
-
No. System routes for traffic related to virtual network, virtual network peerings, or virtual network service endpoints, are preferred routes, even if BGP routes are more specific. As Route Server uses BGP to advertise routes, currently this is not supported by design. You must continue to use UDRs to force override the routes, and you can't utilize BGP to quickly failover these routes. You must continue to use a thirdparty solution to update the UDRs via the API in a failover situation, or use an Azure Load Balancer with HA ports mode to direct traffic.
106
+
No. Azure Route Server uses BGP to advertise routes. System routes for traffic related to virtual network, virtual network peerings, or virtual network service endpoints, are preferred routes, even if BGP routes are more specific. You must continue to use user defined routes (UDRs) to override system routes, and you can't utilize BGP to quickly fail over these routes. You must continue to use a third-party solution to update the UDRs via the API in a failover situation, or use an Azure Load Balancer with HA ports mode to direct traffic.
106
107
107
-
You can still use Route Server to direct traffic between subnets in different virtual networks to flow using the NVA. The only possible design that may work is one subnet per "spoke" virtual network and all virtual networks are peered to a "hub" virtual network, but this is very limiting and needs to take into scaling considerations and Azure's maximum limits on virtual networks vs subnets.
108
+
You can still use Route Server to direct traffic between subnets in different virtual networks to flow using the NVA. A possible design that may work is one subnet per "spoke" virtual network and all "spoke" virtual networks are peered to a "hub" virtual network. This design is very limiting and needs to take into scaling considerations and Azure's maximum limits on virtual networks vs subnets.
108
109
109
110
### Can Azure Route Server filter out routes from NVAs?
110
111
111
-
Azure Route Server supports ***NO_ADVERTISE*** BGP Community. If an NVA advertises routes with this community string to the route server, the route server won't advertise it to other peers including the ExpressRoute gateway. This feature can help reduce the number of routes to be sent from Azure Route Server to ExpressRoute.
112
+
Azure Route Server supports ***NO_ADVERTISE*** BGP community. If a network virtual appliance (NVA) advertises routes with this community string to the route server, the route server doesn't advertise it to other peers including the ExpressRoute gateway. This feature can help reduce the number of routes sent from Azure Route Server to ExpressRoute.
113
+
114
+
### Can Azure Route Server provide transit between ExpressRoute and a Point-to-Site (P2S) VPN gateway connection when enabling the *branch-to-branch*?
115
+
116
+
No, Azure Route Server provides transit only between ExpressRoute and Site-to-Site (S2S) VPN gateway connections (when enabling the *branch-to-branch* setting).
112
117
113
-
## <aname = "limitations"></a>Route Server Limits
118
+
###<aname = "limitations"></a>What are Azure Route Server limits?
114
119
115
120
Azure Route Server has the following limits (per deployment).
0 commit comments