Skip to content

Commit 4068c08

Browse files
Merge pull request #306980 from siddomala/bowtie2ARS
Added more details for ExpressRoute MSEE hairpinning with Route Server
2 parents c58dd4c + cbdc013 commit 4068c08

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ No. By default, Azure Route Server doesn't propagate routes it receives from an
121121

122122
### Do NVA-advertised routes get propagated from one Route Server to another Route Server via ExpressRoute MSEE?
123123

124-
No. If **branch-to-branch** is enabled, then the NVA-advertised routes will be advertised to the ExpressRoute-connected on-premises. However, the NVA-advertised routes will be dropped by the second Route Server. To illustrate this, the diagram below shows the SDWAN on-premises advertising 10.3.0.0/16 to the SDWAN NVA. This route gets learned by the first Route Server, and so any workloads in VNet 1 (or peered to VNet 1) also learn this route. In addition, the ExpressRoute-connected on-premises learns the 10.3.0.0/16 route if **branch-to-branch** is enabled. However, the second Route Server (in VNet 2) does not learn the 10.3.0.0/16 route, and so this route will not be learned by any workloads in VNet 2.
124+
No. If **branch-to-branch** is enabled, then the NVA-advertised routes will be advertised to the ExpressRoute-connected on-premises. However, the NVA-advertised routes will be dropped by the second Route Server. To illustrate this, the diagram below shows the SDWAN on-premises advertising 10.3.0.0/16 to the SDWAN NVA. This route gets learned by the first Route Server, and so any workloads in VNet 1 (or peered to VNet 1) also learn this route. In addition, the ExpressRoute-connected on-premises learns the 10.3.0.0/16 route if **branch-to-branch** is enabled. However, the second Route Server (in VNet 2) does not learn the 10.3.0.0/16 route, and so this route will not be learned by any workloads in VNet 2. As a result, the 10.3.0.0/16 on-premises network will be unreachable from any workloads in VNet 2 and peered to VNet 2.
125125

126126
:::image type="content" source="./media/faq/route-server-msee-hairpin.png" alt-text="Diagram showing NVA-advertised route not being learned by second Route Server via ExpressRoute MSEE bow-tie.":::
127127

0 commit comments

Comments
 (0)