Users Guide

Version Description
9.8(1.0) Introduced on the Z9100–ON.
9.8(0.0P5) Introduced on the S4048-ON.
9.8(0.0P2) Introduced on the S3048-ON.
9.7(0.0) Introduced on the S6000–ON.
9.2(1.0) Introduced on the Z9500.
9.0.2.0 Introduced on the S6000.
8.3.19.0 Introduced on the S4820T.
8.3.11.1 Introduced on the Z9000.
8.3.7.0 Introduced on the S4810.
8.1.1.0 Introduced on the E-Series.
7.8.1.0 Increased the name string to accept up to 140 characters. Prior
to 7.8.1.0, names are up to 16 characters long.
7.6.1.0 Introduced on the S-Series.
7.5.1.0 Introduced on the C-Series.
pre-6.1.1.0 Introduced on the E-Series.
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.
Access Control Lists (ACL) 288