Command:

match extcommunity


Mode:

Router(config-route-map)#


Syntax:

match extcommunity [standard-list-number | expanded-list-number]
no match extcommunity [standard-list-number | extended-list-number]

 

Syntax Description:

standard-list-number A standard extended community list number from 1 to 99 that identifies one or more permit or deny groups of extended community attributes.
expanded-list-number An expanded extended community list number from 100 to 500 that identifies one or more permit or deny groups of extended community attributes.

 

Command Description:

To match Border Gateway Protocol (BGP) extended community list attributes, use the match extcommunity command in route-map configuration mode. To remove the match extcommunity command from the configuration file and remove the BGP extended community list attribute entry, use the no form of this command.

Extended community attributes are used to configure, filter, and identify routes for virtual routing and forwarding instances (VRFs) and Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs).

The match extcommunity command is used to configure match clauses that use extended community attributes in route maps. The range of numbers that can be configured with the match extcommunity command is from 1 to 99. All of the standard rules of match and set clauses apply to the configuration of extended community attributes.


Example:

The following example shows that the routes that match extended community list 1 will have the weight set to 100. Any route that has extended community 1 will have the weight set to 100.

Router(config)# ip extcommunity-list 1 rt 100:2
Router(config)# route-map MAP_NAME permit 10
Router(config-route-map)# match extcommunity 1 
Router(config-route-map)# set weight 100


Misconceptions:

None


Related Commands:

route-map
set extcommunity
set weight
show ip bgp filter-list

� Cisco Systems, Inc. 2001, 2002, 2003
World Wide Education

Converted from CHM to HTML with chm2web Pro 2.85 (unicode)