Associate BGP community information with a static,
aggregate, or generated route.
Options
community-ids—One
or more community identifiers. The community-ids format varies according to the type of attribute that you use.
The BGP community attribute format is as-number:community-value:
as-number—AS number
of the community member. It can be a value from 1 through 65,535.
community-value—Identifier
of the community member. It can be a number from 0 through 65,535.
For more information about BGP community attributes,
see the “Configuring the Extended Communities Attribute”
section in the JUNOS Policy Framework Configuration Guide.
For specifying the BGP community attribute only, you also can
specify community-ids as one of the
following well-known community names defined in RFC 1997:
no-advertise—Routes containing this community
name are not advertised to other BGP peers.
no-export—Routes containing this community
name are not advertised outside a BGP confederation boundary.
no-export-subconfed—Routes containing this
community name are not advertised to external BGP peers, including
peers in other members’ ASs inside a BGP confederation.
none—Explicitly exclude BGP community information
with a static route. Include this option when configuring an individual
route in the route portion to override a community option specified in the defaults portion.
Note:
Extended community attributes are not supported at the [edit routing-options] hierarchy level. You must configure extended
communities at the [edit policy-options] hierarchy level.
For information about configuring extended communities, see the JUNOS Policy Framework Configuration Guide.
