Table 15: Clauses Supported in BGP Match-and-Set Route Maps (continued)
set metricmatch metric
set metric-typematch metric-type
set originmatch route-type
set tagmatch tag
set weight
The match-only route maps consist of the route maps configured with any of the
commands listed in Table 16 on page 72. You can use any of the match clauses listed
in Table 15 on page 71 in these route maps. Set clauses have no effect in these route
maps.
Table 16: Commands That Create Match-Only Route Maps
aggregate support-mapaggregate advertise-map
BGP does not support the clauses listed in Table 17 on page 72. However, see
“Applying Table Maps” on page 81 for exceptions for route maps applied with the
table-map command.
Table 17: Clauses Not Supported in BGP Route Maps
set levelset automatic-tag
set route-typeset distance
match as-path
■ Use to match an AS-path access list.
■ The implemented weight is based on the first matched AS path.
■ Example
host1(config)#route-map nyc1 permit 10
host1(config-route-map)#match as-path pathlist5
■ Use the no version to delete the match clause from a route map or a specified
value from the match clause.
■ See match as-path.
match community
72 ■ Configuring BGP Routing Policy
JUNOSe 11.1.x BGP and MPLS Configuration Guide
To Next Page
Loading...
Need help?
General
