Skip to content

Commit 880bcdd

Browse files
Merge pull request #265620 from halkazwini/rs-hop
Update screenshot
2 parents fb912a9 + 3f5b55a commit 880bcdd

File tree

2 files changed

+6
-5
lines changed

2 files changed

+6
-5
lines changed
31.3 KB
Loading

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

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,20 @@
11
---
2-
title: Next Hop IP Support
2+
title: Next hop IP support
33
titleSuffix: Azure Route Server
4-
description: Learn how to use Next Hop IP feature in Azure Route Server to peer with network virtual appliances (NVAs) behind an internal load balancer.
4+
description: Learn how to use the next hop IP support in Azure Route Server to peer with network virtual appliances (NVAs) behind an internal load balancer.
55
author: halkazwini
66
ms.author: halkazwini
77
ms.service: route-server
88
ms.topic: concept-article
9-
ms.date: 08/21/2023
9+
ms.date: 02/07/2024
10+
#CustomerIntent: As an Azure administrator, I want to use the frontend IP address of the load balancer as the next hop IP so packets are routed to the load balancer to get to the NVAs that are in the backend pool.
1011
---
1112

1213
# Next Hop IP support
1314

1415
With the support for Next Hop IP in Azure Route Server, you can peer with network virtual appliances (NVAs) that are deployed behind an Azure internal load balancer. The internal load balancer lets you set up active-passive connectivity scenarios and use load balancing to improve connectivity performance.
1516

16-
:::image type="content" source="./media/next-hop-ip/route-server-next-hop.png" alt-text="Diagram of two NVAs behind a load balancer and a Route Server.":::
17+
:::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.":::
1718

1819
## Active-passive NVA connectivity
1920

@@ -29,7 +30,7 @@ You can deploy a set of active-active NVAs behind an internal load balancer to o
2930

3031
Next hop IPs are set up in the BGP configuration of the target NVAs. The Next hop IP isn't part of the Azure Route Server configuration.
3132

32-
## Next steps
33+
## Related content
3334

3435
- Learn how to [configure Azure Route Server](quickstart-configure-route-server-portal.md).
3536
- Learn how to [monitor Azure Route Server](monitor-route-server.md).

0 commit comments

Comments
 (0)