Supported Platforms
Related Documentation
- ACX, J, M, MX, SRX, T Series
- Examples: Configuring Static Routes
- ACX, J, M, MX, PTX, SRX, T Series
- Example: Summarizing Routes Through Route Aggregation
- ACX, M, MX, T Series
- Example: Conditionally Generating Static Routes
- ACX, EX, M, MX, PTX, QFX, SRX, T Series
- aggregate
- generate
- ACX, EX, M, MX, PTX, SRX, T Series
- static
community (Routing Options)
Syntax
Hierarchy Level
Release Information
Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Description
Associate BGP community information with a static, aggregate, or generated route.
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 Policy Configuration 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 name are not advertised to external BGP peers, including peers in other members’ ASs inside a BGP confederation.
 | 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, see the Routing Policy Configuration Guide. |
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related Documentation
- ACX, J, M, MX, SRX, T Series
- Examples: Configuring Static Routes
- ACX, J, M, MX, PTX, SRX, T Series
- Example: Summarizing Routes Through Route Aggregation
- ACX, M, MX, T Series
- Example: Conditionally Generating Static Routes
- ACX, EX, M, MX, PTX, QFX, SRX, T Series
- aggregate
- generate
- ACX, EX, M, MX, PTX, SRX, T Series
- static
Published: 2013-01-17
Supported Platforms
Related Documentation
- ACX, J, M, MX, SRX, T Series
- Examples: Configuring Static Routes
- ACX, J, M, MX, PTX, SRX, T Series
- Example: Summarizing Routes Through Route Aggregation
- ACX, M, MX, T Series
- Example: Conditionally Generating Static Routes
- ACX, EX, M, MX, PTX, QFX, SRX, T Series
- aggregate
- generate
- ACX, EX, M, MX, PTX, SRX, T Series
- static
