The following commands configure router Boston to apply route map 5 to routes going
out to 10.5.5.4. If the destination IP address of such a route matches instance 10 of the
route map, router Boston sets the community attribute of the route to no-export.
host3(config)#router bgp 122
host3(config-router)#network 192.168.144.0 mask 255.255.240.0
host3(config-router)#neighbor 10.5.5.4 remote-as 425
host3(config-router)#neighbor 10.5.5.4 send-community
host3(config-router)#neighbor 10.5.5.4 route-map 5 out
host3(config-router)#exit
host3(config)#route-map 5 permit 10
host3(config-route-map)#match ip address access5
host3(config-route-map)#set community no-export
host3(config-route-map)#exit
host3(config)#access-list access5 permit 10.16.22.112
Suppose router Boston forwards a route destined for 10.16.22.112 through router LA. Route
map 5 matches and sets the community attribute to no-export. As a consequence router
LA does not export the route to router NY; the route does not reach its destination.
ip bgp-community new-format
Use to specify that communities must be displayed in AA:NN format, where AA is a
number that identifies the autonomous system and NN is a number that identifies the
community within the autonomous system.
•
• Use the no version to restore the default display.
• See ip bgp-community new-format.
neighbor send-community
• Use to specify that a community attribute must be sent to a BGP neighbor.
• You can specify that only standard communities, only extended communities, or both
be sent.
• When you create a neighbor in a VPNv4 address family, that neighbor automatically
gets a neighbor send-community extended command; this command subsequently
appears in a show configuration display because it is not the default.
• 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. You cannot
override this inheritance for a peer group member.
• Example
host1(config-router)#neighbor send-community westcoast extended
• 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
Copyright © 2010, Juniper Networks, Inc.92
JunosE 11.2.x BGP and MPLS Configuration Guide
To Next Page
Loading...
Need help?
General
