BGP supports the clauses listed in Table 15 on page 71 for match-and-set route maps.
Table 15: Clauses Supported in BGP Match-and-Set Route Maps
set as-path prependmatch as-path
set comm-list deletematch community
set communitymatch distance
set dampeningmatch extcommunity
set extcommunitymatch ip address
set ip next-hopmatch ip next-hop
set local-preferencematch level
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 71. 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 71. However, see “Applying
Table Maps” on page 80 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.
71Copyright © 2010, Juniper Networks, Inc.
Chapter 1: Configuring BGP Routing
To Next Page
Loading...
Need help?
General
