Defining BGP Communities and Extended Communities for Use in Routing Policy Match Conditions

[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

To use a BGP community or extended community as a routing policy match condition, you define the community as described in the following sections:

Defining BGP Communities for Use in Routing Policy Match Conditions

To create a named BGP community and define the community members, 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-systems logical-system-name policy-options]

name identifies the community. It can contain letters, numbers, and hyphens (-) and can be up to 255 characters long. To include spaces in the name, enclose the entire name in quotation marks (“ ”).

community-ids identifies one or more members of the community. Each community ID consists of two components, which you specify in the following format:


            
               as-number:community-value;

as-number—AS number of the community member. It can be a value from 0 through 65,535. For more information about configuring AS numbers, see the JUNOS Routing Protocols Configuration Guide. You can use the following notation in specifying the AS number:
- String of digits.
- Asterisk (*)—A wildcard character that matches all AS numbers. (In the definition of the community attribute, the asterisk also functions as described in Table 18.)
- Period (.)—A wildcard character that matches any single digit in an AS number.
- Group of AS numbers—A single AS number or a group of AS numbers enclosed in parentheses. Grouping the numbers in this way allows you to perform a common operation on the group as a whole and to give the group precedence. The grouped numbers can themselves include regular expression operators. For more information about regular expressions, see Using UNIX Regular Expressions in Community Names.
community-value—Identifier of the community member. It can be a number from 0 through 65,535. You can use the following notation in specifying the community ID:
- String of digits.
- Asterisk (*)—A wildcard character that matches all community values. (In the definition of the community attribute, the asterisk also functions as described in Table 18.)
- Period (.)—A wildcard character that matches any single digit in a community value number.
- Group of community value numbers—A single community value number or a group of community value numbers enclosed in parentheses. Grouping the regular expression in this way allows you to perform a common operation on the group as a whole and to give the group precedence. The grouped path can itself include regular expression operators.

You can also include one of the following well-known community names (defined in RFC 1997, BGP Communities Attribute) in the community-ids option for the members statement:

no-advertise—Routes in this community name must not be advertised to other BGP peers.
no-export—Routes in this community must not be advertised outside a BGP confederation boundary.
no-export-subconfed—Routes in this community must not be advertised to external BGP peers, including peers in other members’ ASs inside a BGP confederation.

Using UNIX Regular Expressions in Community Names

When specifying the members of a named BGP community (in the members [ community-ids ] statement), you can use UNIX-style regular expressions to specify the AS number and the member identifier. A regular expression consists of two components, which you specify in the following format:


            
               term operator;

term identifies the string to match.

operator specifies how the term must match. Table 18 lists the regular expression operators supported in community IDs. You place an operator immediately after term with no intervening space, except for the pipe ( | ) and dash (–) operators, which you place between two terms, and parentheses, with which you enclose terms. Table 19 shows examples of how to define community-ids using community regular expressions. The operator is optional.

Community regular expressions are identical to the UNIX regular expressions. Both implement the extended (or modern) regular expressions as defined in POSIX 1003.2.

Community regular expressions evaluate the string specified in term on a character-by-character basis. For example, if you specify 1234:5678 as term, the regular expressions see nine discrete characters, including the colon (:), instead of two sets of numbers (1234 and 5678) separated by a colon.

Note: In JUNOS Release 9.1 and later, you can specify 4-byte AS numbers as defined in RFC 4893, BGP Support for Four-octet AS Number Space, as well as the 2-byte AS numbers that are supported in earlier releases of the JUNOS software. For more information about configuring AS numbers, see the JUNOS Routing Protocols Configuration Guide.

Table 18: Community Attribute Regular Expression Operators

