Configuring the Extended Communities Attribute

To configure extended communities, include the community statement:

community name {

    invert-match;

    members [ community-ids ]; 

}

You can include this statement at the following hierarchy levels:

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

To include the community in a routing policy, include the community condition in the from statement at the [edit policy-options policy-statement policy-name term term-name] hierarchy level:

[edit policy-options] 

community name members [ community-ids ]; 

policy-statement policy-name {

    term term-name {

        from {

            community name; 

        }

    } 

}

name identifies one or more routers in the BGP extended community.

community-ids identifies the type of extended community in the following format:

type:administrator:assigned-number

type is the type of extended community and can be either a bandwidth, target, origin, or domain-id community. The bandwidth community sets up the bandwidth extended 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 IP version 4 (IPv4) address prefix, depending on the type of extended community.

assigned-number identifies the local provider.

For information about the community attribute, see Configuring the Community Attribute.

NOTE: Regular expressions are not supported for extended communities.

Examples: Configuring the Extended Communities Attribute

Configure a target community with an administrative field of 10458 and an assigned number of 20:

[edit]

policy-options {

    community test-a members [target:10458:20];

}

Configure a target community with an administrative field of 1.1.1.1 and an assigned number of 20:

[edit]

policy-options {

    community test-a members [target:1.1.1.1:20];

}

Configure an origin community with an administrative field of 1.1.1.1 and an assigned number of 20:

[edit]

policy-options {

    community test-a members [origin:1.1.1.1:20];

}