Skip to content

Commit a11bbd9

Browse files
cfields475cfields475
committed
1 parent c797372 commit a11bbd9

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

42 files changed

+434
-0
lines changed

‎articles/virtual-wan/How to configure Route-maps to drop inbound routes from Branch sites.md

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
---
2+
title: 'How to configure Route-maps to drop inbound routes from branch sites'
3+
titleSuffix: Azure Virtual WAN
4+
description: Learn how to configure Route-maps to drop inbound routes from branch sites.
5+
author: cfields475
6+
ms.service: azure-virtual-wan
7+
ms.topic: how-to
8+
ms.date: 03/04/2025
9+
ms.author: cfields
10+
ms.custom: references_region
11+
12+
---
13+
# How to configure Route-maps to drop routes from branch sites
14+
15+
This article helps you use the Route-maps feature to drop routes from branch sites using the Azure portal. For more information about Virtual WAN Route-maps, see [About Route-maps](route-maps-about.md).
16+
17+
## Prerequisites
18+
19+
Verify that you've met the following criteria before beginning your configuration:
20+
21+
* You have virtual WAN (VWAN) with a connection (S2S, P2S, or ExpressRoute) already configured.
22+
23+
* For steps to create a VWAN with a S2S connection, see [Tutorial - Create a S2S connection with Virtual WAN](virtual-wan-site-to-site-portal.md).
24+
* For steps to create a virtual WAN with a P2S User VPN connection, see [Tutorial - Create a User VPN P2S connection with Virtual WAN](virtual-wan-point-to-site-portal.md).
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+
27+
## Design
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.
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":::
32+
33+
Here is the addressing for this environment:
34+
35+
| Resource |Address Space |
36+
| --- |---|
37+
|Hub 1 |192.168.1.0/24 |
38+
|Hub 2 |192.168.2.0/24 |
39+
|VNet 1 |10.1.0.0/24 |
40+
|VNet 2 |10.2.0.0/24 |
41+
|VNet 3 |10.3.0.0/24 |
42+
|VNet 4 |10.4.0.0/24 |
43+
|VPN Branch 1 |10.122.1.0/24, 10.122.2.0/24, 10.122.3.0/24, 10.100.0.0/16|
44+
|VPN Branch 2 |10.200.0.0/16 |
45+
|NVA 1 | 10.150.1.0/24, 10.150.2.0/24 , 10.150.3.0/24 , 10.150.4.0/24 |
46+
47+
## Scenario : Drop inbound routes from Branch sites
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.
50+
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+
53+
## Workflow
54+
55+
1. Use the Route-Map dashboard in hub 1 to verify what routes are being advertised from the VPN branch.
56+
57+
:::image type="content" source="./media/route-maps-how-to-Drop/DB_Before.png" alt-text="Screenshot that shows routes before." lightbox="./media/route-maps-how-to-Drop/DB_Before.png":::
58+
59+
Verify the routes are showing up in the effective route table for hub 1.
60+
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+
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.
64+
65+
The Route-Map will have a match rule for route 10.122.2.0/16. The action **Drop** will be selected.
66+
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":::
68+
69+
3. Apply the Route-Map on the VPN branch 1 site connection. The Route-Map will be applied in the inbound direction.
70+
71+
:::image type="content" source="./media/route-maps-how-to-Drop/Apply.png" alt-text="Screenshot that shows applying the Route-Map." lightbox="./media/route-maps-how-to-Drop/Apply.png":::
72+
73+
4. Using the Route-Map dashboard in Hub 1, Verify that routes 10.122.1.0/24,10.122.2.0/24, 10.122.3.0/24 are being dropped.
74+
75+
:::image type="content" source="./media/route-maps-how-to-Drop/DB_After.png" alt-text="Screenshot that shows routes after applying Route-Map." lightbox="./media/route-maps-how-to-Drop/DB_After.png":::
76+
77+
Verify the routes are no longer in the effective route table.
78+
79+
:::image type="content" source="./media/route-maps-how-to-Drop/ER_After.png" alt-text="Screenshot that shows routes after applying Route-Map." lightbox="./media/route-maps-how-to-Drop/ER_After.png":::
80+
81+
## Next steps
82+
83+
* Use the [Route-maps dashboard](route-maps-dashboard.md) to monitor routes, AS Path, and BGP communities.
84+
* To learn more about Route-maps, see [About Route-maps](route-maps-about.md).

