Skip to content

Commit 9197cfc

Browse files
committed
commit
1 parent 8512e81 commit 9197cfc

File tree

5 files changed

+4
-4
lines changed

5 files changed

+4
-4
lines changed

articles/virtual-wan/next-hop-ip.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ In this scenario, the virtual hub named "Hub 1" is connected to a virtual networ
4343

4444
Verify what routes are currently being advertised and what the next hop IPs are for those routes.
4545

46-
:::image type="content" source="./media/next-hop-ip/effectiveroutes-before.png" alt-text="Screenshot that shows the route before changing the next hop IP." lightbox="./media/next-hop-ip/effectiveroutes-before.png":::
46+
:::image type="content" source="./media/next-hop-ip/effective-routes-before.png" alt-text="Screenshot that shows the route before changing the next hop IP." lightbox="./media/next-hop-ip/effective-routes-before.png":::
4747

4848
The next hop for route **10.222.222.0/24** is the NVA.
4949

@@ -53,19 +53,19 @@ In this scenario, the virtual hub named "Hub 1" is connected to a virtual networ
5353

5454
Check the effective routes to verify the next hop IP for the route **10.222.222.0/24** has changed to the load balancer (**192.168.1.40**).
5555

56-
:::image type="content" source="./media/next-hop-ip/effectiveroutes-after.png" alt-text="Screenshot showing the routes after changing the next hop IP." lightbox="./media/next-hop-ip/effectiveroutes-after.png":::
56+
:::image type="content" source="./media/next-hop-ip/effective-routes-after.png" alt-text="Screenshot showing the routes after changing the next hop IP." lightbox="./media/next-hop-ip/effective-routes-after.png":::
5757

5858
## Troubleshooting
5959

6060
1. Verify BGP peering with the hub is set up correctly and working before attempting to set a custom next hop. Instructions on setting up BGP peering with the hub can be found [here](scenario-bgp-peering-hub.md).
6161

6262
2. Verify the BGP peering status is up. In the "BGP peer" section, select on "BGP Status".
6363

64-
:::image type="content" source="./media/next-hop-ip/bgppeers.png" alt-text="Screenshot showing the confonfigured BGP peers." lightbox="./media/next-hop-ip/bgppeers.png":::
64+
:::image type="content" source="./media/next-hop-ip/bgp-peers.png" alt-text="Screenshot showing the confonfigured BGP peers." lightbox="./media/next-hop-ip/bgp-peers.png":::
6565

6666
Verify the BGP peer is up.
6767

68-
:::image type="content" source="./media/next-hop-ip/bgppeersup.png" alt-text="Screenshot showing the bgp peers are up." lightbox="./media/next-hop-ip/bgppeersup.png":::
68+
:::image type="content" source="./media/next-hop-ip/bgp-peers-up.png" alt-text="Screenshot showing the bgp peers are up." lightbox="./media/next-hop-ip/bgp-peers-up.png":::
6969

7070
3. Check the current limitations for BGP peering with the hub.
7171

0 commit comments

Comments
 (0)