Filter
Top Products
Implementing Routing Policy on Cisco IOS XR Software
Information About Implementing Routing Policy
RC-208
Cisco IOS XR Routing Configuration Guide
surrounded by parentheses as follows: (<element-entry>,<element-entry>,<element-entry>,
...<element-entry>), where <element-entry> is an entry of an item appropriate to the type of usage such
as a prefix or a community value.
The following is an example using an inline community set:
route-policy sample-inline
if community matches-any ([10..15]:100) then
set local-preference 100
endif
end-policy
The following is an equivalent example using the named set test-communities:
community-set test-communities
10:100,
11:100,
12:100,
13:100,
14:100,
15:100
end-set
route-policy sample
if community matches-any test-communities then
set local-preference 100
endif
end-policy
Both of these policies are functionally equivalent, but the inline form does not require the configuration
of the community set just to store the six values. You can choose the form appropriate to the
configuration context. In the following sections, examples of both the named set version and the inline
form are provided where appropriate.
as-path-set
An AS path set comprises operations for matching an AS path attribute. The only matching operation is
a regular expression match.
Named Set Form
The named set form uses the ios-regex keyword to indicate the type of regular expression and requires
single quotation marks around the regular expression.
The following is a sample definition of a named AS path set:
as-path-set aset1
ios-regex ’_42$’,
ios-regex ’_127$’
end-set
This AS path set comprises two elements. When used in a matching operation, this AS path set matches
any route whose AS path ends with either the autonomous system (AS) number 42 or 127.
To remove the named AS path set, use the no as-path-set aset1 command-line interface (CLI) command.
Inline Set Form
The inline set form is a parenthesized list of comma-separated expressions, as follows:
(ios-regex '_42$', ios-regex '_127$')