‎articles/virtual-wan/How to configure Route-maps to prepend routes.md

Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
---
2+
title: 'How to configure Route-maps to prepend routes'
3+
titleSuffix: Azure Virtual WAN
4+
description: Learn how to configure Route-maps to prepend routes.
5+
author: cfields475
6+
ms.service: azure-virtual-wan
7+
ms.topic: how-to
8+
ms.date: 03/04/2025
9+
ms.author: cfields
10+
ms.custom: references_region
11+
12+
---
13+
# How to configure Route-maps to prepend routes
14+
15+
This article helps you use the Route-maps feature to prepend routes using the Azure portal. For more information about Virtual WAN Route-maps, see [About Route-maps](route-maps-about.md).
16+
17+
## Prerequisites
18+
19+
Verify that you've met the following criteria before beginning your configuration:
20+
21+
* You have virtual WAN (VWAN) with a connection (S2S, P2S, or ExpressRoute) already configured.
22+
23+
* For steps to create a VWAN with a S2S connection, see [Tutorial - Create a S2S connection with Virtual WAN](virtual-wan-site-to-site-portal.md).
24+
* For steps to create a virtual WAN with a P2S User VPN connection, see [Tutorial - Create a User VPN P2S connection with Virtual WAN](virtual-wan-point-to-site-portal.md).
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+
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.
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":::
31+
32+
Here is the addressing for this environment:
33+
34+
| Resource |Address Space |
35+
| --- |---|
36+
|Hub 1 |192.168.1.0/24 |
37+
|Hub 2 |192.168.2.0/24 |
38+
|VNet 1 |10.1.0.0/24 |
39+
|VNet 2 |10.2.0.0/24 |
40+
|VNet 3 |10.3.0.0/24 |
41+
|VNet 4 |10.4.0.0/24 |
42+
|VPN Branch 1 |10.122.1.0/24, 10.122.2.0/24, 10.122.3.0/24, 10.100.0.0/16|
43+
|VPN Branch 2 |10.200.0.0/16 |
44+
|NVA 1 | 10.150.1.0/24, 10.150.2.0/24 , 10.150.3.0/24 , 10.150.4.0/24 |
45+
46+
## Scenario : Using ASNs to prepend routes
47+
48+
In this scenario, the goal is to prepend route 10.5.0.192/26 from VNet 3 on Hub 2 with ASN 65533.
49+
> [!Important]
50+
> [!INCLUDE [Preview text](../../includes/virtual-wan-route-maps-ASN.md)]
51+
52+
:::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+
54+
## Workflow
55+
56+
1. Use the Route-Map dashboard in hub 2 to verify the ASNs on routes are being advertised from the VNet connection.
57+
58+
:::image type="content" source="./media/route-maps-how-to-prepend/DB_Before_1.png" alt-text="Screenshot that shows the routes before Route-Map." lightbox="./media/route-maps-how-to-prepend/DB_Before_1.png":::
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.
61+
62+
:::image type="content" source="./media/route-maps-how-to-prepend/DB_Before_2.png" alt-text="Screenshot that shows the routes before Route-Map." lightbox="./media/route-maps-how-to-prepend/DB_Before_2.png":::
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.
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.
67+
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+
70+
3. Apply the Route-Map on the VNet 3 connection. The Route-Map will be applied in the inbound direction.
71+
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":::
73+
74+
4. Using the Route-Map dashboard in Hub 2, Verify that route 10.5.0.192/26 has an ASN of 65533 added.
75+
76+
:::image type="content" source="./media/route-maps-how-to-prepend/DB_After_1.png" alt-text="Screenshot of routes after Route-map being applied." lightbox="./media/route-maps-how-to-prepend/DB_After_1.png":::
77+
78+
look at the Route-Map dashboard for VPN branch 2 connection to verify route 10.5.0.192/26 has the ASNs 65533 advertised to VPN branch 2.
79+
80+
:::image type="content" source="./media/route-maps-how-to-prepend/DB_After_2.png" alt-text="Screenshot of routes after Route-map being applied." lightbox="./media/route-maps-how-to-prepend/DB_After_2.png":::
81+
82+
## Next steps
83+
84+
* Use the [Route-maps dashboard](route-maps-dashboard.md) to monitor routes, AS Path, and BGP communities.
85+
* To learn more about Route-maps, see [About Route-maps](route-maps-about.md).

