Reference Guide

Border Gateway Protocol | 293
Parameters
Defaults
Not configured
Command Modes
CONFIGURATION (conf-ext-community-list)
Usage
Information
Duplicate commands are silently accepted.
Example
Figure 9-31. Command Example: permit regexp
FTOS(conf-ext-community-list)#permit regexp 123
FTOS(conf-ext-community-list)#
Related
Commands
Command
History
set extcommunity rt
s z
Use this feature to set Route Origin community attributes in Route Map.
Syntax
set extcommunity rt {as4 ASN4:NN [non-trans] | ASN:NNNN [non-trans] | IPADDR:NN
[non-trans]} [additive]
To delete the Route Origin community, use the no set extcommunity command.
Parameters
Defaults
No default values or behavior
Command Modes
ROUTE MAP (config-route-map)
Usage
Information
If the set community rt and soo are in the same route-map entry, we can define the behavior as:
• If rt option comes before soo, with or without additive option, then soo overrides the
communities set by rt
• If rt options comes after soo, without the additive option, then rt overrides the communities set by
soo
regex
Enter a regular expression.
deny regex Deny a community using a regular expression
Version 9.0.2.0 Introduced on the S6000.
Version 9.0.0.0 Introduced on Z9000
Version 7.8.1.0 Introduced support on S-Series
S6000
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)
additive (OPTIONAL) Enter the keyword additive to add to the existing extended
community.
non-trans (OPTIONAL) Enter the keyword non-trans to indicate a non-transitive BGP
extended community.