To create or configure a BGP community list, use the ip community-list command in Global Configuration mode. A community list statement with no community values is considered a match for all routes, regardless of their community membership. So the statement ip community-list bullseye permit is a permit all statement.
A community number may be entered in either format, as a 32-bit integer or a pair of 16-bit integers separated by a colon, regardless of whether the ip bgp-community new-format command is active. Up to 16 communities, including the well-known communities, can be listed in a single command. Up to 32 statements may be configured with a given community list name. Up to 128 unique community list names may be configured.
| Default | No community lists are configured by default. |
| Format | ip community-list standard list-name {permit | deny} [community-number] [no-advertise] [no-export] |
| Mode | Global Config |
| Parameter | Description |
|---|---|
| standard list-name | Identifies a named standard community list. The name may contain up to 32 characters. |
| permit | Indicates that matching routes are permitted. |
| deny | Indicates that matching routes are denied. |
| community-number | From zero to 16 community numbers formatted as a 32-bit integers or in AA:NN format, where AA is a 2-byte autonomous system number and NN is a 16 bit integer. The range is 1 to 4,294,967,295 (any 32-bit integer other than 0). Communities are separated by spaces. |
| no-advertise | The well-known standard community, NO_ADVERTISE (0xFFFFFF02). |
| no-export | The well-known standard community, NO_EXPORT, (0xFFFFFF01). |
