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


Specify Community Information

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

[edit routing-options generate (defaults | route)] 
community [ community-ids ]; 

For a list of hierarchy levels at which you can configure 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 1 through 65534. community-value is the community identifier and can be a number in the range 0 through 65535.

You also can specify community-ids for communities as one of the following well-known community names, which are defined in RFC 1997:

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.

The format for extended community identifiers is:

type:administrator:assigned-number

type is the type of extended community and can be either a target, origin, or domain-id community. The target community identifies the destination to which the route is going. The origin community identifies where the route originated. The domain-id community identifies the OSPF domain where the route originated.

administrator is the administrator. It is either an autonomous system (AS) number or an IPv4 address prefix, depending on the type of extended community.

assigned-number identifies the local provider.


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