Table of Contents
Advertisement
Command History
Introduced in version 6.3.0.1 firmware.
Example
The following example shows the creation of an extended community list
that permits routes from route target 1:1 and site of origin 2:2 and denies
routes from route target 3:3 and 4:4.
(R1)(Config)# ip extcommunity-list 10 permit rt 1:1
(R1)(Config)# ip extcommunity-list 10 permit rt 2:2
(R1)(Config)# ip extcommunity-list 20 deny rt 3:3 rt 4:4
List 10 shows a logical OR condition which means the first match is
processed.
List 20 shows a logical AND condition which means all the community values
must match in order for list 20 to be processed.
The following example show how the extended communities list is used by
route-maps.
(R1)(config)# route-map SEND_OUT permit 10
(R1)(config-route-map)# match extcommunity 10
(R1)(config-route-map)# set extcommunity rt 10:10 additive
(R1)(config-route-map)# exit
The following example shows the usage of extended communities attribute in
BGP configuration mode and sending of the extended communities attribute
to external peer at 1.1.1.1.
(R1)(Config)# router bgp 1
(R1)(Config-router)# neighbor 1.1.1.1 remote-as 2
(R1)(Config-router)# neighbor 1.1.1.1 route-map SEND_OUT out
(R1)(Config-router)# address-family vpnv4 unicast
(R1)(Config-router-af)# neighbor 1.1.1.1 send-community extended
(R1)(Config-router-af)# neighbor 1.1.1.1 activate
match extcommunity
Use the match extcommunity command to match BGP extended community
list attributes. Use the no form of this command to remove the match
extcommunity from the configuration and BGP extended community list
attribute entry.
NOTE: This command is effective only if BGP is running on the router.
1256
Layer 3 Routing Commands
Advertisement
Table of Contents
