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-tag-routes.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
@@ -51,25 +51,25 @@ In this scenario, the goal is to tag route 10.5.0.192/26 form virtual network 3
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 virtual network 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-tag-routes/db-before.png" alt-text="Screenshot that shows routes before Route-map." lightbox="./media/route-maps-tag-routes/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 vary what routes are being sent on premises.
59
59
60
60
:::image type="content" source="./media/route-maps-tag-routes/db-before-two.png" alt-text="Screenshot that shows routes for VPN branch." lightbox="./media/route-maps-tag-routes/db-before-two.png":::
61
61
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.
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
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-tag-routes/rm.png" alt-text="Screenshot that shows the Route-map." lightbox="./media/route-maps-tag-routes/rm.png":::
67
67
68
-
3. Apply the Route-Map on the virtual network 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-tag-routes/apply.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="./media/route-maps-tag-routes/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 virtual network 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-tag-routes/db-after.png" alt-text="Screenshot that shows routes after Route-map being applied." lightbox="./media/route-maps-tag-routes/db-after.png":::
0 commit comments