community (Routing Options)
Syntax
community ([ community-ids ] | no-advertise | no-export | no-export-subconfed | none | llgr-stale | no-llgr);
Hierarchy Level
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-options (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name routing-options (aggregate | generate | static) (defaults | route)], [edit logical-systems logical-system-name 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 routing-options (aggregate | generate | static) (defaults | route)], [edit routing-options rib routing-table-name (aggregate | generate | static) (defaults | route)]
Description
Associate BGP community information with a static, aggregate, or generated route.
BGP large community is available only for static routes.
Default
No BGP community information is associated with static routes.
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 1 through 65,535. The AS number can be a decimal or hexadecimal value.
community-value—Identifier of the community member. It can be a number from 0 through 65,535.
For more information about BGP community attributes, see the “Configuring the Extended Communities Attribute” section in the Routing Policies, Firewall Filters, and Traffic Policers User Guide.
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 are advertised to IBGP peers with the same AS number, but not to members of other confederations.
llgr-stale—Adds a community to a long-lived stale route when it is readvertised.no-llgr—Marks routes which a BGP speaker does not want to be retained by LLGR. The Notification message feature does not have any associated configuration parameters.
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 Routing Policies, Firewall Filters, and Traffic Policers User Guide.
As defined in RFC 8092, BGP large community uses 12-byte encoding
and the format for BGP large community-ids is:
large: global-administrator:assigned-number:assigned-number
large indicates BGP large community.
global-administrator is the administrator. It is
a 4-byte AS number.
assigned-number is a 4-byte value used to identify
the local provider. BGP large community uses two 4-byte assigned number
to identify the local provider.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced before Junos OS Release 7.4.
llgr-stale and no-llgr options added in Junos OS
Release 15.1.
Support for BGP large community introduced in Junos OS Release 17.3 for MX Series, PTX Series, and QFX Series.