Summary of Routing Policy Configuration Statements > community

Syntax

community name {

    bandwidth as:bandwidth;

    invert-match;

    members [ community-ids ]; 

}

Hierarchy Level

[edit logical-routers logical-router-name policy-options],

[edit policy-options]

Release Information

Statement introduced before JUNOS Release 7.4.

Description

Define a community or extended community for use in a routing policy match condition.

Options

name—Name that identifies the regular expression. The name can contain letters, numbers, and hyphens (-) and can be up to 255 characters. To include spaces in the name, enclose it in quotation marks (double quotes).

bandwidth as:bandwidth—Link bandwidth community attribute. as specifies the autonomous system and bandwidth specifies bandwidth in bytes per second.

invert-match—Invert the results of the community expression matching.

members community-ids—One or more community members. If you specify more than one member, you must enclose all members in brackets.

The format for community identifiers is:

as-number:community-value

as-number is the AS number and can be a value in the range 0 through 65,535. community-value is the community identifier and can be a number in the range 0 through 65,535.

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

• no-export—Routes containing this community name are not advertised outside a Border Gateway Protocol (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 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 the following:

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 Open Shortest Path First (OSPF) domain from which the route originated.

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

assigned-number identifies the local provider.

Usage Guidelines

See Configuring Communities.

Required Privilege Level

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