Specify Community Information

By default, no Border Gateway Protocol (BGP) community information is associated with static routes. To associate community information with IPv4 routes, include the community statement:

[edit routing-options static (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.

To associate community information with IPv6 routes, include the community statement:

[edit routing-options rib inet6.0 static (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 autonomous system (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 hrough 65535.

You also can specify community-ids 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 also explicitly exclude BGP community information with a static route using the none option. Include none when configuring an individual route in the route portion of the static 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.