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

Specifying Community Information

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




aggregate (defaults | route) {

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-value is the community identifier and can be a number in the range from 0 through 65,535.

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-export—Routes containing this community name are not advertised outside a BGP confederation boundary.
no-advertise—Routes containing this community name are not advertised to other BGP peers.
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 an aggregate route using the none option. Include none when configuring an individual route in the route portion of the aggregate 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 information, see the “Configuring the Extended Communities Attribute” section in the JUNOS Policy Framework Configuration Guide.

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