community

Syntax

community ([ community-ids ] | no-advertise | no-export | no-export-subconfed | none);

Hierarchy Level

[edit routing-options (aggregate | generate | static) (defaults | route)],
[edit routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)],
[edit routing-instances routing-instance-name routing-options (aggregate | generate | static)
    (defaults | route)],
[edit routing-instances routing-instance-name routing-options rib routing-table-name
    (aggregate | generate | static) (defaults | route)],
[edit logical-routers logical-router-name routing-options (aggregate | generate | static)
    (defaults | route)],
[edit logical-routers logical-router-name routing-options rib routing-table-name
    (aggregate | generate | static) (defaults | route)],
[edit logical-routers logical-router-name routing-instances routing-instance-name routing-options
    (aggregate | generate | static) (defaults | route)],
[edit logical-routers logical-router-name routing-instances routing-instance-name routing-options
    rib routing-table-name (aggregate | generate | static) (defaults | route)]

Description

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 0 through 65535.

community-value—Identifier of the community member. It can be a number from 0 through 65535.

For more information about BGP community attributes, see the JUNOS Internet Software Configuration Guide: Policy Framework.

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.

The BGP extended communities attribute format 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.

For more information about the BGP extended communities attribute, see the JUNOS Internet Software Configuration Guide: Policy Framework.

Usage Guidelines

See Configure Static Routes, Configure Aggregate Routes, and Configure Generated Routes.

Required Privilege Level

routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.

See Also

aggregate, generate, static