[Contents] [Prev] [Next] [Index] [Report an Error]

Specifying Community Information

By default, no BGP community information is associated with generated routes. To associate community information with the routes, include the community option:




community [ community-ids ];

For a list of hierarchy levels at which you can include this statement, see the statement summary section for this statement.

community-ids is one or more community identifiers for either communities or extended communities.

The format for community identifiers is:




as-number:community-value

as-number is the AS number and can be a value in the range from 1 through 65,534.

You also can specify community-ids for communities as one of the following well-known community names, which are 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.

You can explicitly exclude BGP community information with a generated route using the none option. Include none when configuring an individual route in the route portion of the generate statement to override a community option specified in the defaults portion of the statement.

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 “Configuring the Extended Communities Attribute” section in the JUNOS Policy Framework Configuration Guide.

[Contents] [Prev] [Next] [Index] [Report an Error]