Users Guide

Usage Information
The community list used in the set comm-list delete command must be
configured so that each filter contains only one community. For example, the filter
deny 100:12 is acceptable, but the filter deny 120:13 140:33 results in an error.
If the set comm-list delete command and the set community command are
configured in the same route map sequence, the deletion command (
set comm-list
delete
) is processed before the insertion command (set community).
Related
Commands
• match community — redistribute routes that match the COMMUNITY attribute.
• set community — specify a COMMUNITY attribute.
set community
Allows you to assign a BGP COMMUNITY attribute.
Syntax
set community {community-number | local-as | no-advertise | no-
export | none} [additive]
To delete a BGP COMMUNITY attribute assignment, use the no set community
{community-number | local-as | no-advertise | no-export | none}
command.
Parameters
community-
number
Enter the community number in AA:NN format where AA is the
AS number (2 bytes) and NN is a value specific to that
autonomous system.
local-AS Enter the keywords local-AS to drop all routes with the
COMMUNITY attribute of NO_EXPORT_SUBCONFED.
All routes with the NO_EXPORT_SUBCONFED (0xFFFFFF03)
community attribute must not be advertised to external BGP
peers.
no-advertise Enter the keywords no-advertise to drop all routes containing
the well-known community attribute of NO_ADVERTISE.
All routes with the NO_ADVERTISE (0xFFFFFF02) community
attribute must not be advertised to other BGP peers.
no-export Enter the keywords no-export to drop all routes containing the
well-known community attribute of NO_EXPORT.
All routes with the NO_EXPORT (0xFFFFFF01) community
attribute must not be advertised outside a BGP confederation
boundary.
none Enter the keyword none to remove the community attribute
from routes meeting the route map criteria.
Access Control Lists (ACL) 323