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/how-to-configure-route-maps-to-drop-inbound-routes-from-branch-sites.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ This article helps you use the Route-maps feature to drop routes from branch sit
16
16
17
17
## Prerequisites
18
18
19
-
Verify that you've met the following criteria before beginning your configuration:
19
+
Verify that you have met the following criteria before beginning your configuration:
20
20
21
21
* You have virtual WAN (VWAN) with a connection (S2S, P2S, or ExpressRoute) already configured.
22
22
@@ -26,27 +26,27 @@ Verify that you've met the following criteria before beginning your configuratio
26
26
27
27
## Design
28
28
29
-
In this situation we have two hubs. Hub 1 has 2 VNets and a VPN branch office. One of the VNets has an NVA peered with the hub. Hub 2 also has 2 VNets and a VPN branch office.
29
+
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.
30
30
31
-
:::image type="content" source="./media/route-maps-how-to-summarize/environment.png" alt-text="Screenshot shows how to the Enviroment." lightbox="./media/route-maps-how-to-summarize/environment.png":::
31
+
:::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":::
## Scenario: Drop inbound routes from Branch sites
47
+
## Scenario: Drop inbound routes from Branch sites
48
48
49
-
In this scenario, the goal is to drop routes being advertised from VPN branch site 1. In this example we will be taking the routes 10.122.1.0/24,10.122.2.0/24, 10.122.3.0/24 and dropping them.
49
+
In this scenario, the goal is to drop routes being advertised from VPN branch site 1. In this example we'll be taking the routes 10.122.1.0/24,10.122.2.0/24, 10.122.3.0/24 and dropping them.
50
50
51
51
:::image type="content" source="./media/route-maps-how-to-drop/drop.png" alt-text="Screenshot that shows the Scenario." lightbox="./media/route-maps-how-to-drop/drop.png":::
52
52
@@ -60,9 +60,9 @@ In this scenario, the goal is to drop routes being advertised from VPN branch si
60
60
61
61
:::image type="content" source="./media/route-maps-how-to-drop/er_before.png" alt-text="Screenshot that shows routes before." lightbox="./media/route-maps-how-to-drop/er_before.png":::
62
62
63
-
2. Create a Route-Map to drop the routes. If this is your frist time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information.
63
+
2. Create a Route-Map to drop the routes. If this is your first time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information.
64
64
65
-
The Route-Map will have a match rule for route 10.122.2.0/16. The action **Drop**will be selected.
65
+
The Route-Map will have a match rule for route 10.122.2.0/16. The action **Drop**is selected.
66
66
67
67
:::image type="content" source="./media/route-maps-how-to-drop/rm.png" alt-text="Screenshot that shows the Route-map." lightbox="./media/route-maps-how-to-drop/rm.png":::
Copy file name to clipboardExpand all lines: articles/virtual-wan/how-to-configure-route-maps-to-prepend-routes.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ This article helps you use the Route-maps feature to prepend routes using the Az
16
16
17
17
## Prerequisites
18
18
19
-
Verify that you've met the following criteria before beginning your configuration:
19
+
Verify that you have met the following criteria before beginning your configuration:
20
20
21
21
* You have virtual WAN (VWAN) with a connection (S2S, P2S, or ExpressRoute) already configured.
22
22
@@ -25,49 +25,49 @@ Verify that you've met the following criteria before beginning your configuratio
25
25
* Be sure to view [About Route-maps](route-maps-about.md#considerations-and-limitations) for considerations and limitations before proceeding with configuration steps.
26
26
27
27
## Design
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 peered with the hub. Hub 2 also has 2 VNets and a VPN branch office.
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 Enviroment." 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 shows how to the Environment." lightbox="./media/route-maps-how-to-summarize/environment.png":::
:::image type="content" source="./media/route-maps-how-to-prepend/Prepend.png" alt-text="Screenshot that shows the Scenario." lightbox="./media/route-maps-how-to-prepend/Prepend.png":::
53
53
54
54
## Workflow
55
55
56
-
1. Use the Route-Map dashboard in hub 2 to verify the ASNs on routes are being advertised from the VNet connection.
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
58
:::image type="content" source="./media/route-maps-how-to-prepend/db_before_one.png" alt-text="Screenshot that shows the routes before Route-Map." lightbox="./media/route-maps-how-to-prepend/db_before_one.png":::
59
59
60
-
look at the Route-Map dashboard for the VPN brach 2 to verify the ASNs for route 10.5.0.192/26 that are being sent to the branch office.
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
62
:::image type="content" source="./media/route-maps-how-to-prepend/db_before_two.png" alt-text="Screenshot that shows the routes before Route-Map." lightbox="./media/route-maps-how-to-prepend/db_before_two.png":::
63
63
64
-
2. Create a Route-Map to tag the route. If this is your frist time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information.
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.
65
65
66
-
The Route-Map will have a match rule for route 10.5.0.192/26. The action **modify** will be selected. Route Modification will have an**Prepend** for **AS Path** 65533.
66
+
The Route-Map will have a match rule for route 10.5.0.192/26. The action **modify** will be selected. Route Modification has a**Prepend** for **AS Path** 65533.
67
67
68
68
:::image type="content" source="./media/route-maps-how-to-prepend/rm.png" alt-text="Screenshot that shows the Route-Map." lightbox="./media/route-maps-how-to-prepend/rm.png":::
69
69
70
-
3. Apply the Route-Map on the VNet 3 connection. The Route-Map will be applied in the inbound direction.
70
+
3. Apply the Route-Map on the virtual network 3 connection. The Route-Map will be applied in the inbound direction.
71
71
72
72
:::image type="content" source="./media/route-maps-how-to-prepend/apply.png" alt-text="Screenshot the Route-map being applied." lightbox="./media/route-maps-how-to-prepend/apply.png":::
Copy file name to clipboardExpand all lines: articles/virtual-wan/how-to-configure-route-maps-to-summarize-routes-from-an-device-a-spoke-vNet.md
+19-19Lines changed: 19 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: 'How to configure Route-maps summarize routes from an NVA in a spoke VNet'
2
+
title: 'How to configure Route-maps summarize routes from an NVA in a spoke virtual network'
3
3
titleSuffix: Azure Virtual WAN
4
4
description: Learn how to configure Route-maps to summarize routes from an NVA
5
5
author: cfields475
@@ -10,13 +10,13 @@ ms.author: cfields
10
10
ms.custom: references_region
11
11
12
12
---
13
-
# How to configure Route-maps to summarize routes from an NVA in a spoke VNet
13
+
# How to configure Route-maps to summarize routes from an NVA in a spoke virtual network
14
14
15
-
This article helps you use the Route-maps feature to summarize routes from an NVA in a spoke VNet using the Azure portal. For more information about Virtual WAN Route-maps, see [About Route-maps](route-maps-about.md).
15
+
This article helps you use the Route-maps feature to summarize routes from an NVA in a spoke virtual network using the Azure portal. For more information about Virtual WAN Route-maps, see [About Route-maps](route-maps-about.md).
16
16
17
17
## Prerequisites
18
18
19
-
Verify that you've met the following criteria before beginning your configuration:
19
+
Verify that you have met the following criteria before beginning your configuration:
20
20
21
21
* You have virtual WAN (VWAN) with a connection (S2S, P2S, or ExpressRoute) already configured.
22
22
@@ -25,47 +25,47 @@ Verify that you've met the following criteria before beginning your configuratio
25
25
* Be sure to view [About Route-maps](route-maps-about.md#considerations-and-limitations) for considerations and limitations before proceeding with configuration steps.
26
26
27
27
## Design
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 peered with the hub. Hub 2 also has 2 VNets and a VPN branch office.
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 Enviroment." 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 shows how to the Environment." lightbox="./media/route-maps-how-to-summarize/environment.png":::
## Scenario: Summarize routes from an NVA in a spoke VNet
46
+
## Scenario: Summarize routes from an NVA in a spoke virtual network
47
47
48
-
In this scenario, the goal is to summarize some routes being advertised to the hub from the NVA in VNet 1. In this example we will be taking the routes 10.150.1.0/24, 10.150.2.0/24, 10.150.3.0/24, 10.150.4.0/24, and summarizing them to 10.150.0.0/16
48
+
In this scenario, the goal is to summarize some routes being advertised to the hub from the NVA in virtual network 1. In this example we'll be taking the routes 10.150.1.0/24, 10.150.2.0/24, 10.150.3.0/24, 10.150.4.0/24, and summarizing them to 10.150.0.0/16
49
49
50
50
:::image type="content" source="./media/route-maps-how-to-nva/nva.png" alt-text="Screenshot that shows the Scenario." lightbox="route-maps-how-to-nva/nva.png":::
51
51
52
52
## Workflow
53
53
54
-
1. Use the Route-Map dashboard in hub 1 to verify the correct routes are currently being advertised from VNet 1 to the hub.
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
56
:::image type="content" source="./media/route-maps-how-to-nva/db_before_one.png" alt-text="Screenshot that shows the routes before Route-maps." lightbox="route-maps-how-to-nva/db_before_one.png":::
57
57
58
-
use the Route-Map dashboard to verify the routes being sent to VPN branch 1.
58
+
Use the Route-Map dashboard to verify the routes being sent to VPN branch 1.
59
59
60
60
:::image type="content" source="./media/route-maps-how-to-nva/db_before_2.png" alt-text="Screenshot that shows the routes before Route-maps." lightbox="route-maps-how-to-nva/db_before_2.png":::
61
61
62
-
2. Create a Route-Map to tag the route. If this is your frist time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information.
62
+
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.
63
63
64
-
The Route-Map will have a match rule for route 10.150.0.0/16. The action **modify** will be selected. Route Modification will have an **Replace** for **RoutePrefix** 10.150.0.0/16.
64
+
The Route-Map will have a match rule for route 10.150.0.0/16. The action **modify** will be selected. Route Modification has an **Replace** for **RoutePrefix** 10.150.0.0/16.
65
65
66
66
:::image type="content" source="./media/route-maps-how-to-nva/rm.png" alt-text="Screenshot that shows the Route-map." lightbox="route-maps-how-to-nva/rm.png":::
67
67
68
-
3. Apply the Route-Map on the VNet 1 connection. The Route-Map will be applied in the inbound direction.
68
+
3. Apply the Route-Map on the virtual network 1 connection. The Route-Map will be applied in the inbound direction.
69
69
70
70
:::image type="content" source="./media/route-maps-how-to-nva/apply.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="route-maps-how-to-nva/apply.png":::
Copy file name to clipboardExpand all lines: articles/virtual-wan/how-to-configure-route-maps-to-tag-routes.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ This article helps you use the Route-maps feature to tag routes using the Azure
16
16
17
17
## Prerequisites
18
18
19
-
Verify that you've met the following criteria before beginning your configuration:
19
+
Verify that you have met the following criteria before beginning your configuration:
20
20
21
21
* You have virtual WAN (VWAN) with a connection (S2S, P2S, or ExpressRoute) already configured.
22
22
@@ -25,51 +25,51 @@ Verify that you've met the following criteria before beginning your configuratio
25
25
* Be sure to view [About Route-maps](route-maps-about.md#considerations-and-limitations) for considerations and limitations before proceeding with configuration steps.
26
26
27
27
## Design
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 peered with the hub. Hub 2 also has 2 VNets and a VPN branch office.
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 shows how to the Enviroment." 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 shows how to the Environment." lightbox="./media/route-maps-how-to-summarize/environment.png":::
In this scenario, the goal is to tag route 10.5.0.192/26 form VNet 3 on Hub 2 with BGP community 3356:70
48
+
In this scenario, the goal is to tag route 10.5.0.192/26 form virtual network 3 on Hub 2 with BGP community 3356:70
49
49
50
50
:::image type="content" source="./media/route-maps-how-to-tag/tag.png" alt-text="Screenshot that shows the Scenario." lightbox="./media/route-maps-how-to-tag/tag.png":::
51
51
52
52
## Workflow
53
53
54
-
1. Use the Route-Map dashboard in hub 2 to verify the BGP community on the route 10.5.0.192/26 being advertised from the VNet connection.
54
+
1. Use the Route-Map dashboard in hub 2 to verify the BGP community on the route 10.5.0.192/26 being advertised from the virtual network connection.
55
55
56
56
:::image type="content" source="./media/route-maps-how-to-tag/db_before.png" alt-text="Screenshot that shows routes before Route-map." lightbox="./media/route-maps-how-to-tag/db_before.png":::
57
57
58
58
look at the Route-Map dashboard for the VPN Brach to verify the BGP community on the route for 10.5.0.192/26. The goal is to very what routes are being sent on prem.
59
59
60
60
:::image type="content" source="./media/route-maps-how-to-tag/db_before_2.png" alt-text="Screenshot that shows routes before Route-map." lightbox="./media/route-maps-how-to-tag/db_before_2.png":::
61
61
62
-
2. Create a Route-Map to tag the route. If this is your frist time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information.
62
+
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.
63
63
64
-
The Route-Map will have a match rule for route 10.5.0.192/26. The action **modify** will be selected. Route Modification will have an **add** for **community** 3356:70.
64
+
The Route-Map will have a match rule for route 10.5.0.192/26. The action **modify** will be selected. Route Modification has an **add** for **community** 3356:70.
65
65
66
66
:::image type="content" source="./media/route-maps-how-to-tag/rm.png" alt-text="Screenshot that shows the Route-map." lightbox="./media/route-maps-how-to-tag/rm.png":::
67
67
68
-
3. Apply the Route-Map on the VNet 3 connection. The Route-Map will be applied in the inbound direction.
68
+
3. Apply the Route-Map on the virtual network 3 connection. The Route-Map will be applied in the inbound direction.
69
69
70
70
:::image type="content" source="./media/route-maps-how-to-tag/rm.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="./media/route-maps-how-to-tag/apply.png":::
71
71
72
-
4. Using the Route-Map dashboard in Hub 2, Verify that route 10.5.0.192/26 has the BGP community of 3356:70 added on the VNet 3 connection.
72
+
4. Using the Route-Map dashboard in Hub 2, Verify that route 10.5.0.192/26 has the BGP community of 3356:70 added on the virtual network 3 connection.
73
73
74
74
:::image type="content" source="./media/route-maps-how-to-tag/db_after.png" alt-text="Screenshot that shows routes after Route-map being applied." lightbox="./media/route-maps-how-to-tag/db_after.png":::
0 commit comments