Skip to content

Commit dd45d1c

Browse files
committed
commit
1 parent 4cca4f2 commit dd45d1c

4 files changed

+9
-9
lines changed

articles/virtual-wan/route-maps-how-to-summarize-routes-leaving-your-virtual-wan.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ In this scenario, a Route-map will summarize the routes being advertised to the
5454

5555
1. Use the Route-map dashboard in hub 2 to verify the correct routes are currently being advertised to VPN branch 2 site.
5656

57-
:::image type="content" source="./media/route-maps-how-to-summarize/db-one.png" alt-text="Screenshot shows before routes." lightbox="./media/route-maps-how-to-summarize/db-one.png":::
57+
:::image type="content" source="./media/route-maps-how-to-summarize/db-one.png" alt-text="Screenshot that shows routes before Route-Maps." lightbox="./media/route-maps-how-to-summarize/db-one.png":::
5858

5959
2. Create a Route-map to summarize the routes. Before you create your first time Route-map, see [How to configure Route-maps](route-maps-how-to.md) for more information.
6060

articles/virtual-wan/route-maps-prepend-routes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,11 +55,11 @@ In this scenario, the goal is to prepend route 10.5.0.192/26 from virtual networ
5555

5656
1. Use the Route-Map dashboard in hub 2 to verify the ASNs on routes are being advertised from the virtual network connection.
5757

58-
:::image type="content" source="./media/route-maps-prepend-routes/db-before-one.png" alt-text="Screenshot that shows the routes before Route-Map." lightbox="./media/route-maps-prepend-routes/db-before-one.png":::
58+
:::image type="content" source="./media/route-maps-prepend-routes/db-before-one.png" alt-text="Screenshot that shows the routes before Route-Map being applied." lightbox="./media/route-maps-prepend-routes/db-before-one.png":::
5959

6060
Look at the Route-Map dashboard for the VPN branch 2 to verify the ASNs for route 10.5.0.192/26 that are being sent to the branch office.
6161

62-
:::image type="content" source="./media/route-maps-prepend-routes/db-before-two.png" alt-text="Screenshot that shows the routes before Route-Map for the VPN branch." lightbox="./media/route-maps-prepend-routes/db-before-two.png":::
62+
:::image type="content" source="./media/route-maps-prepend-routes/db-before-two.png" alt-text="Screenshot that shows the routes before Route-Map being applied to the VPN branch." lightbox="./media/route-maps-prepend-routes/db-before-two.png":::
6363

6464
2. Create a Route-Map to tag the route. If this is your first time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information.
6565

articles/virtual-wan/route-maps-summarize-from-device-spoke-vnet-nva.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: 'How to configure Route-maps summarize routes from an NVA in a spoke virtual network'
33
titleSuffix: Azure Virtual WAN
4-
description: Learn how to configure Route-maps to summarize routes from an NVA
4+
description: Learn how to configure Route-maps to summarize routes from an NVA in a spoke virtual network
55
author: cfields475
66
ms.service: azure-virtual-wan
77
ms.topic: how-to
@@ -27,7 +27,7 @@ Verify that you have met the following criteria before beginning your configurat
2727
## Design
2828
In this situation, we have two hubs. Hub 1 has 2 VNets and a VPN branch office. One of the VNets has an NVA (network virtual appliance) peered with the hub. Hub 2 also has 2 VNets and a VPN branch office.
2929

30-
:::image type="content" source="./media/route-maps-how-to-summarize/environment.png" alt-text="Screenshot shows how to the Environment." lightbox="./media/route-maps-how-to-summarize/environment.png":::
30+
:::image type="content" source="./media/route-maps-how-to-summarize/environment.png" alt-text="Screenshot that shows to the Environment." lightbox="./media/route-maps-how-to-summarize/environment.png":::
3131

3232
Here's the addressing for this environment:
3333

@@ -53,7 +53,7 @@ In this scenario, the goal is to summarize some routes being advertised to the h
5353

5454
1. Use the Route-Map dashboard in hub 1 to verify the correct routes are currently being advertised from virtual network 1 to the hub.
5555

56-
:::image type="content" source="./media/route-maps-summarize-from-device-spoke-vnet-nva/db-before-one.png" alt-text="Screenshot that shows the routes before Route-maps." lightbox="./media/route-maps-summarize-from-device-spoke-vnet-nva/db-before-one.png":::
56+
:::image type="content" source="./media/route-maps-summarize-from-device-spoke-vnet-nva/db-before-one.png" alt-text="Screenshot that shows the routes before Route-maps." lightbox="./media/route-maps-summarize-from-device-spoke-vnet-nva/db-before-one.png":::
5757

5858
Use the Route-Map dashboard to verify the routes being sent to VPN branch 1.
5959

@@ -75,7 +75,7 @@ In this scenario, the goal is to summarize some routes being advertised to the h
7575

7676
Using the Route-Map dashboard verify route 10.150.0.0/16 has been advertised to VPN branch 1
7777

78-
:::image type="content" source="./media/route-maps-summarize-from-device-spoke-vnet-nva/db-after-two.png" alt-text="Screenshot that shows routes after Route-map being applied VPN branch." lightbox="./media/route-maps-summarize-from-device-spoke-vnet-nva/db-after-two.png":::
78+
:::image type="content" source="./media/route-maps-summarize-from-device-spoke-vnet-nva/db-after-two.png" alt-text="Screenshot that shows routes after Route-map being applied for the VPN branch." lightbox="./media/route-maps-summarize-from-device-spoke-vnet-nva/db-after-two.png":::
7979

8080
## Next steps
8181

articles/virtual-wan/route-maps-tag-routes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Verify that you have met the following criteria before beginning your configurat
2727
## Design
2828
In this situation, we have two hubs. Hub 1 has 2 VNets and a VPN branch office. One of the VNets has an (network virtual appliance) peered with the hub. Hub 2 also has 2 VNets and a VPN branch office.
2929

30-
:::image type="content" source="./media/route-maps-how-to-summarize/environment.png" alt-text="Screenshot that shows to the environment." lightbox="./media/route-maps-how-to-summarize/environment.png":::
30+
:::image type="content" source="./media/route-maps-how-to-summarize/environment.png" alt-text="Screenshot that shows the environment." lightbox="./media/route-maps-how-to-summarize/environment.png":::
3131

3232
Here's the addressing for this environment:
3333

@@ -75,7 +75,7 @@ In this scenario, the goal is to tag route 10.5.0.192/26 form virtual network 3
7575

7676
look at the Route-Map dashboard for the VPN branch connection to verify route 10.5.0.192/26 has the BGP community 3356:70 being advertised to the VPN branch office 2.
7777

78-
:::image type="content" source="./media/route-maps-tag-routes/rm-after-two.png" alt-text="Screenshot that shows routes after the Route-map has been applied to VPN branch." lightbox="./media/route-maps-tag-routes/rm-after-two.png":::
78+
:::image type="content" source="./media/route-maps-tag-routes/rm-after-two.png" alt-text="Screenshot that shows routes after the Route-map has been applied for the VPN branch." lightbox="./media/route-maps-tag-routes/rm-after-two.png":::
7979

8080
## Next steps
8181

0 commit comments

Comments
 (0)