.
'Set' is a valid operator for the 'med' attribute at the bgp import attach point.Note
Export
The export attach point provides control over the export of routes from a particular VRF to a global VPN
IPv4 table.
For Layer 3 VPN networks, export route targets are added to the VPN IPv4 routes when VRF IPv4 routes are
converted into VPN IPv4 routes and advertised through the MP-iBGP to other PE routers (or flow from one
VRF to another within a PE router).
A set of export route targets is configured with the VRF without RPL configuration; however, to set route
targets conditionally, you can configure a VRF export policy.
The following example shows some match and set operations supported for the export route policy. If a route
matches 172.16.1.0/24 then the route target extended community is set to 10:101, and the weight is set to 211.
If the route does not match 172.16.1.0/24 but the origin of the route is egp, then the local preference is set to
212 and the route target extended community is set to 10:101. If the route does not match those specified
criteria, then the route target extended community 10:111222 is added to the route. In addition, RT 10:111222
is added to the route that matches any of the previous conditions as well.
route-policy bgpvrf_export
if destination in (172.16.1.0/24) then
set extcommunity rt (10:101)
set weight 211
elseif origin is egp then
set local-preference 212
set extcommunity rt (10:101)
endif
set extcommunity rt (10:111222) additive
end-policy
vrf vrf-export
address-family ipv4 unicast
export route-policy bgpvrf-export
.
.
.
'Set' is a valid operator for the 'med' attribute at the bgp export attach point.Note
Allocate-Label
The allocate-label attach point provides increased control based on various attribute match operations. This
attach point is typically used in inter-AS option C to decide whether the label should be allocated or not when
sending updates to the neighbor for the IPv4 labeled unicast address family. The attribute setting actions
supported are for pass and drop.
The following example shows how to configure a route policy that passes the prefix 0.0.0.0 with prefix length
0. Label allocation happens only if prefix 0.0.0.0 exists.
route-policy label_policy
Cisco ASR 9000 Series Aggregation Services Router Routing Configuration Guide, Release 5.1.x
OL-30423-03 497
Implementing Routing Policy
Attach Points
To Next Page
Loading...
Need help?
General
