Cisco Nexus 7000 Series - Configuring Extended Community Lists

Send document comments to nexus7k-docfeedback@cisco.com.
16-10
Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 4.x
OL-20002-02
Chapter 16 Configuring Route Policy Manager
Configuring Route Policy Manager
The following example shows how to create a community list with two entries:
switch# config t
switch(config)# ip community-list standard BGPCommunity permit no-advertise 65536:20
switch(config)# ip community-list standard BGPCommunity permit local-AS no-export
switch(config)# copy running-config startup-config
Configuring Extended Community Lists
You can use extended community lists to filter BGP routes based on the community attribute. The
community number consists of a 6-byte value in the aa4:nn format. The first four bytes represent the
autonomous system number, and the last two bytes represent a user-defined network number.
When you configure multiple values in the same extended community list statement, all extended
community values must match to satisfy the extended community list filter. When you configure multiple
values in separate extended community list statements, the first list that matches a condition is processed.
Use extended community lists in a match statement to filter BGP routes based on the extended
community attribute.
SUMMARY STEPS
1. config t
2. ip extcommunity-list standard list-name {deny | permit} generic {transitive | nontransitive}
aa4:nn
or
ip extcommunity-list expanded list-name {deny | permit} generic {transitive | nontransitive}
3. show ip extcommunity-list name
4. copy running-config startup-config
Step 3
show ip community-list name
Example:
switch(config)# show ip community-list
BGPCommunity
(Optional) Displays information about community
lists.
Step 4
copy running-config startup-config
Example:
switch# copy running-config
startup-config
(Optional) Saves this configuration change.
Command Purpose