Skip to content

Commit 59b1eaa

Browse files
committed
load balancer in same region
1 parent e0ccd08 commit 59b1eaa

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/route-server/next-hop-ip.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,9 @@ With the support for Next hop IP in Azure Route Server, you can peer with networ
1717

1818
:::image type="content" source="./media/next-hop-ip/route-server-next-hop.png" alt-text="Diagram of a Route Server peered with two NVAs behind an internal load balancer.":::
1919

20+
> [!NOTE]
21+
> The load balancer must be in the same region as the Route Server. If the load balancer is in a different region than the Route Server, then connectivity to these NVAs will not be functional.
22+
2023
## Active-passive NVA connectivity
2124

2225
You can deploy a set of active-passive NVAs behind an internal load balancer to ensure symmetrical routing to and from the NVA. With the support for Next hop IP, you can define the next hop for both the active and passive NVAs as the IP address of the internal load balancer and set up the load balancer to direct traffic towards the Active NVA instance.

0 commit comments

Comments
 (0)