Table 15: Clauses Supported In Bgp Match-And-Set Route Maps; Table 16: Commands That Create Match-Only Route Maps; Table 17: Clauses Not Supported In Bgp Route Maps - Juniper JUNOSE 11.2.X BGP AND MPLS Configuration Manual

match as-path
Copyright © 2010, Juniper Networks, Inc.
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

match as-path
match community
match distance
match extcommunity
match ip address
match ip next-hop
match level
match metric
match metric-type
match route-type
match tag
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 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 automatic-tag
set distance
Use to match an AS-path access list.
The implemented weight is based on the first matched AS path.
Chapter 1: Configuring BGP Routing
set as-path prepend
set comm-list delete
set community
set dampening
set extcommunity
set ip next-hop
set local-preference
set metric
set metric-type
set origin
set tag
set weight
aggregate support-map
set level
set route-type
71