Skip to content

Community List

Community lists define named collections of BGP community values used for route filtering and matching in route maps. NX-OS supports standard community lists (matching exact community values) and regex-based community lists (matching community strings using regular expressions). Community lists are referenced in route map match clauses to implement community-based routing policies.

Diagram
NameTypeConstraintMandatoryDefault Value
community_listsList[community_lists]No

community_lists (nxos.devices.configuration)

Section titled “community_lists (nxos.devices.configuration)”
NameTypeConstraintMandatoryDefault Value
nameStringYes
modeChoicestandard, expandedNo
entriesList[entries]No

entries (nxos.devices.configuration.community_lists)

Section titled “entries (nxos.devices.configuration.community_lists)”
NameTypeConstraintMandatoryDefault Value
seqIntegermin: 1, max: 4294967294Yes
actionChoicepermit, denyNo
regexStringNo
communitiesListStringNo

Example 1: Standard community list matching specific community values

nxos:
devices:
- name: LEAF1
configuration:
community_lists:
- name: CL-STANDARD-TENANT
mode: standard
entries:
- seq: 10
action: permit
communities:
- "regular:as2-nn2:65000:100"
- "regular:as2-nn2:65000:200"
- seq: 20
action: deny

Example 2: Regex-based community list for flexible pattern matching

nxos:
devices:
- name: SPINE1
configuration:
community_lists:
- name: CL-REGEX-DATACENTER
mode: expanded
entries:
- seq: 10
action: permit
regex: "65000:.*"

Example 3: Multiple community lists for a multi-tenant EVPN fabric

nxos:
devices:
- name: BORDER-LEAF1
configuration:
community_lists:
- name: CL-TENANT-A
mode: standard
entries:
- seq: 10
action: permit
communities:
- "regular:as2-nn2:65000:1010"
- "regular:as2-nn2:65000:1020"
- name: CL-TENANT-B
mode: standard
entries:
- seq: 10
action: permit
communities:
- "regular:as2-nn2:65000:2010"
- "regular:as2-nn2:65000:2020"
- name: CL-NO-EXPORT
mode: expanded
entries:
- seq: 10
action: permit
regex: "no-export"