Cisco Nexus 7000 Series - Configuring Community Lists

Send document comments to nexus7k-docfeedback@cisco.com.
16-9
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
Configuring Community Lists
You can use community lists to filter BGP routes based on the community attribute. The community
number consists of a 4-byte value in the aa:nn format. The first two 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 community list statement, all community values must
match to satisfy the community list filter. When you configure multiple values in separate community
list statements, the first list that matches a condition is processed.
Use community lists in a match statement to filter BGP routes based on the community attribute.
SUMMARY STEPS
1. config t
2. ip community-list standard list-name {deny | permit} [community-list ] [internet] [local-AS]
[no-advertise] [no-export]
or
ip community-list expanded list-name {deny | permit} expression
3. show ip community-list name
4. copy running-config startup-config
DETAILED STEPS
Command Purpose
Step 1
config t
Example:
switch# config t
switch(config)#
Enters configuration mode.
Step 2
ip community-list standard list-name
{deny | permit} [ community-list ]
[internet] [local-AS] [no-advertise]
[no-export]
Example:
switch(config)# ip community-list
standard BGPCommunity permit
no-advertise 65536:20
Creates a standard BGP community list. The list-name
can be any case-sensitive alphanumeric string up to 63
characters. The community-list can be one or more
communities in the aa:nn format.
ip community-list expanded list-name
{deny | permit} expression
Example:
switch(config)# ip community-list
expanded BGPComplex deny
50000:[0-9][0-9]_
Creates an expanded BGP community list using a
regular expression.