Configure the Layer 2 Circuit Community

To configure a community for Layer 2 circuits, include the community statement.

community name {

    members [ community-ids ]; 

}

You can include the community statement at the following hierarchy levels:

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

name identifies the community or communities.

community-ids identifies the type of community or extended community:

• A normal community uses the following community ID format:

as-number:community-value

as-number is the autonomous system (AS) number of the community member.

community-value is the identifier of the community member. It can be a number from 0 through 65,535.

• An extended community uses the following community ID format:

type:administrator:assigned-number

type is the type of target community. The target community identifies the route's destination.

administrator is either an AS number or an Internet Protocol version 4 (IPv4) address prefix, depending on the type of community.

assigned-number identifies the local provider.

You need to associate the communities with the appropriate Layer 2 circuits. To associate a community with a Layer 2 circuit, include the virtual-circuit-id and community statements:

virtual-circuit-id number;

community community-name;

You can include these statements at the following hierarchy levels:

• [edit protocols l2circuit neighbor address interface interface-name]
• [edit logical-routers logical-router-name protocols l2circuit neighbor address interface interface-name]