‎articles/virtual-wan/How to configure Route-maps to summarize routes from an NVA in a spoke VNet .md

Lines changed: 81 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,81 @@
1+
---
2+
title: 'How to configure Route-maps summarize routes from an NVA in a spoke VNet'
3+
titleSuffix: Azure Virtual WAN
4+
description: Learn how to configure Route-maps to summarize routes from an NVA
5+
author: cfields475
6+
ms.service: azure-virtual-wan
7+
ms.topic: how-to
8+
ms.date: 03/04/2025
9+
ms.author: cfields
10+
ms.custom: references_region
11+
12+
---
13+
# How to configure Route-maps to summarize routes from an NVA in a spoke VNet
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).
16+
17+
## Prerequisites
18+
19+
Verify that you've met the following criteria before beginning your configuration:
20+
21+
* You have virtual WAN (VWAN) with a connection (S2S, P2S, or ExpressRoute) already configured.
22+
23+
* For steps to create a VWAN with a S2S connection, see [Tutorial - Create a S2S connection with Virtual WAN](virtual-wan-site-to-site-portal.md).
24+
* For steps to create a virtual WAN with a P2S User VPN connection, see [Tutorial - Create a User VPN P2S connection with Virtual WAN](virtual-wan-point-to-site-portal.md).
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+
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.
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":::
31+
32+
Here is the addressing for this environment:
33+
34+
| Resource |Address Space |
35+
| --- |---|
36+
|Hub 1 |192.168.1.0/24 |
37+
|Hub 2 |192.168.2.0/24 |
38+
|VNet 1 |10.1.0.0/24 |
39+
|VNet 2 |10.2.0.0/24 |
40+
|VNet 3 |10.3.0.0/24 |
41+
|VNet 4 |10.4.0.0/24 |
42+
|VPN Branch 1 |10.122.1.0/24, 10.122.2.0/24, 10.122.3.0/24, 10.100.0.0/16|
43+
|VPN Branch 2 |10.200.0.0/16 |
44+
|NVA 1 | 10.150.1.0/24, 10.150.2.0/24 , 10.150.3.0/24 , 10.150.4.0/24 |
45+
46+
## Scenario : Summarize routes from an NVA in a spoke VNet
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
49+
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+
52+
## Workflow
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.
55+
56+
:::image type="content" source="./media/route-maps-how-to-NVA/DB_Before_1.png" alt-text="Screenshot that shows the routes before Route-maps." lightbox="route-maps-how-to-NVA/DB_Before_1.png":::
57+
58+
use the Route-Map dashboard to verify the routes being sent to VPN branch 1.
59+
:::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":::
60+
61+
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+
63+
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+
:::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":::
65+
66+
3. Apply the Route-Map on the VNet 1 connection. The Route-Map will be applied in the inbound direction.
67+
68+
:::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":::
69+
70+
4. Using the Route-Map dashboard in Hub 1, Verify that route 10.150.0.0/16 is being summarized.
71+
72+
:::image type="content" source="./media/route-maps-how-to-NVA/DB_After_1.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="route-maps-how-to-NVA/DB_After_1.png":::
73+
74+
Using the Route-Map dashboard verify route 10.150.0.0/16 has been advertised to VPN branch 1
75+
76+
:::image type="content" source="./media/route-maps-how-to-NVA/DB_After_2.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="route-maps-how-to-NVA/DB_After_2.png":::
77+
78+
## Next steps
79+
80+
* Use the [Route-maps dashboard](route-maps-dashboard.md) to monitor routes, AS Path, and BGP communities.
81+
* To learn more about Route-maps, see [About Route-maps](route-maps-about.md).

