Reference Guide

Border Gateway Protocol IPv4 (BGPv4) | 407
Usage
Information
Like standard communities, extended communities can be used in route-map to match the
attribute.
Example
FTOS(config-route-map)#match extcommunity Freedombird
FTOS(config-route-map)#
Command
History
permit
c e s
Use this feature to add rules (permit) from the two types of extended communities, Route
Origin (rt) or Site-of-Origin (soo).
Syntax
permit {rt | soo} {as4 ASN4:NN | ASN:NNNN | IPADDR:NN}
To change the rules, use the
no permit {rt | soo} {as4 ASN4:NN | ASN:NNNN | IPADDR:NN}
command.
Parameters
Defaults
Not Configured
Command Modes
CONFIGURATION (conf-ext-community-list)
Related
Commands
Command
History
permit regex
c e s
This features enables you specify an extended communities to forward (permit) using a
regular expressions (regex).
Version 7.8.1.0 Introduced on S-Series
Version 7.7.1.0 Introduced on C-Series
Version 7.6.1.0 Introduced on E-Series
rt
Enter the keyword rt to designate a Route Origin community
soo
Enter the keyword soo to designate a Site-of-Origin community (also known
as Route Origin).
as4 ASN4:NN
Enter the keyword as4 followed by the 4-octet AS specific extended
community number in the format ASN4:NN (4-byte AS number:2-byte
community value).
ASN:NNNN
Enter the 2-octet AS specific extended community number in the format
ASN:NNNN (2-byte AS number:4-byte community value).
IPADDR:NN
Enter the IP address specific extended community in the format
IPADDR:NN (4-byte IPv4 Unicast Address:2-byte community value)
deny Configure to delete (deny) rules
show ip extcommunity-list Display the Extended Community list
Version 7.8.1.0 Introduced on S-Series
Version 7.7.1.0 Introduced on C-Series
Version 7.6.1.0 Introduced on E-Series