Operator	Match Definition
{m,n}	At least m and at most n repetitions of term. Both m and n must be positive integers, and m must be smaller than n.
{m}	Exactly m repetitions of term. m must be a positive integer.
{m,}	m or more repetitions of term. m must be a positive integer.
*	Zero or more repetitions of term. This is equivalent to {0,}.
+	One or more repetitions of term. This is equivalent to {1,}.
?	Zero or one repetition of term. This is equivalent to {0,1}.
\|	One of the two terms on either side of the pipe.
–	Between a starting and ending range, inclusive.
^	Character at the beginning of a community attribute regular expression. We recommend the use of this operator for the clearest interpretation of your community attribute regular expression. If you do not use this operator, the regular expression 123:456 could also match a route tagged with 5123:456.
$	Character at the end of a community attribute regular expression. We recommend the use of this operator for the clearest interpretation of your community attribute regular expression. If you do not use this operator, the regular expression 123:456 could also match a route tagged with 123:4563.
[ ]	Set of characters. One character from the set can match. To specify the start and end of a range, use a hyphen (-). To specify a set of characters that do not match, use the caret (^) as the first character after the opening square bracket ([).
( )	Group of terms that are enclosed in parentheses. If enclosed in quotation marks with no intervening space ("()" ), indicates a null. Intervening space between the parentheses and the terms is ignored.
“ ”	Characters (such as space, tab, question mark, and bracket) that are enclosed within quotation marks in a community attribute regular expression indicate special characters.

Table 19: Examples of Community Attribute Regular Expressions

Community Attribute to Match	Regular Expression	Sample Matches
AS number is 56 or 78. Community value is any number.	^((56) \| (78)):(.*)$	56:1000 78:65000
AS number is 56. Community value is any number that starts with 2.	^56:(2.*)$	56:2 56:222 56:234
AS number is any number. Community value is any number that ends with 5, 7, or 9.	^(.):(.[579])$	1234:5 78:2357 34:65009
AS number is 56 or 78. Community value is any number that starts with 2 and ends with 2 through 8.	^((56) \| (78)):(2.*[2–8])$	56:22 56:21197 78:2678

Defining BGP Extended Communities for Use in Routing Policy Match Conditions

To create a named BGP community and define the community members, 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-systems logical-system-name policy-options]

community-ids identifies one or more members of the community. Each community ID consists of three components, which you specify in the following format:


            
               type:administrator:assigned-number

type is the type of extended community and can be either the 16-bit numerical identifier of a specific BGP extended community or one of these types:

bandwidth—Sets up the bandwidth extended community. Specifying link bandwidth allows you to distribute traffic unequally among different BGP paths.

Note: The link bandwidth attribute does not work concurrently with per-prefix load balancing.

domain-id—Identifies the OSPF domain from which the route originated.
origin —Identifies where the route originated.

rt-import—Identifies the route to install in the routing table.

Note: You must identify the route by an IP address, not an AS number.

src-as—Identifies the AS from which the route originated. You must specify an AS number, not an IP address.

Note: You must identify the AS by an AS number, not an IP address.

target —Identifies the destination to which the route is going.

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.

In JUNOS Release 9.1 and later, you can specify 4-byte AS numbers as defined in RFC 4893, BGP Support for Four-octet AS Number Space, as well as the 2-byte AS numbers that are supported in earlier releases of the JUNOS software. In plain-number format, you can configure a value in the range from 1 through 4,294,967,295. To configure a target or origin extended community that includes a 4-byte AS number in the plain-number format, append the letter “L” to the end of number. For example, a target community with the 4-byte AS number 334,324 and an assigned number of 132 is represented as target:334324L:132.

In JUNOS Release 9.2 and later, you can also use AS-dot notation when defining a 4-byte AS number for the target and origin extended communities. Specify two integers joined by a period: 16-bit high-order value in decimal.16-bit low-order value in decimal. For example, the 4-byte AS number represented in plain-number format as 65546 is represented in AS-dot notation as 1.10.

For more information about configuring AS numbers, see the JUNOS Routing Protocols Configuration Guide.

Examples: Defining BGP Extended Communities

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 10.1.1.1 and an assigned number of 20:


            
               [edit policy-options]
               community test-a members [ target:10.1.1.1:20 ];

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


            
               [edit policy-options]
               community test-a members [ origin:10.1.1.1:20 ];

Inverting Community Matches

To invert the results of the community expression matching, include the invert-match statement:


            
               invert-match;

You can include this statement at the following hierarchy levels:

[edit policy-options community name]
[edit logical-systems logical-system-name policy-options community name]

[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]