You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-wan/route-maps-how-to-summarize-routes-leaving-your-virtual-wan.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ In this scenario, a Route-map will summarize the routes being advertised to the
54
54
55
55
1. Use the Route-map dashboard in hub 2 to verify the correct routes are currently being advertised to VPN branch 2 site.
56
56
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":::
58
58
59
59
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.
Copy file name to clipboardExpand all lines: articles/virtual-wan/route-maps-prepend-routes.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,11 +55,11 @@ In this scenario, the goal is to prepend route 10.5.0.192/26 from virtual networ
55
55
56
56
1. Use the Route-Map dashboard in hub 2 to verify the ASNs on routes are being advertised from the virtual network connection.
57
57
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":::
59
59
60
60
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.
61
61
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":::
63
63
64
64
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.
Copy file name to clipboardExpand all lines: articles/virtual-wan/route-maps-summarize-from-device-spoke-vnet-nva.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: 'How to configure Route-maps summarize routes from an NVA in a spoke virtual network'
3
3
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
5
5
author: cfields475
6
6
ms.service: azure-virtual-wan
7
7
ms.topic: how-to
@@ -27,7 +27,7 @@ Verify that you have met the following criteria before beginning your configurat
27
27
## Design
28
28
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.
29
29
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":::
31
31
32
32
Here's the addressing for this environment:
33
33
@@ -53,7 +53,7 @@ In this scenario, the goal is to summarize some routes being advertised to the h
53
53
54
54
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.
55
55
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":::
57
57
58
58
Use the Route-Map dashboard to verify the routes being sent to VPN branch 1.
59
59
@@ -75,7 +75,7 @@ In this scenario, the goal is to summarize some routes being advertised to the h
75
75
76
76
Using the Route-Map dashboard verify route 10.150.0.0/16 has been advertised to VPN branch 1
77
77
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":::
Copy file name to clipboardExpand all lines: articles/virtual-wan/route-maps-tag-routes.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Verify that you have met the following criteria before beginning your configurat
27
27
## Design
28
28
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.
29
29
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":::
31
31
32
32
Here's the addressing for this environment:
33
33
@@ -75,7 +75,7 @@ In this scenario, the goal is to tag route 10.5.0.192/26 form virtual network 3
75
75
76
76
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.
77
77
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":::
0 commit comments