Policy Framework Configuration Guide - Juniper Networks

Chapter 5: Extended Match Conditions Configuration
Table 17: Community Attribute Regular Expression Operators (continued)
Operator
Match Definition
“ ”
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 18: 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]
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 three components, which you specify in the following format:
Copyright © 2010, Juniper Networks, Inc.
107