‎articles/virtual-wan/How to configure Route-maps to tag routes.md

Lines changed: 82 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,82 @@
1+
---
2+
title: 'How to configure Route-maps to tag routes'
3+
titleSuffix: Azure Virtual WAN
4+
description: Learn how to configure Route-maps to tag routes.
5+
author: cfields475
6+
ms.service: azure-virtual-wan
7+
ms.topic: how-to
8+
ms.date: 03/04/2025
9+
ms.author: cfields
10+
ms.custom: references_region
11+
12+
---
13+
# How to configure Route-maps to tag routes
14+
15+
This article helps you use the Route-maps feature to tag routes using the Azure portal. For more information about Virtual WAN Route-maps, see [About Route-maps](route-maps-about.md).
16+
17+
## Prerequisites
18+
19+
Verify that you've met the following criteria before beginning your configuration:
20+
21+
* You have virtual WAN (VWAN) with a connection (S2S, P2S, or ExpressRoute) already configured.
22+
23+
* For steps to create a VWAN with a S2S connection, see [Tutorial - Create a S2S connection with Virtual WAN](virtual-wan-site-to-site-portal.md).
24+
* For steps to create a virtual WAN with a P2S User VPN connection, see [Tutorial - Create a User VPN P2S connection with Virtual WAN](virtual-wan-point-to-site-portal.md).
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+
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.
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":::
31+
32+
Here is the addressing for this environment:
33+
34+
| Resource |Address Space |
35+
| --- |---|
36+
|Hub 1 |192.168.1.0/24 |
37+
|Hub 2 |192.168.2.0/24 |
38+
|VNet 1 |10.1.0.0/24 |
39+
|VNet 2 |10.2.0.0/24 |
40+
|VNet 3 |10.3.0.0/24 |
41+
|VNet 4 |10.4.0.0/24 |
42+
|VPN Branch 1 |10.122.1.0/24, 10.122.2.0/24, 10.122.3.0/24, 10.100.0.0/16|
43+
|VPN Branch 2 |10.200.0.0/16 |
44+
|NVA 1 | 10.150.1.0/24, 10.150.2.0/24 , 10.150.3.0/24 , 10.150.4.0/24 |
45+
46+
## Scenario : Using BGP communities to Tag routes
47+
48+
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
49+
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+
52+
## Workflow
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.
55+
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+
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+
:::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":::
60+
61+
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+
63+
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+
65+
:::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":::
66+
67+
3. Apply the Route-Map on the VNet 3 connection. The Route-Map will be applied in the inbound direction.
68+
69+
:::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":::
70+
71+
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+
73+
:::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":::
74+
75+
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.
76+
77+
:::image type="content" source="./media/route-maps-how-to-Tag/RM_After_2.png" alt-text="Screenshot that shows routes after Route-map being applied." lightbox="./media/route-maps-how-to-Tag/RM_After_2.png":::
78+
79+
## Next steps
80+
81+
* Use the [Route-maps dashboard](route-maps-dashboard.md) to monitor routes, AS Path, and BGP communities.
82+
* To learn more about Route-maps, see [About Route-maps](route-maps-about.md).

0 commit comments

Comments
 (0)