■
Use to match a route for the specified route type.
■
Example
host1(config)#
route-map nyc1 permit 10
host1(config-route-map)#
match route-type level-1
■
Use the
no
version to delete the match clause from a route map or a specified
value from the match clause.
■
See match route-type.
match tag
■
Use to match the tag value of the destination routing protocol.
■
Example
host1(config)#
route-map 1
host1(config-route-map)#
match tag 25
■
Use the
no
version to delete the match clause from a route map or a specified
value from the match clause.
■
See match tag.
neighbor route-map
■
Use to apply a route map to incoming or outgoing routes.
■
If you specify an outbound route map, BGP advertises only routes that match at
least one section of the route map. For routes that do not match, no further
processing takes place with respect to this peer, and those routes are not
advertised to this peer. The nonmatching route is still in the BGP RIB and can
be sent to other peers depending on the outbound policy applied to those peers.
■
If you specify an inbound route map, BGP processes only the received routes
that match at least one section of the route map. The nonmatching routes are
rejected from entering the local BGP RIB and no further processing takes place.
■
A clause with multiple values matches a route having any of the values; that is,
the multiple values are logical ORed.
■
If you specify a BGP peer group by using the
peerGroupName
argument, all the
members of the peer group inherit the characteristic configured with this
command unless it is overridden for a specific peer. However, you cannot
configure a member of a peer group to override the inherited peer group
characteristic for outbound policy.
■
New policy values are applied to all routes that are sent (outbound policy) or
received (inbound policy) after you issue the command.
To apply the new policy to routes that are already present in the BGP routing
table, you must use the
clear ip bgp
command to perform a soft clear or hard
clear of the current BGP session.
Behavior is different for outbound policies configured for peer groups for which
you have enabled Adj-RIBs-Out. If you change the outbound policy for such a
peer group and want to fill the Adj-RIBs-Out table for that peer group with the
Configuring BGP Routing Policy
■
75
Chapter 1: Configuring BGP Routing
Summary of Contents for JUNOSE
Page 6: ...vi...
Page 8: ...viii JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 24: ...xxiv Table of Contents JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 37: ...Part 1 Border Gateway Protocol Configuring BGP Routing on page 3 Border Gateway Protocol 1...
Page 38: ...2 Border Gateway Protocol JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 234: ...198 Monitoring BGP JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 236: ...200 Multiprotocol Layer Switching JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 298: ...262 Point to Multipoint LSPs Configuration JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 536: ...500 Monitoring BGP MPLS VPNs JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 538: ...502 Layer 2 Services Over MPLS JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 604: ...568 Virtual Private LAN Service JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 618: ...582 VPLS References JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 674: ...638 Virtual Private Wire Service JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 718: ...682 Monitoring MPLS Forwarding Table for VPWS JUNOSe 11 0 x BGP and MPLS Configuration Guide...
Page 719: ...Part 6 Index Index on page 685 Index 683...
Page 720: ...684 Index JUNOSe 11 0 x BGP and MPLS Configuration Guide...