-
Cisco IOS XR Routing Command Reference, Release 3.3
-
Preface
-
BGP Commands on Cisco IOS XR Software
-
EIGRP Commands on Cisco IOS XR Software
-
IS-IS Commands on Cisco IOS XR Software
-
RIB Commands on Cisco IOS XR Software
-
RIP Commands on Cisco IOS XR Software
-
OSPF Commands on Cisco IOS XR Software
-
OSPFv3 Commands on Cisco IOS XR Software
-
Routing Policy Language Commands on Cisco IOS XR Software
-
Static Routing Commands on Cisco IOS XR Software
-
Index
-
Table Of Contents
Routing Policy Language Commands on Cisco IOS XR Software
extcommunity soo matches-every
show rpl active extcommunity-set
show rpl as-path-set attachpoints
show rpl as-path-set references
show rpl community-set attachpoints
show rpl community-set references
show rpl inactive community-set
show rpl inactive extcommunity-set
show rpl inactive route-policy
show rpl prefix-set attachpoints
show rpl prefix-set references
show rpl route-policy attachpoints
show rpl route-policy references
show rpl unused extcommunity-set
Routing Policy Language Commands on Cisco IOS XR Software
This chapter describes the Cisco IOS XR software routing policy language (RPL) commands used to create, modify, monitor, and maintain routing policies.
For detailed information about RPL concepts, configuration tasks, and examples, see Implementing Routing Policy on Cisco IOS XR Software.
abort
To discard a route policy or set definition and return to global configuration mode, use the abort command in route-policy configuration mode.
abort
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Prefix set configurationCommand History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to discard a route policy definition that was started and return to global configuration mode:
RP/0/RP0/CPU0:router(config)# route-policy policy_1RP/0/RP0/CPU0:router(config-rpl)# if as-path is-local thenRP/0/RP0/CPU0:router(config-rpl-if)# abortRP/0/RP0/CPU0:router(config)#The following example shows how to discard a prefix set definition that was started and return to global configuration mode:
RP/0/RP0/CPU0:router(config)# prefix-set legal-ipv4-prefix-examplesRP/0/RP0/CPU0:router(config-pfx)# 10.0.1.1,RP/0/RP0/CPU0:router(config-pfx)# 10.0.2.0/24,RP/0/RP0/CPU0:router(config-pfx)# abortRP/0/RP0/CPU0:router(config)#Related Commands
add
To add an offset to an existing value, use the add command in route-policy configuration mode.
add {eigrp-metric bandwidth | rip-metric {number | parameter}}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to add 1000 kilobits per second to the EIGRP metric:
RP/0/RP0/CPU0:router(config)# route-policy policy_1RP/0/RP0/CPU0:router(config-rpl)# add eigrp-metric 1000RP/0/RP0/CPU0:router(config-rpl)# end-policyapply
To execute a parameterized or unparameterized policy from within another policy, use the apply command in route-policy configuration mode.
apply name [parameter1, parameter2, . . . , parameterN]
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the apply command to execute a policy (either parameterized or unparameterized) from within another policy, which allows for the reuse of common blocks of policy.
Task ID
Examples
In the following example, the policy CustomerIn applies the route-policy SetLocalPref to conditionally set the local preference on a route. The parameters 20, 30, 40, and 50 are passed to the parameterized policy SetLocalPref, where the local preference is set to:
•
20, if the community 217:20 is present in the route
•
•
•
RP/0/RP0/CPU0:router(config)# route-policy CustomerInRP/0/RP0/CPU0:router(config-rpl)# apply SetLocalPref (20, 30, 40, 50)RP/0/RP0/CPU0:router(config-rpl)# end-policyRP/0/RP0/CPU0:router(config)# route-policy SetLocalPref ($lp1, $lp2, $lp3, $lp4)RP/0/RP0/CPU0:router(config-rpl)# if community matches-any (217:$lp1) thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference $lp1RP/0/RP0/CPU0:router(config-rpl-elseif)# elseif community matches-any (217:$lp2) thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference $lp2RP/0/RP0/CPU0:router(config-rpl-elseif)# elseif community matches-any (217:$lp3) thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference $lp3RP/0/RP0/CPU0:router(config-rpl-elseif)# elseif community matches-any (217:$lp4) thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference $lp4RP/0/RP0/CPU0:router(config-rpl-elseif)# endifRP/0/RP0/CPU0:router(config-rpl)# end-policyas-path in
To match the AS path of a route to an AS path set, use the as-path in command in route-policy configuration mode.
as-path in {as-path-set-name | inline-as-path-set}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the as-path in command as a conditional expression within an if statement to match the AS path of a route to an AS path set. The AS path is a sequence of autonomous system numbers traversed by a route.
Note
The as-path in command evaluates to true if at least one of the regular expressions defined in the associated AS path set matches the AS path attribute of the route.
In the case where the AS path set is defined but contains no elements in it, the as-path in conditional expression command returns false.
Task ID
Examples
For example, assume we have an AS path set named my-as-set defined as follows:
RP/0/RP0/CPU0:router(config)# as-path-set my-as-setRP/0/RP0/CPU0:router(config-as)# ios-regex '_12$',RP/0/RP0/CPU0:router(config-as)# ios-regex '_13$'RP/0/RP0/CPU0:router(config-as)# end-setand the following policy excerpt using an as-path-set-name argument:
RP/0/RP0/CPU0:router(config-rpl)# if as-path in my-as-set thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 100RP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)#The AS path in condition evaluates to true if one or more of the regular expression matches in the set my-as-set match the AS path associated with the route. In the case of a defined but empty AS path set, this operator returns false.
The preceding policy excerpt is equivalent to the following version, which uses an inline-as-path set variable:
RP/0/RP0/CPU0:router(config-rpl)# if as-path in (ios-regex `_12$,ios-regex `_13$') thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 100RP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)#as-path is-local
To determine if this router or another router within this autonomous system or confederation originated a route, use the as-path is-local command in route-policy configuration mode.
as-path is-local
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the as-path is-local command as a conditional expression within an if statement to determine if this router (or another router within this autonomous system or confederation) originated the route.
Note
Routes that are locally originated within the autonomous system or confederation carry an empty AS path. For the Border Gateway Protocol (BGP) specification, when a route is advertised across the autonomous system boundary or a confederation boundary, the local autonomous system number or confederation ID is appended to the autonomous system path. The AS path of a locally originated aggregate is also empty unless it has been modified by policy.
The is-local operator evaluates to true for autonomous system paths that are empty. An empty AS path is how an AS path that is local to our autonomous system is represented in BGP.
Task ID
Examples
In the following example, if the AS path is local, then the local preference is set to 100:
RP/0/RP0/CPU0:router(config-rpl)# if as-path is-local thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 100RP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)#as-path length
To compare the number of ASN in the AS path of a route, use the as-path length command in route-policy configuration mode.
as-path length {eq | is | ge | le} {number | parameter}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the as-path length command as a conditional expression within an if statement to perform a conditional check based on the length of the AS path.
Note
This command takes either a specific integer value or a range of integer values specified with the ge and le operators. Any or all of these integers can be parameterized. The operator counts one for each autonomous system in the path. In the case where the route may be aggregated and contain one or more as-sets, the length operator adds one for each set present, the occurrence of an as-set typically indicates that this route is an aggregated route, and the aggregated route had a component route that contained one of the autonomous systems in the set. Likewise, in the case of confederations, a count of one is added for each confederation in the path or each confederation set in the path. A null AS path has a length of zero.
Task ID
Examples
In the following example, if the AS path length equals 10, then the local preference is set to 100:RP/0/RP0/CPU0:router(config-rpl)# if as-path length eq 10 thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 100RP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)#Related Commands
as-path neighbor-is
To test to learn if the sequence of autonomous system numbers matches the path beginning with the neighboring autonomous system from which a route was heard, use the as-path neighbor-is command in route-policy configuration mode.
as-path neighbor-is as-number-list [exact]
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the as-path neighbor-is command as a conditional expression within an if statement to test the autonomous system number or numbers at the head of the AS path against a sequence of one or more integral values or parameters, in other words, to test to learn if the sequence of autonomous system numbers matches the path beginning with the neighboring autonomous system from which this route was heard.
Note
This command has an equivalent regular expression (ios-regex). For example, AS path neighbor-is `1' would be `^1_'.
Task ID
Examples
The following are incomplete configuration examples:RP/0/RP0/CPU0:router(config-rpl)# if as-path neighbor-is '10' thenRP/0/RP0/CPU0:router(config-rpl-if)# if as-path neighbor-is '$asnum' thenRP/0/RP0/CPU0:router(config-rpl-if)# if as-path neighbor-is '10 20' thenThese statements evaluate to true when the first autonomous system numbers on the AS path match, in the same order, the supplied parameters or integer values in the neighbor-is statement. If the neighboring autonomous system location happens to be an AS-set, the operator evaluates to true if the corresponding argument to the neighbor-is operator is an element of the AS-set.
Without the exact keyword, repeated autonomous system numbers in the AS path are ignored. For example,
RP/0/RP0/CPU0:router(config-rpl)# if as-path neighbor-is '10 20' thenmatches an AS path beginning
10 10 10 20 ...and an AS path beginning:
10 20 ....With the exact keyword, repetitions are not ignored, therefore
RP/0/RP0/CPU0:router(config-rpl)# if as-path neighbor-is '10 20' exact thenmatches the second of these AS paths but not the first.
Related Commands
as-path originates-from
To compare an AS path against the AS sequence beginning with the AS number that originated a route, use the as-path originates-from command in route-policy configuration mode.
as-path originates-from as-number-list [exact]
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the as-path originates-from command as a conditional expression within an if statement to compare an AS path to the autonomous system sequence.
Note
The originates-from operator is similar to the neighbor-is operator, except that it looks at the autonomous system number at the opposite end of the AS path. In other words, it is comparing to the autonomous system that originated the route. It can take numbers or parameters, enclosed in single quotation marks, that represent a sequence of autonomous system numbers. When more than one number is specified in the list, the sequence of autonomous system numbers listed must appear as a subsequence in the AS path, with the last number corresponding to the autonomous system that originated the route.
Task ID
Examples
The following are incomplete configuration examples:
RP/0/RP0/CPU0:router(config-rpl)# if as-path originates-from '10 11' thenRP/0/RP0/CPU0:router(config-rpl-if)# if as-path originates-from '$asnum 11' thenThe first line of the preceding example evaluates to true if autonomous system 11 originated the route and then advertised it to autonomous system 10, from which the route was eventually propagated to us. In the case where the route has been aggregated, and the location of the originating autonomous system contains an AS-set, the originates-from operator evaluates to true if the argument to the originates-from operator is contained in the AS-set.
Without the exact keyword, repeated autonomous system numbers in the AS path are ignored. For example,
RP/0/RP0/CPU0:router(config-rpl)# if as-path originates-from '10 11' thenmatches an autonomous system path ending
...10 10 10 11and an autonomous system path ending
...10 11With the exact keyword, repetitions are not ignored, therefore
RP/0/RP0/CPU0:router(config-rpl)# if as-path originates-from '10 11' exact thenmatches the second of these autonomous system paths but not the first.
Related Commands
as-path passes-through
To verify if the supplied integer or parameter appears anywhere in the AS path or if the supplied sequence of integers and parameters appears, in the same order, anywhere in the AS path, use the as-path passes-through command in route-policy configuration mode.
as-path passes-through as-number-list [exact]
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the as-path passes-through command as a conditional expression within an if statement to verify if the specified integer or parameter appears anywhere in the AS path or if the sequence of integers and parameters appears.
Note
The passes-through operator takes a sequence of integers or parameters, enclosed in single quotation marks, as an argument. It can also take a single integer or parameter as an argument. It evaluates to true if the supplied integer or parameter appears anywhere in the AS path, or if the supplied sequence of integers and parameters appears, in the same order, anywhere in the AS path. This includes the originates-from or neighbor-is location in the AS path.
Task ID
Examples
The following are incomplete configuration examples:
RP/0/RP0/CPU0:router(config-rpl)# if as-path passes-through '10' thenRP/0/RP0/CPU0:router(config-rpl-if)# if as-path passes-through '$asnum' thenRP/0/RP0/CPU0:router(config-rpl-if)# if as-path passes-through '10 11' thenRP/0/RP0/CPU0:router(config-rpl-if)# if as-path passes-through '10 $asnum 12' thenWithout the exact keyword, repeated autonomous system numbers in the AS path are ignored. For example:
RP/0/RP0/CPU0:router(config-rpl)# if as-path passes-through '9 10 11' thenmatches an AS path containing
...9 10 10 10 11 ....and an AS path containing:
...9 10 11...With the exact keyword, repetitions are not ignored. Therefore:
RP/0/RP0/CPU0:router(config-rpl)# if as-path passes-through '9 10 11' exact thenmatches the second of these AS paths but not the first.
Related Commands
as-path-set
To create a named AS path set, use the as-path-set command in global configuration mode. To remove the named AS path set, use the no form of this command.
as-path-set name
no as-path-set name
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the as-path-set command to create a named AS path set.
An AS path set comprises operations for matching an AS path attribute.
This command enters AS path set configuration mode, in which you can use the ios-regex keyword to indicate the type of regular expression. Single quotation marks are required around the regular expression.
The inline set form is a parenthesized list of comma-separated expressions.
See the "Understanding Regular Expressions, Special Characters and Patterns" appendix in Cisco IOS XR Getting Started Guide for information about forming regular expressions.
Task ID
Examples
The following is a sample definition of an AS path set named aset1:
RP/0/RP0/CPU0:router(config)# as-path-set aset1RP/0/RP0/CPU0:router(config-as)# ios-regex '_42$',RP/0/RP0/CPU0:router(config-as)# ios-regex '_127$'RP/0/RP0/CPU0:router(config-as)# end-setThis AS path set is composed of two elements. When used in a matching operation, this AS path set matches any route whose AS path ends with either the autonomous system number 42 or 127.
The following is a sample of an inline set:
RP/0/RP0/CPU0:router(config-rpl)# if as-path in (ios-regex '_42$', ios-regex$ '_127$')RP/0/RP0/CPU0:router(config-rpl-if)# passRP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)#as-path unique-length
To perform specific checks based on the length of the AS path, use the as-path unique-length command in route-policy configuration mode.
as-path unique-length {eq | is | ge | le} {number | parameter}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the as-path unique-length command as a conditional expression within an if statement to perform a check based on the length of the AS path.
Note
The unique-length operator is similar to the length operator, except that when an AS path has been padded with the same autonomous system number multiple times, the operator counts only one when the route is padded. Therefore, given an AS path of 333 333 111 222 123 444 444 444, the unique-length operator would return a value of 5, whereas the length operator would return a value of 8.
Task ID
Examples
The following example shows show to perform checks based on the AS path length. If the AS path matches the specified values, the local preference is set to 100:
RP/0/RP0/CPU0:router(config-rpl)# if as-path unique-length eq 10 thenRP/0/RP0/CPU0:router(config-rpl-if)# if as-path unique-length ge 10 thenRP/0/RP0/CPU0:router(config-rpl-if)# if as-path unique-length le 10 thenRP/0/RP0/CPU0:router(config-rpl)# if as-path unique-length eq $integerparam thenRP/0/RP0/CPU0:router(config-rpl-if)# if as-path unique-length ge $geparam thenRP/0/RP0/CPU0:router(config-rpl-if)# if as-path unique-length le $leparam thenRP/0/RP0/CPU0:router(config-rpl)# set local-preference 100RP/0/RP0/CPU0:router(config-rpl)# endifRelated Commands
community is-empty
To learn if a route has no community attributes associated with it, use the community is-empty command in route-policy configuration mode.
community is-empty
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the community is-empty command as a conditional expression within an if statement to learn if a route has community attributes associated with it.
Note
This command takes no arguments and evaluates to true only if the route has no community attributes associated with it.
Task ID
Examples
In the following example, if the route has no community attributes associated with it, then the local preference is set to 100:
RP/0/RP0/CPU0:router(config-rpl)# if community is-empty thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 100RP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)#community matches-any
To match any elements of a community set, use the community matches-any command in route-policy configuration mode.
community matches-any {community-set-name | inline-community-set}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the community matches-any command as a conditional expression within an if statement to match any element of a community set.
Note
A simple condition using the matches-any operator evaluates as true if at least one community element of the community attribute for the route matches an element in the community set operand. If no community in the route matches any of the specifications in the named or inline set, then the condition evaluates to false. Likewise, when there is no community at all in the route, the condition evaluates to false.
Matching of a community in the route to a specification in a named or an inline set is intuitive. If the community specification in a set is the familiar colon-separated decimal 16-bit numbers specification, or one of the well-known communities, the community matches the specification if the specification denotes the same 32-bit number as that in the route. If the community specification uses a wildcard, then the community in the route matches if it is one of the many communities denoted by the wildcard specification. In inline sets, community specifications may be parameterized, in which case the relevant matching is done when the value of the parameter has been supplied.
Communities may also be matched using range and regular expression operators. Range specifications are entered as follows: [low-value..high-value]. Either or both colon-separated halves of a community value may contain a range. The following are valid range specifications:
10:[100..1000][10..100]:80[10..100]:[100..2000]In addition, the private-as keyword may be used to specify the range from 64512 to 65534. Regular expressions are specified as the ios-regex keyword followed by a valid regular expression string.
Community values from the route are matched one at a time to the match specifications. Therefore, regex match specifications are expected to represent one individual community value and not a sequence of community values.
Task ID
Examples
In the following example, a named community set called my-community-set and a route policy called community-matches-any-example are created. The policy sets the local-preference to 100 for any route that has one or more of the communities in the my-community-set community set. If the route does not have any of these communities, the policy checks whether it has any communities whose first half is in the range from 10 to 25 and whose second half is the value 35, in which case it sets the local-preference to 200. Otherwise, it checks for a community value in the range of 30:100 to 30:500, in which case it sets the local-preference to 300.
RP/0/RP0/CPU0:router(config)# community-set my-community-setRP/0/RP0/CPU0:router(config-comm)# 10:20,RP/0/RP0/CPU0:router(config-comm)# 10:30,RP/0/RP0/CPU0:router(config-comm)# 10:40RP/0/RP0/CPU0:router(config-comm)# end-setRP/0/RP0/CPU0:router(config)# route-policy community-matches-any-exampleRP/0/RP0/CPU0:router(config-rpl)# if community matches-any my-community-set thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 100RP/0/RP0/CPU0:router(config-rpl-if)# elseif community matches-any ([10..25]:35) thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference 200RP/0/RP0/CPU0:router(config-rpl-elseif)# elseif community matches-any (30:[100..500]) thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference 300RP/0/RP0/CPU0:router(config-rpl-elseif)# endifRP/0/RP0/CPU0:router(config-rpl)# end-policyRelated Commands
community matches-every
To match every element of a community set, use the community matches-every command in route-policy configuration mode.
community matches-every {community-set-name | inline-community-set}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the community matches-every command as a conditional expression within an if statement to match every element of a community set.
Note
A simple condition using the matches-every operator evaluates as true if every specification in the named set or inline set specified matches at least one community value in the route. If any community specification in the named or inline set is not matched, then the operation evaluates to false.
Matching of a community in the route to a specification in a named or an inline set is intuitive. If the community-specification in a set is the familiar colon-separated decimal 16-bit numbers specification, or one of the well-known communities, the community matches the specification if the specification denotes the same 32-bit number as that in the route. If the community specification uses a wildcard, then the community in the route matches if it is one of the many communities denoted by the wildcard specification. In inline sets, community specifications may be parameterized, in which case the relevant matching is done when the value of the parameter has been supplied.
Communities may also be matched using range and regular expression operators. Range specifications are entered as follows: [low-value..high-value]. Either or both colon-separated halves of a community value may contain a range. The following are valid range specifications:
10:[100..1000][10..100]:80[10..100]:[100..2000]Therefore, a matches-every operation with two community range specifications means that a community must be present in the route that corresponds to each range. For example, in the following statement:
if community matches-every (10:[100..200],20:[100..200]) thenthe statement evaluates as true if one or more communities in the route lie in the range 10:[100.200] and one or more communities in the route lie in the range 20:[100..200].
In addition, the private-as keyword may be used to specify the range from 64512 to 65534.
Regular expressions are specified as the ios-regex keyword followed by a valid single-quoted regular expression string. Community values from the route are matched one at a time against the match specifications. Therefore, regex match specifications are expected to represent one individual community value and not a sequence of community values.
Task ID
Examples
In the following example, the route policy named community-matches-every-example sets the local-preference value to 100 for all routes that have all three communities in the my-community-set community set. Routes that do not have all three communities but have a community that matches the first regular expression match have the local-preference value set to 200. Finally, any remaining routes that match the last regular expression have the local-preference values set to 300.
RP/0/RP0/CPU0:router(config)# community-set my-community-setRP/0/RP0/CPU0:router(config-comm)# 10:20,RP/0/RP0/CPU0:router(config-comm)# 10:30,RP/0/RP0/CPU0:router(config-comm)# 10:40RP/0/RP0/CPU0:router(config-comm)# end-setRP/0/RP0/CPU0:router(config)# route-policy community-matches-every-exampleRP/0/RP0/CPU0:router(config-rpl)# if community matches-every my-community-set thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 100RP/0/RP0/CPU0:router(config-rp-elseif)# elseif community matches-every (ios-regex '_10:[0-9]0_') thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference 200RP/0/RP0/CPU0:router(config-rpl-elseif)# elseif community matches-every (ios-regex'_20:[0-9]0_') thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference 300RP/0/RP0/CPU0:router(config-rpl-elseif)# endifRP/0/RP0/CPU0:router(config-rpl)# end-policyRelated Commands
community-set
To define a community set, use the community-set command in global configuration mode. To remove the community set, use the no form of this command.
community-set name
no community-set name
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Regular expressions and ranges can be specified in a community set to support the matching or deleting of communities using ranges or regular expressions in named community sets. An attempt to use a community set that contains a range or regular expression to set a community value is rejected when an attempt to attach such a policy is made.
A community set holds community values for matching against the Border Gateway Protocol (BGP) community attribute. A community is a 32-bit quantity. For notational convenience, each community value must be split in half and expressed as two unsigned decimal integers in the range from 0 to 65535, separated by a colon.
The inline form of a community set also supports parameterization. Each 16-bit portion of the community may be parameterized.
The routing policy language (RPL) provides symbolic names for the standard well-known community values: internet is 0:0, no-export is 65535:65281, no-advertise is 65535:65282, and local-as is 65535:65283.
RPL also provides a facility for using wildcards in community specifications. A wildcard is specified by inserting an asterisk (*) in place of one of the 16-bit portions of the community specification, which indicates that any value for that portion of the community matches.
Every community set must contain at least one community value. An empty community set is invalid and the policy configuration system rejects it.
Task ID
Examples
In the following example, a community set named cset1 is created:
RP/0/RP0/CPU0:router(config)# community-set cset1RP/0/RP0/CPU0:router(config-comm)# 12:34,RP/0/RP0/CPU0:router(config-comm)# 12:56,RP/0/RP0/CPU0:router(config-comm)# 12:78,RP/0/RP0/CPU0:router(config-comm)# internetRP/0/RP0/CPU0:router(config-comm)# end-setIn the following example, a community set named cset2 is created:
RP/0/RP0/CPU0:router(config)# community-set cset2RP/0/RP0/CPU0:router(config-comm)# 123:456,RP/0/RP0/CPU0:router(config-comm)# no-advertise,RP/0/RP0/CPU0:router(config-comm)# end-setIn the following example, a community set named cset3 is created. This policy uses wildcards and matches all communities where the autonomous system part of the community is 123.
RP/0/RP0/CPU0:router(config)# community-set cset3RP/0/RP0/CPU0:router(config-comm)# 123:*RP/0/RP0/CPU0:router(config-comm)# end-setdelete community
To delete community values from a community list in a route, use the delete community command in route-policy configuration mode.
delete community {all | in {community-set-name | inline-community-set} | not in {community-set-name | inline-community-set}}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the delete community command to delete community values from a community list in a route.
Note
Communities are 32-bit values carried in Border Gateway Protocol (BGP) routes. Each route may have zero or more communities in an unordered list.
You can remove a well-known community (internet, no-export, no-advertise, or local-as) from a route, but this removal must be done explicitly. This command should be used with a degree of caution. In general, few circumstances exist in which you would need to remove a well-known community.
Task ID
Examples
The following example shows how to delete any communities associated with the routes that are listed in either the named community set or inline community set, respectively.
RP/0/RP0/CPU0:router(config-rpl)# delete community in my_community_setRP/0/RP0/CPU0:router(config-rpl)# delete community in (10:[0..50],20:[60..80])The following example shows how to remove all communities except for the well-known communities.
RP/0/RP0/CPU0:router(config-rpl)# delete community allThe following example shows how to delete the well-known community value internet from a route:
RP/0/RP0/CPU0:router(config-rpl)# delete community in (internet)delete extcommunity rt
To delete extended community values from a BGP route target extended community list in a route, use the delete extcommunity rt command in route-policy configuration mode.
delete extcommunity rt {all | in {extcommunity-set-name | inline-extcommunity-set} | not in {extcommunity-set-name | inline-extcommunity-set}}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the delete extcommunity rt command to delete extended community values from a BGP route target extended community list in a route.
Note
Extended communities are similar to regular Border Gateway Protocol (BGP) communities but contain more data and have a richer structure for encoding information in them.
Extended communities can be in the following forms: SoO:AS:tag, SoO:IP:tag, RT:AS:tag, or RT:IP:tag.
Wildcards (*) are not allowed for extended community set elements.
The forms of this command that take a named extended community set or an inline extended community set value as arguments are equivalent. They delete any extended communities that are listed in either the named set or the inline set, respectively.
Task ID
Examples
In the following example, all extended communities are deleted:
RP/0/RP0/CPU0:router(config-rpl)# delete extcommunity rt allIn this example, any extended communities that are listed in my-extcommunity-set are deleted:
RP/0/RP0/CPU0:router(config-rpl)# delete extcommunity rt in my-extcommunity-setIn this example, extended communities associated with the route listed in the named inline extended community sets are deleted:
RP/0/RP0/CPU0:router(config-rpl)# delete extcommunity rt in (RT:67:29, RT:67:55)destination in
To match a destination entry in a named prefix set or inline prefix set, use the destination in command in route-policy configuration mode.
destination in {prefix-set-name | inline-prefix-set}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the destination in command as a conditional expression within an if statement to match a destination entry in a named prefix set or inline prefix set.
Note
This command takes either a named prefix set or an inline prefix set value as an argument. The condition returns true if the destination entry matches any entry in the prefix set or inline prefix set. An attempt to match a destination using a prefix set that is defined but contains no elements returns false.
The destination of a route is also known in Border Gateway Protocol (BGP) as its network-layer reachability information (NLRI). It comprises a prefix value and a mask length. The routing policy language (RPL) provides the ability to test destinations for a match to a list of prefix match specifications using the in operator.
RPL supports both 32-bit IPv4 prefixes, specified in dotted-decimal format, and 128-bit IPv6 prefixes, specified in colon-separated hexadecimal format.
Task ID
Examples
In the following example, a prefix set named my-prefix-set is defined and a route policy named use-destination-in is created. Within the use-destination-in route policy, the destination in command is used within an if statement to learn if the destination is in the prefix-set named my-prefix-set. If it is, then local preference is set to 100. If it is not in my-prefix-set but does match the next prefix specifications, then local preference is set to 200.
RP/0/RP0/CPU0:router(config)# prefix-set my-prefix-setRP/0/RP0/CPU0:router(config-pfx)# 10.0.0.1/32,RP/0/RP0/CPU0:router(config-pfx)# fe80::203:0:0:0/64,RP/0/RP0/CPU0:router(config-pfx)# 10.0.0.2/24 le 32RP/0/RP0/CPU0:router(config-pfx)# end-setRP/0/RP0/CPU0:router(config)# route-policy use-destination-inRP/0/RP0/CPU0:router(config-rpl)# if destination in my-prefix-set thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 100RP/0/RP0/CPU0:router(config-rpl-if)# elseif destination in (10.0.0.1/32, 10.0.0.2/24 le 32) thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference 200RP/0/RP0/CPU0:router(config-rpl-elseif)# endifRP/0/RP0/CPU0:router(config-rpl)# end-policyIn the following example, a prefix set named ipv6-prefix-set is defined and a route policy named ipv6-destination-in is created. Within the ipv6-destination-in route policy, the destination in command is used within an if statement to learn if the destination is in the prefix-set named ipv6-prefix-set. If it is, then the next hop is set to 2001:abcd:fedc::1. If it is not in ipv6-prefix-set but does match the next prefix specifications, then the next hop is set to 1111:2222:3333:4444:5555:6666:7777:8888.
RP/0/RP0/CPU0:router(config)# prefix-set ipv6-prefix-setRP/0/RP0/CPU0:router(config-pfx)# 2001:0:0:1::/64,RP/0/RP0/CPU0:router(config-pfx)# 2001:0:0:2::/64,RP/0/RP0/CPU0:router(config-pfx)# 2001:0:0:3::/64,RP/0/RP0/CPU0:router(config-pfx)# 2001:0:0:4::/64RP/0/RP0/CPU0:router(config-pfx)# end-setRP/0/RP0/CPU0:router(config)# route-policy ipv6-destination-inRP/0/RP0/CPU0:router(config-rpl)# if destination in ipv6-prefix-set thenRP/0/RP0/CPU0:router(config-rpl-if)# set next-hop 2001:abcd:fedc::1RP/0/RP0/CPU0:router(config-rpl-if)# elseif destination in (2001::1, 2002:1:2:3::/64) thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set next-hop 1111:2222:3333:4444:5555:6666:7777:8888RP/0/RP0/CPU0:router(config-rpl-elseif)# endifRP/0/RP0/CPU0:router(config-rpl)# end-policydrop
To discard a route, use the drop command in route-policy configuration mode.
drop
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the drop command within a route policy to drop a route.
Note
This command signifies to the engine that executes policy that the action to take is to discard the route. After a route is dropped, no further execution of policy occurs. Therefore, if after executing the first two statements of a policy the drop statement is encountered, the route is discarded and execution stops immediately even when the policy contains further statements.
Note
Task ID
Examples
In the following example, any route with a destination address contained within the prefix set pset1 is dropped:
RP/0/RP0/CPU0:router(config-rpl)# if destination in pset1 thenRP/0/RP0/CPU0:router(config-rpl-if)# dropRP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)#edit
To edit the contents of a route policy, a prefix set, an AS path set, a community set, or an extended community set, use the edit command in EXEC mode.
edit {{route-policy | prefix-set | as-path-set | community-set | extended-community-set} emacs | vim} name
Syntax Description
Defaults
Default editor is Micro Emacs
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the edit command to edit the contents of a route policy, a prefix set, an AS path set, a community set, or an extended community set.
After editing with Emacs, save the editor buffer by using the Ctrl-x and Ctrl-s keystrokes. To save and exit the editor, use the Ctrl-x and Ctrl-c keystrokes.
After editing with Vim, to write to a current file and exit use the :wq or :x or ZZ keystrokes. To quit and confirm, use the :q keystrokes. To quit and discard changes, use the :q! keystrokes.
Task ID
Examples
In the following example, the policy_A policy is opened in the editor:
RP/0/RP0/CPU0:router# edit route-policy policy_A----------------------------------------== MicroEMACS 3.8b () == rpl_edit.139281 ==if destination in (2001::/8) thendropendifend-policy!== MicroEMACS 3.8b () == rpl_edit.139281 ==Parsing.83 bytes parsed in 1 sec (82)bytes/secCommitting.1 items committed in 1 sec (0)items/secUpdating.Updated Commit database in 1 secRP/0/RP0/CPU0:router#If there are parse errors, you are asked whether editing should continue:
RP/0/RP0/CPU0:router#edit route-policy policy_B== MicroEMACS 3.8b () == rpl_edit.141738route-policy policy_Bset metric-type type_1if destination in (2001::/8) thendropendifend-policy!== MicroEMACS 3.8b () == rpl_edit.141738 ==Parsing.105 bytes parsed in 1 sec (103)bytes/sec% Syntax/Authorization errors in one or more commands.!! CONFIGURATIONFAILED DUE TO SYNTAX/AUTHORIZATION ERRORSset metric-type type_1if destination in (2001::/8) thendropendifend-policy!Continue editing? [no]:If you answer yes, the editor continues on the text buffer from where you left off. If you answer no, the running configuration is not changed and the editing session is ended.
After the policy is opened, it may be manipulated using normal editor commands, then saved and committed to the running configuration.
end-policy
To end the definition of a route policy and exit route-policy configuration mode, use the end-policy command in route-policy configuration mode.
end-policy
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the end-policy command to end the definition of a route policy and exit route-policy configuration mode.
Task ID
Examples
In the following example, the end-policy command ends the definition of a route policy:
RP/0/RP0/CPU0:router(config)# route-policy med-to-local-prefRP/0/RP0/CPU0:router(config-rpl)# if med eq 150 thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 10RP/0/RP0/CPU0:router(config-rpl-if)# elseif med eq 200 thenRP/0/RP0/CPU0:router(config-elseif)# set local-preference 60RP/0/RP0/CPU0:router(config-elseif)# elseif med eq 250 thenRP/0/RP0/CPU0:router(config-elseif)# set local-preference 0RP/0/RP0/CPU0:router(config-elseif)# endifRP/0/RP0/CPU0:router(config-rpl)# end-policyend-set
To end the definition of an AS path set, a prefix set, a community set, an extended community set, or an RD set and return to global configuration mode, use the end-set command in route-policy configuration mode.
end-set
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the end-set command to end the definition of an AS path set, a prefix set, a community set, or an extended community set.
Task ID
Examples
In the following example, the end-set command ends the definition of an AS path set named aset1:
RP/0/RP0/CPU0:router(config)# as-path-set aset1RP/0/RP0/CPU0:router(config-as)# ios-regex '_42$',RP/0/RP0/CPU0:router(config-as)# ios-regex '_127$'RP/0/RP0/CPU0:router(config-as)# end-setRP/0/RP0/CPU0:router(config)#The following example shows how to create an RD set called my_rd_set and use the end-set command to end the definition:
RP/0/RP0/CPU0:router(config)# rd-set my_rd_setRP/0/RP0/CPU0:router(config-rd)# 172.16.0.0/16:*,RP/0/RP0/CPU0:router(config-rd)# 172.17.0.0/16:100,RP/0/RP0/CPU0:router(config-rd)# 192:*,RP/0/RP0/CPU0:router(config-rd)# 192:100RP/0/RP0/CPU0:router(config-rd)# end-setextcommunity rt is-empty
To test to learn if a Border Gateway Protocol (BGP) route target (RT) has extended community attributes associated with it, use the extcommunity rt is-empty command in route-policy configuration mode.
extcommunity rt is-empty
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or value
Command Modes
Route-policy configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
This command replaced the extcommunity is-empty command.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the extcommunity rt is-empty command as a conditional expression within an if statement to learn if a BGP route has extended community attributes associated with it.
Note
The is-empty operator takes no arguments and evaluates to true if the route has no extended community attributes associated with it.
Task ID
Examples
In the following example, if the extended community is empty, then the local preference is set to 100:
RP/0/RP0/CPU0:router(config)# route-policy extcommunity-is-empty-exampleRP/0/RP0/CPU0:router(config-rpl)# if extcommunity rt is-empty thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 100RP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)# end-policyextcommunity rt matches-any
To match any element of a Border Gateway Protocol (BGP) route target (RT) extended community set, use the extcommunity rt matches-any command in route-policy configuration mode.
extcommunity rt matches-any {extcommunity-set-name | inline-extcommunity-set}
Syntax Description
extcommunity-set-name
Name of an extended community set.
inline-extcommunity-set
Inline extended community set.
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
This command replaced the extcommunity matches-any command.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the extcommunity rt matches-any command as a conditional expression within an if statement to match elements of an extended community set.
Note
A simple condition using the matches-any operator evaluates as true if at least one extended community in the route matches an extended community specification in the named or inline set. If no extended community in the route matches any of the specifications in the named or inline set, then this simple condition evaluates to false. Likewise, when there is no extended community at all in the route, the condition evaluates to false.
Matching an extended community in the route to a specification in a named or an inline set is intuitive. Because there is no use of wildcards with extended communities, a community in the route matches a specification in the set if the extended communities in the route and the inline set both encode the same 64-bit number. In inline sets, extended community specifications may be parameterized, in which case the relevant matching is done when the value of the parameter has been supplied.
Task ID
Examples
In the following example, an extended community set named my-extcommunity-set and a parameterized route-policy named my-extcommunity-set-example($tag,$ip) are defined. The extcommunity rt matches-any command is used in an if statement such that if at least one extended community in the route matches an extended community specification in the named set, then the local preference is set to 100. If there is no extended community in the route that matches any of the specifications in the named set, then the condition evaluates as false and the extended community is compared to the inline extended sets.
RP/0/RP0/CPU0:router(config)# extcommunity-set rt my-extcommunity-setRP/0/RP0/CPU0:router(config-ext)# 10:615,RP/0/RP0/CPU0:router(config-ext)# 10:6150,RP/0/RP0/CPU0:router(config-ext)# 15.15.15.15:15RP/0/RP0/CPU0:router(config-ext)# end-setRP/0/RP0/CPU0:router(config)# route-policy my-extcommunity-set-example($tag,$ip)RP/0/RP0/CPU0:router(config-rpl)# if extcommunity rt matches-any my-extcommunity-set thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 100RP/0/RP0/CPU0:router(config-rpl-if)# elseif extcommunity rt matches-any (10:20, 10:$tag) thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference 200RP/0/RP0/CPU0:router(config-rpl-elseif)# elseif extcommunity rt matches-any ($ip:$tag) thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference 300RP/0/RP0/CPU0:router(config-rpl-elseif)# elseif extcommunity rt matches-any (2.3.4.5:$tag) thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference 400RP/0/RP0/CPU0:router(config-rpl-elseif)# endifRP/0/RP0/CPU0:router(config-rpl)# end-policyRelated Commands
extcommunity rt matches-every
To match every element of a Border Gateway Protocol (BGP) route target (RT) extended community set, use the extcommunity rt matches-every command in route-policy configuration mode.
extcommunity rt matches-every {extcommunity-set-name | inline-extcommunity-set}
Syntax Description
extcommunity-set-name
Name of an extended community set.
inline-extcommunity-set
Inline extended community set.
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
This command replaced the extcommunity matches-every command.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the extcommunity rt matches-every command as a conditional expression within an if statement to match every element of an extended community set.
Note
A simple condition using the matches-every operator evaluates as true if every extended community value in the extended community attribute for the route matches at least one element of the extended community set or inline set. If no extended community in the route matches any of the specifications in the named or inline set, then this simple condition evaluates to false. Likewise, when there is no extended community at all in the route, the condition evaluates to false.
Matching an extended community in the route to a specification in a named or an inline set is intuitive. Because there is no use of wildcards with extended communities, a community in the route matches a specification in the set if they encode the same 64-bit number. In inline sets, extended community specifications may be parameterized, in which case the relevant matching is done when the value of the parameter has been supplied.
Task ID
Examples
In the following example, an extended community set named my-extcommunity-set and a parameterized route policy named extcommunity-matches-every-example ($as, $tag) are defined. The condition extcommunity rt matches-every is used in an if statement in this policy. If it evaluates to true, the local-preference value is set to 100. If it evaluates to false, the extended community is evaluated using an inline set. If that condition evaluates to true, the local-preference value is set to 200. If it evaluates to false, the local-preference value is set to 300.
RP/0/RP0/CPU0:router(config)# extcommunity-set rt my-extcommunity-setRP/0/RP0/CPU0:router(config-ext)# 10:20,RP/0/RP0/CPU0:router(config-ext)# 10:30,RP/0/RP0/CPU0:router(config-ext)# 10:40RP/0/RP0/CPU0:router(config-ext)# end-setRP/0/RP0/CPU0:router(config)# route-policy extcommunity-matches-every-example($as,$tag)RP/0/RP0/CPU0:router(config-rpl)# if extcommunity rt matches-every my-extcommunity-set thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 100RP/0/RP0/CPU0:router(config-rpl-if)# elseif extcommunity rt matches-every (10:20, 10:$tag, $as:30) thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference 200RP/0/RP0/CPU0:router(config-rpl-elseif)# elseifRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference 300RP/0/RP0/CPU0:router(config-rpl-elseif)# endifRP/0/RP0/CPU0:router(config-rpl)# end-policyRelated Commands
extcommunity-set cost
To define a cost extended community set, use the extcommunity-set cost command in global configuration mode. To remove the cost extended community set, use the no form of this command.
extcommunity-set cost name
no extcommunity-set cost name
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router.
This command replaced the extcommunity-set command.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the extcommunity-set cost command to define a cost community type extended community set for Enhanced Interior Gateway Routing Protocol (EIGRP).
An extended community set is analogous to a community set except that it contains extended community values instead of regular community values. Extended community values are 64-bit structured values. An extended community set also supports named forms and inline forms.
As with community sets, the inline form supports parameterization within parameterized policies. Either portion of the extended community value can be parameterized.
Every extended community set must contain at least one extended community value. Empty extended community sets are invalid and the policy configuration system rejects them.
Note
Examples
In the following example, a cost extended community set named extcomm-cost is defined:
RP/0/RP0/CPU0:router(config)# extcommunity-set cost extcomm-costRP/0/RP0/CPU0:router(config-ext)# IGP:90:914,RP/0/RP0/CPU0:router(config-ext)# Pre-Bestpath:91:915RP/0/RP0/CPU0:router(config-ext)# end-set
extcommunity-set rt
To define a route target (RT) extended community set, use the extcommunity-set rt command in global configuration mode. To remove the RT community set, use the no form of this command.
extcommunity-set rt name
no extcommunity-set rt name
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router.
This command replaced the extcommunity-set command.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the extcommunity-set rt command to define an RT extended community set for Enhanced Interior Gateway Routing Protocol (EIGRP).
An extcommunity set RT holds RT extended community values to match against the Border Gateway Protocol (BGP) RT extended community attribute. RT extended communities can be entered in either of the following formats:
•
•
Examples
In the following example, an RT extended community set named extcomm-rt is defined:
RP/0/RP0/CPU0:router(config)# extcommunity-set rt extcomm-rtRP/0/RP0/CPU0:router(config-ext)# 10002:666RP/0/RP0/CPU0:router(config-ext)# 10.0.0.2:666RP/0/RP0/CPU0:router(config-ext)# end-setextcommunity-set soo
To define a Border Gateway Protocol (BGP) Site-of-Origin (SoO) extended community set, use the extcommunity-set soo command in global configuration mode. To remove the SoO extended community set, use the no form of this command.
extcommunity-set soo name
no extcommunity-set soo name
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router.
This command replaced the extcommunity-set command.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the extcommunity-set soo command to define an SoO extended community set for Enhanced Interior Gateway Routing Protocol (EIGRP).
An extcommunity set soo holds SoO extended community values to match against the Border Gateway Protocol (BGP) SoO extended community attribute. SoO extended communities can be entered in either of the following formats:
•
•
Examples
In the following example, a SoO extended community set named extcomm-soo is defined:
RP/0/RP0/CPU0:router(config)# extcommunity-set soo extcomm-sooRP/0/RP0/CPU0:router(config-ext)# 66:60001,RP/0/RP0/CPU0:router(config-ext)# 77:70001,RP/0/RP0/CPU0:router(config-ext)# 88:80001,RP/0/RP0/CPU0:router(config-ext)# 99:90001,RP/0/RP0/CPU0:router(config-ext)# 100.100.100.1:153RP/0/RP0/CPU0:router(config-ext)# end-setextcommunity soo is-empty
To determine if a route has any Border Gateway Protocol (BGP) Site-of-Origin (SoO) extended community associated with it, use the extcommunity soo is-empty command in route-policy configuration mode.
extcommunity soo is-empty
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
This command replaced the extcommunity is-empty command.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the extcommunity soo is-empty command as a conditional expression within an if statement to learn if a BGP SoO route has extended community attributes associated with it.
Note
The is-empty operator takes no arguments and evaluates to true if the route has no extended community attributes associated with it.
Task ID
Examples
In the following example, if the extended community is empty, then the local preference is set to 100:
RP/0/RP0/CPU0:router(config)# route-policy extcommunity-is-empty-exampleRP/0/RP0/CPU0:router(config-rpl)# if extcommunity soo is-empty thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 100RP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)# end-policy
extcommunity soo matches-any
To match any element of a Border Gateway Protocol (BGP) Site-of-Origin (SoO) extended community set, use the extcommunity soo matches-any command in route-policy configuration mode.
extcommunity soo matches-any {extcommunity-set-name | inline-extcommunity-set}
Syntax Description
extcommunity-set-name
Name of an extended community set.
inline-extcommunity-set
Inline extended community set.
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
This command replaced the extcommunity matches-any command.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the extcommunity soo matches-any command as a conditional expression within an if statement to match elements of an extended community set.
Note
A simple condition using the matches-any operator evaluates as true if at least one extended community in the route matches an extended community specification in the named or inline set. If no extended community in the route matches any of the specifications in the named or inline set, then this simple condition evaluates to false. Likewise, when there is no extended community at all in the route, the condition evaluates to false.
Matching an extended community in the route to a specification in a named or an inline set is intuitive. Because there is no use of wildcards with extended communities, a community in the route matches a specification in the set if the community encodes the same 64-bit number. In inline sets, extended community specifications may be parameterized, in which case the relevant matching is done when the value of the parameter has been supplied.
Task ID
Examples
In the following example, an SoO extended community set named extcomm-soo and a parameterized route policy named my-extcommunity-set-example($tag,$ip) are defined.
The condition route policy named extcommunity soo matches-any is used in an if statement in this policy. If it evaluates to true, the local preference value is set to 100.
If it evaluates to false, the SoO extended community is evaluated using an inline set. If it evaluates to true, the local preference value is set to 200.
If it evaluates to false, the the SoO extended community is evaluated using a different inline set. If it evaluates to true, the local preference value is set to 300.
If it evaluates to false, the SoO extended community is evaluated using a different inline set. If it evaluates to true, the local preference value is set to 400.
RP/0/RP0/CPU0:router(config)# extcommunity-set soo extcomm-sooRP/0/RP0/CPU0:router(config-ext)# 66:60001,RP/0/RP0/CPU0:router(config-ext)# 77:70001,RP/0/RP0/CPU0:router(config-ext)# 88:80001,RP/0/RP0/CPU0:router(config-ext)# 99:90001,RP/0/RP0/CPU0:router(config-ext)# 100.100.100.1:153RP/0/RP0/CPU0:router(config-ext)# end-setRP/0/RP0/CPU0:router(config)# route-policy my-extcommunity-set-example($tag,$ip)RP/0/RP0/CPU0:router(config-rpl)# if extcommunity soo matches-any extcomm-soo thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 100RP/0/RP0/CPU0:router(config-rpl-if)# elseif extcommunity soo matches-any (10:20, 10:$tag) thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference 200RP/0/RP0/CPU0:router(config-rpl-elseif)# elseif extcommunity soo matches-any ($ip:$tag) thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference 300RP/0/RP0/CPU0:router(config-rpl-elseif)# elseif extcommunity soo matches-any (2.3.4.5:$tag) thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference 400RP/0/RP0/CPU0:router(config-rpl-elseif)# endifRP/0/RP0/CPU0:router(config-rpl)# end-policy
Related Commands
Matches any element of a BGP RT extended community set.
Matches every element of a BGP SoO extended community set.
extcommunity soo matches-every
To match every element of a Border Gateway Protocol (BGP) Site-of-Origin (SoO) extended community set, use the extcommunity soo matches-every command in route-policy configuration mode.
extcommunity soo matches-every {extcommunity-set-name | inline-extcommunity-set}
Syntax Description
extcommunity-set-name
Name of an extended community set.
inline-extcommunity-set
Inline extended community set.
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
This command replaced the extcommunity matches-every command.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the extcommunity soo matches-every command as a conditional expression within an if statement to match every element of an extended community set.
Note
A simple condition using the matches-every operator evaluates as true if every extended community value in the extended community attribute for the route matches at least one element of the extended community set or inline set. If no extended community in the route matches any of the specifications in the named or inline set, then this simple condition evaluates to false. Likewise, when there is no extended community at all in the route, the condition evaluates to false.
Matching an extended community in the route to a specification in a named or an inline set is intuitive. Because there is no use of wildcards with extended communities, a community in the route matches a specification in the set if they encode the same 64-bit number. In inline sets, extended community specifications may be parameterized, in which case the relevant matching is done when the value of the parameter has been supplied.
Examples
In the following example, an extended community set named my-extcomm-rt-set and a parameterized route policy named extcommunity-matches-every-example($as, $tag) are defined. The condition extcommunity soo matches-every is used in an if statement in this policy and if it evaluates to true, the local-preference value is set to 100. If it evaluates to false, the extended community is evaluated using an inline set. If that condition evaluates to true, the local-preference value is set to 200. If it evaluates to false, the local-preference value is set to 300.
RP/0/RP0/CPU0:router(config)# extcommunity-set soo my-extcomm-rt-setRP/0/RP0/CPU0:router(config-ext)# 10:20,RP/0/RP0/CPU0:router(config-ext)# 10:30,RP/0/RP0/CPU0:router(config-ext)# 10:40RP/0/RP0/CPU0:router(config-ext)# end-setRP/0/RP0/CPU0:router(config)# route-policy extcommunity-matches-every-example($as, $tag)RP/0/RP0/CPU0:router(config-rpl)# if extcommunity soo matches-every my-extcomm-rt-set thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 100RP/0/RP0/CPU0:router(config-rpl-if)# elseif extcommunity soo matches-every (10:20, 10:$tag, $as:30) thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference 200RP/0/RP0/CPU0:router(config-rpl-elseif)# elseRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference 300RP/0/RP0/CPU0:router(config-rpl-elseif)# endifRP/0/RP0/CPU0:router(config-rpl)# end-policyRelated Commands
if
To decide which actions or dispositions should be taken for a given route, use the if command in route-policy configuration mode.
if conditional-expression then action-statement [action-statement] [elseif conditional-expression then action-statement [action-statement]] [else action-statement [action-statement]] endif
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The if command uses a conditional expression to decide which actions or dispositions should be taken for a given route. Table 1 lists the conditional expressions.
An action statement is a sequence of operations that modify a route, most of which are distinguished by the set keyword. In a route policy, these operations can be grouped. Table 2 lists the action statements.
Task ID
Examples
In the following example, any route whose AS path is in the set as-path-set-1 is dropped:
RP/0/RP0/CPU0:router(config-rpl)# if as-path in as-path-set-1 thenRP/0/RP0/CPU0:router(config-rpl-if)# dropRP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)#The contents of the then clause may be an arbitrary sequence of action statements.
The following example shows an if statement with two action statements:
RP/0/RP0/CPU0:router(config-rpl)# if origin is igp thenRP/0/RP0/CPU0:router(config-rpl-if)# set med 42RP/0/RP0/CPU0:router(config-rpl-if)# prepend as-path 73 5RP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)#The if command also permits an else clause to be executed if the expression is false, as follows:
RP/0/RP0/CPU0:router(config-rpl)# if med eq 200 thenRP/0/RP0/CPU0:router(config-rpl-if)# set community (12:34) additiveRP/0/RP0/CPU0:router(config-rpl-if)# elseRP/0/RP0/CPU0:router(config-rpl-else)# set community (12:56) additiveRP/0/RP0/CPU0:router(config-rpl-else)# endifRP/0/RP0/CPU0:router(config-rpl)#The routing policy language (RPL) also provides syntax using the elseif command to string together a sequence of tests, as shown in the following example:
RP/0/RP0/CPU0:router(config-rpl)# if med eq 150 thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 10RP/0/RP0/CPU0:router(config-rpl-if)# elseif med eq 200 thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference 60RP/0/RP0/CPU0:router(config-rpl-elseif)# elseif med eq 250 thenRP/0/RP0/CPU0:router(config-rpl-elseif)# set local-preference 110RP/0/RP0/CPU0:router(config-rpl-elseif)# elseRP/0/RP0/CPU0:router(config-rpl-else)# set local-preference 0RP/0/RP0/CPU0:router(config-rpl-else)# endifRP/0/RP0/CPU0:router(config-rpl)#The statements within an if statement may themselves be if statements, as shown in this example:
RP/0/RP0/CPU0:router(config-rpl)# if community matches-any (12:34, 56:78) thenRP/0/RP0/CPU0:router(config-rpl-if)# if med eq 150 thenRP/0/RP0/CPU0:router(config-rpl-if)# dropRP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 100RP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)#The policy configuration shown sets the value of the local preference attribute to 100 on any route that has a community value of 12:34 or 56:78 associated with it. However, if any of these routes has a Multi Exit Descriminator (MED) value of 150, then each route with both the community value of 12:34 or 56:78 and a MED of 150 is dropped.
med
To compare the Multi Exit Discriminator (MED) to an integer value or a parameterized value, use the med command in route-policy configuration mode.
med {eq | is | ge | le} {number | parameter}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the med command as a conditional expression within an if statement to compare the MED to an integer value or a parameterized value.
Note
The MED is a 32-bit unsigned integer. The eq operation compares the MED to either a static value or a parameterized value passed to a parameterized policy for equality with that value. A greater than or equal to comparison can also be done with the ge operator, and a less than or equal to comparison can be performed using the le operator.
Task ID
Examples
The following example shows that if the med commands match, the local preference is set to 100:
RP/0/RP0/CPU0:router(config-rpl)# if med eq 10 thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 100RP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)#next-hop in
To compare the next hop associated with the route to data contained in either an inline or a named prefix set, use the next-hop in command in route-policy configuration mode.
next-hop in {prefix-set-name | inline-prefix-set}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the next-hop in command as a conditional expression within an if statement to compare the next hop associated with the route to data contained in either an inline or a named prefix set. The result is true if any value in the prefix set matches the next hop of the route. A comparison that refers to a named prefix set that has no elements in it returns false.
Note
The next hop is an IPv4 address entered as a dotted-decimal or an IPv6 address entered as a colon-separated hexadecimal.
Task ID
Examples
The following example shows that if the next-hop in commands match, the local preference is set to 100
RP/0/RP0/CPU0:router(config-rpl)# if next-hop in some-prefix-set thenRP/0/RP0/CPU0:router(config-rpl-if)# if next-hop in (10.0.0.5, fe80::230/64) thenRP/0/RP0/CPU0:router(config-rpl-if)# set local-preference 0RP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)#orf prefix in
To configure an outbound route filter (ORF), use the orf prefix in command in route-policy configuration mode.
orf prefix in {prefix-set-name | inline-prefix-set}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use this command to match a prefix in a prefix set or an inline prefix set.
Examples
In the following example, the prefix set orfpreset1 and the route policy named orfpolicy are defined. Next, the orfpolicy is applied to the neighbor orf attach point.
If the prefix of the route matches any of the prefixes specified in orfpreset1 (211.105.1.0/24, 211.105.5.0/24, 211.105.11.0/24), then the prefix is dropped. If the prefix matches in(211.105.3.0/24, 211.105.7.0/24, 211.105.13.0/24), then the prefix is accepted. In addition to this inbound filtering, BGP sends these prefix entries to the upstream neighbor indicating a permit or deny so that the neighbor can make the same filter updates.
RP/0/RP0/CPU0:router(config)# prefix-set orfpreset1RP/0/RP0/CPU0:router(config-pfx)# 211.105.1.0/24,RP/0/RP0/CPU0:router(config-pfx)# 211.105.5.0/24,RP/0/RP0/CPU0:router(config-pfx)# 211.105.11.0/24RP/0/RP0/CPU0:router(config-pfx)# end-set!!RP/0/RP0/CPU0:router(config)# route-policy orfpolicyRP/0/RP0/CPU0:router(config-rpl)# if orf prefix in orfpreset1 thenRP/0/RP0/CPU0:router(config-rpl-if)# dropRP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)# if orf prefix in (211.105.3.0/24, 211.105.7.0/24, 211.105.13.0/24) thenRP/0/RP0/CPU0:router(config-rpl-if)# passRP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)# end-policy!!RP/0/RP0/CPU0:router(config)# router bgp 2RP/0/RP0/CPU0:router(config-bgp)# neighbor 1.1.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 3RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# orf route-policy orfpolicyorigin is
To match a specific origin type, use the origin is command in route-policy configuration mode.
origin is {igp | egp | incomplete | parameter}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the origin is command as a conditional expression within an if statement to test the value of the origin attribute.
Note
The origin of a BGP route is an enumeration; it is igp, egp, or incomplete.
This command can be parameterized.
Task ID
Examples
In the following example, the origin is tested within an if statement to learn if it is either igp or egp:
RP/0/RP0/CPU0:router(config-rpl)# if origin is igp or origin is egp thenIn the following example, a parameter is used to match a specific origin type:
RP/0/RP0/CPU0:router(config)# route-policy bar($origin)RP/0/RP0/CPU0:router(config-rpl)# if origin is $origin thenRP/0/RP0/CPU0:router(config-rpl-if)# set med 20RP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)#pass
To pass a route for further processing, use the pass command in route-policy configuration mode.
pass
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the pass command to signify that even though this route has not been modified, the user wants to continue executing in this policy block.
Note
When a policy block has finished executing, any route that has been modified in this policy block or has received a pass disposition in this policy block passes the policy and execution finishes for that policy. If this policy block is applied from within another policy block and the route is either passed or modified, then execution continues in the policy block that applied this policy block.
Task ID
Examples
The following example shows how to accept the route unconditionally without modifying it:
RP/0/RP0/CPU0:router(config-rpl)# passThis example accepts the route unconditionally, without modifying it, if the destination is in prefix-set permitted:
RP/0/RP0/CPU0:router(config-rpl)# if destination in permitted thenRP/0/RP0/CPU0:router(config-rpl-if)# passRP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)#prefix-set
To enter prefix set configuration mode and define a prefix set, use the prefix-set command in global configuration mode. To remove a named prefix set, use the no form of this command.
prefix-set name
no prefix-set name
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the prefix-set command to enter prefix set configuration mode and define a prefix set.
A prefix set is a comma-separated list of prefix match specifications. It holds IPv4 or IPv6 prefix match specifications, each of which has four parts: an address, a mask length, a minimum matching length, and a maximum matching length. The address is required, but the other three parts are optional. The address is a standard four-part, dotted-decimal numeric IPv4 address or a colon-separated hexadecimal IPv6 address. The mask length, if present, is a nonnegative decimal integer in the range from 0 to 32 for IPv4 prefixes or 0 to 128 for IPv6 prefixes following the address and separated from it by a slash. The optional minimum matching length follows the address and optional mask length and is expressed as the keyword ge (mnemonic for greater than or equal to), followed by a nonnegative decimal integer in the range from 0 to 32 for IPv4 or 0 to 128 for IPv6. The optional maximum matching length follows the rest and is expressed by the keyword le (mnemonic for less than or equal to), followed by yet another nonnegative decimal integer in the range from 0 to 32 for IPv4 or 0 to 128 for IPv6. A syntactic shortcut for specifying an exact length for prefixes to match is the eq keyword, mnemonic for equal to.
If a prefix match specification has no mask length, then the default mask length is 32 for IPv4 or 128 for IPv6. The default minimum matching length is the mask length. If a minimum matching length is specified, then the default maximum matching length must be less than 32 for IPv4 prefixes or 128 for IPv6 prefixes. Otherwise, if neither a minimum nor maximum length is specified, the default maximum length is the mask length.
Task ID
Examples
The following example shows a prefix set named legal-ipv4-prefix-examples:
RP/0/RP0/CPU0:router(config)# prefix-set legal-ipv4-prefix-examplesRP/0/RP0/CPU0:router(config-pfx)# 10.0.1.1,RP/0/RP0/CPU0:router(config-pfx)# 10.0.2.0/24,RP/0/RP0/CPU0:router(config-pfx)# 10.0.3.0/24 ge 28,RP/0/RP0/CPU0:router(config-pfx)# 10.0.4.0/24 le 28,RP/0/RP0/CPU0:router(config-pfx)# 10.0.5.0/24 ge 26 le 30,RP/0/RP0/CPU0:router(config-pfx)# 10.0.6.0/24 eq 28RP/0/RP0/CPU0:router(config-pfx)# end-setThe first element of the prefix set matches only one possible value, 10.0.1.1/32 or the host address 10.0.1.1. The second element matches only one possible value, 10.0.2.0/24. The third element matches a range of prefix values, from 10.0.3.0/28 to 10.0.3.255/32. The fourth element matches a range of values, from 10.0.4.0/24 to 10.0.4.240/28. The fifth element matches prefixes in the range from 10.0.5.0/26 to 10.0.5.252/30. The sixth element matches any prefix of length 28 in the range from 10.0.6.0/28 through 10.0.6.240/28.
The following prefix set consists entirely of invalid prefix match specifications:
RP/0/RP0/CPU0:router(config)# prefix-set INVALID-PREFIX-EXAMPLESRP/0/RP0/CPU0:router(config-pfx)# 10.1.1.1 ge 16,RP/0/RP0/CPU0:router(config-pfx)# 10.1.2.1 le 16,RP/0/RP0/CPU0:router(config-pfx)# 10.1.3.0/24 le 23,RP/0/RP0/CPU0:router(config-pfx)# 10.1.4.0/24 ge 33,RP/0/RP0/CPU0:router(config-pfx)# 10.1.5.0/25 ge 29 le 28RP/0/RP0/CPU0:router(config-pfx)# end-setNeither the minimum length nor the maximum length is legal without a mask length. The maximum length must be at least the mask length. The minimum length must be less than 32, the maximum length of an IPv4 prefix. The maximum length must be equal to or greater than the minimum length.
The following example shows a valid IPv6 prefix set named legal-ipv6-prefix-examples:
RP/0/RP0/CPU0:router(config)# prefix-set legal-ipv6-prefix-examplesRP/0/RP0/CPU0:router(config-pfx)# 2001:0:0:1::/64,RP/0/RP0/CPU0:router(config-pfx)# 2001:0:0:2::/64,RP/0/RP0/CPU0:router(config-pfx)# 2001:0:0:3::/64,RP/0/RP0/CPU0:router(config-pfx)# 2001:0:0:4::/64RP/0/RP0/CPU0:router(config-pfx)# end-setprepend as-path
To prepend the AS path with additional autonomous system numbers, use the prepend as-path command in route-policy configuration mode.
prepend as-path {as-number | parameter} [number | parameter]
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the prepend as-path command to prepend the AS path with additional autonomous system numbers.
Note
This command can take one or two arguments. The first argument (either a number or parameter) is the autonomous system number to prepend to the path. The optional second argument (either a number or parameter) is the number of times the autonomous system number should be prepended.
Task ID
Examples
The following example shows how to prepend the autonomous system number 666 to the AS path three times:
RP/0/RP0/CPU0:router(config-rpl)# prepend as-path 666 3
The following example shows how to prepend the autonomous system number 666 to the AS path one time:
RP/0/RP0/CPU0:router(config-rpl)# prepend as-path 666protocol
To check the protocol that installs the route, use the protocol command in route-policy configuration mode.
protocol {in ( protocol-set ) | is protocol-name}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the protocol command as a conditional expression within an if statement to specify a protocol to install a route.
Note
Task ID
Examples
The following example shows how to use the protocol command as a conditional expression within if statements:
RP/0/RP0/CPU0:router(config)# route-policy rip1RP/0/RP0/CPU0:router(config-rpl)# if protocol in (connected, static) thenRP/0/RP0/CPU0:router(config-rpl-if)# add rip-metric 2RP/0/RP0/CPU0:router(config-rpl-if)# elseif protocol is bgp 1 thenRP/0/RP0/CPU0:router(config-rpl-elseif)# add rip-metric 3RP/0/RP0/CPU0:router(config-rpl-elseif)# elseif protocol is ospf 2 thenRP/0/RP0/CPU0:router(config-rpl-elseif)# add rip-metric 4RP/0/RP0/CPU0:router(config-rpl-elseif)# elseRP/0/RP0/CPU0:router(config-rpl-else)# add rip-metric 5RP/0/RP0/CPU0:router(config-rpl-else)# endifRP/0/RP0/CPU0:router(config-rpl)# end-policyRP/0/RP0/CPU0:router(config)# router ripRP/0/RP0/CPU0:router(config-rip)# interface GigabitEthernet0/1/0/1RP/0/RP0/CPU0:router(config-rip-if)# route-policy rip1 outrd in
To compare the route distinguisher (RD) associated with the route to RDs contained in either a named or an inline RD set, use the rd in command in route-policy configuration mode.
rd in {rd-set-name | inline-rd-set}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the rd in command as a conditional expression within an if statement to match a destination entry in a named prefix set or inline prefix set.
Note
This command takes either a named RD set or an inline RD set value as an argument. The condition returns true if the destination entry matches any entry in the RD set or inline RD set. An attempt to match an RD using an RD set that is defined but contains no elements returns false.
Task ID
Examples
The following example shows the rd in command with an inline RD set value as an argument:
RP/0/RP0/CPU0:router(config)# route-policyRP/0/RP0/CPU0:router(config-rpl)# if rd in (128.1.0.0/16:100) thenRP/0/RP0/CPU0:router(config-rpl-if)# passRP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)# end-policyrd-set
To define a route distinguisher (RD) set and enter RD configuration mode, use the rd-set command in global configuration mode.
rd-set name
no rd-set name
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the rd-set command to create a set with RD elements and enter RD configuration mode. An RD set is a 64-bit value prepended to an IPv4 address to create a globally unique Border Gateway Protocol (BGP) VPN IPv4 address.
You can define RD values with the following commands:
•
•
•
•
•
•
Task ID
Examples
The following example shows how to create an RD set called my_rd_set:
RP/0/RP0/CPU0:router(config)# rd-set my_rd_setRP/0/RP0/CPU0:router(config-rd)# 172.16.0.0/16:*,RP/0/RP0/CPU0:router(config-rd)# 172.17.0.0/16:100,RP/0/RP0/CPU0:router(config-rd)# 192:*,RP/0/RP0/CPU0:router(config-rd)# 192:100RP/0/RP0/CPU0:router(config-rd)# end-setrib-has-route
To check if there is a Routing Information Base (RIB) in a route, use the rib-has-route command in route-policy configuration mode.
rib-has-route in name
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
This command was supported on the Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If routes are active, then they are advertised. Routes are considered active if they are already installed in the Routing Information Base (RIB) by the Border Gateway Protocol (BGP).
Use the rib-has-route command as a conditional expression within an if statement to check if there is an active route with a specific prefix set contained in the RIB. If the statement reveals an active route that meets that criteria, additional actions are executed.
For a list of all conditional expressions available within an if statement, see the if command.
Task ID
Examples
In the following example, an if statement is used to learn if a route with a prefix set named pf1 is in the RIB:
RP/0/RP0/CPU0:router(config-rpl)# if rib-has-route in pf1 thenRP/0/RP0/CPU0:router(config-rpl-if)# passRP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)#route-has-label
To check if there is an MPLS label in a route during redistribution, use the route-has-label command in route-policy configuration mode.
route-has-label
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the route-has-label command as a conditional expression within an if statement to check if there is a RIB in a route.
For a list of all conditional expressions available within an if statement, see the if command.
Task ID
Examples
In the following example, an if statement learns if an MPLS label is present in a route:
RP/0/RP0/CPU0:router(config-rpl)# if route-has-label thenRP/0/RP0/CPU0:router(config-rpl-if)# passRP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)#route-policy (RPL)
To define a route policy and enter route-policy configuration mode, use the route-policy command in global configuration mode. To remove a policy definition, use the no form of this command.
route-policy name [parameter1, parameter2, . . . , parameterN]
no route-policy name [parameter1, parameter2, . . . , parameterN]
Syntax Description
name
Name of a route policy.
parameter
(Optional) Parameter name. The parameter name must be preceded with a "$."
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the route-policy command to define a route policy and enter route-policy configuration mode.
Policy definitions create named bundles of policy statements. A policy definition consists of the route-policy command followed by a name, a group of policy statements, and the end-policy command.
The policy name serves as a handle for binding the policy to protocols.
Task ID
Examples
The following example shows a simple policy named drop-everything that drops any route it encounters:
RP/0/RP0/CPU0:router(config)# route-policy drop-everythingRP/0/RP0/CPU0:router(config-rpl)# dropRP/0/RP0/CPU0:router(config-rpl)# end-policyPolicies may also refer to other policies such that common blocks of policy can be reused. This reference to other policies is accomplished by using the apply command. The following is a simple example:
RP/0/RP0/CPU0:router(config)# route-policy drop-as-1234RP/0/RP0/CPU0:router(config-rpl)# if as-path passes-through '1234' thenRP/0/RP0/CPU0:router(config-rpl-if)# apply check-communitiesRP/0/RP0/CPU0:router(config-rpl-if)# elseRP/0/RP0/CPU0:router(config-rpl-else)# passRP/0/RP0/CPU0:router(config-rpl-else)# endifRP/0/RP0/CPU0:router(config-rpl)# end-policyThe apply command indicates that the policy check-communities should be executed if the route under consideration passed through autonomous system 1234 before it was received. If so, the communities of the route are checked, and based on the findings the route may be accepted unmodified, accepted with changes, or dropped.
Related Commands
route-type is
To match route types when redistribution is being performed into Border Gateway Protocol (BGP), Open Shortest Path First (OSPF), or Integrated Intermediate System-to-Intermediate System (IS-IS), use the route-type is command in route-policy configuration mode.
route-type is {local | interarea | internal | type-1 | type-2 | level-l | level-2 | level-1-2 | parameter}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the route-type is command as a conditional expression within an if statement to compare route types when redistribution is being performed into BGP, OSPF, or IS-IS.
Note
The valid keywords are local, internal, type-1, type-2, level-1, level-2, and level-1-2. A parameterized value that fills in one of these values may also be used. The local value is used to match locally generated BGP routes. The internal value is used to match OSPF intra- and interarea routes. The type-1 and type-2 values are used to match Type 1 and Type 2 OSPF external routes. The level-1, level-2, and level-1-2 values are used to match IS-IS routes of those respective types.
Because the route type is a matching operator, it appears in conditional clauses of if and then statements.
Task ID
Examples
In the following example, non-local routes are dropped:
RP/0/RP0/CPU0:router(config)# route-policy policy_ARP/0/RP0/CPU0:router(config-rpl)# if route-type is local thenRP/0/RP0/CPU0:router(config-rpl-if)# passRP/0/RP0/CPU0:router(config-rpl-if)# elseRP/0/RP0/CPU0:router(config-rpl-else)# dropRP/0/RP0/CPU0:router(config-rpl-if)# endifRP/0/RP0/CPU0:router(config-rpl)# end-policyrpl editor
To set the default routing policy language (RPL) editor, use the rpl editor command in in global configuration mode.
rpl editor {emacs | vim}
Syntax Description
Defaults
Emacs editor
Command Modes
Global configuration
Command History
Release 3.3.0
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
In the following example, the default RPL editor is set to EMACS:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rpl emacsRP/0/RP0/CPU0:router(config)#In the following example, the default RPL editor is set to VIM:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rpl vimRP/0/RP0/CPU0:router(config)#rpl maximum
To configure system limits on the routing policy subsystem, use the rpl maximum command in global configuration mode.
rpl maximum {{lines | policies} number}
Syntax Description
lines number
Configures the number of lines of configuration limit. Range is from 1 to 131072.
policies number
Configures the number of policies limit. Range is from 1 to 5000.
Defaults
lines number: 65536
policies numbers: 3500Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the rpl maximum command to configure system limits on the routing policy subsystem. As such, rpl maximum configuration lines do not appear as statements within a routing policy. This command places resource limits on the routing policy subsystem. Use the rpl maximum command to configure the maximum number of lines of configuration and number of policies.
The number of lines of configuration includes the beginning and ending statements, for example, route-policy and end-policy. Each line of configuration for sets is also counted.
A line of configuration is counted only once; it is not counted each time it is used. Similarly, any multiple use of policy in an apply statement counts only as one policy.
A user can change the default values for lines and policies but cannot exceed the maximum value, nor can the value for lines and policies be configured lower than the number of lines or policies that are currently configured.
Task ID
Examples
In the following example, the maximum number of RPL system limits are modified:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rpl maximum lines 50RP/0/RP0/CPU0:router(config)# rpl maximum policies 6RP/0/RP0/CPU0:router(config)# rpl maximum elseifs 12RP/0/RP0/CPU0:router(config)# rpl maximum ifconditions 12RP/0/RP0/CPU0:router(config)# rpl maximum ifdepth 30Related Commands
set community
To set the Border Gateway Protocol (BGP) community attributes in a route, use the set community command in route-policy configuration mode.
set community {community-set-name | inline-community-set} [additive]
Syntax Description
community-set-name
Community set name.
inline-community-set
Inline community set.
additive
(Optional) Adds communities to communities in the route.
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the set community command to set the BGP community attribute.
Note
Communities are 32-bit values carried in BGP routes. Each route may have zero or more communities in an unordered list.
Use this command to replace the communities in a route or add to them using the optional additive keyword.
As with the other community forms that support inline sets, either or both 16-bit portions of the community can be parameterized. Likewise, the names of the well-known communities internet, no-advertise, no-export, and local-AS can also be used.
Without the additive keyword, any existing communities (other than the well-known communities) are removed and replaced with the given communities. The additive keyword specifies that all communities already present in the route be maintained and the list of communities be added to them.
Task ID
Examples
The following are incomplete configuration examples using the set community command:
RP/0/RP0/CPU0:router(config-rpl)# set community (10:24)RP/0/RP0/CPU0:router(config-rpl)# set community (10:24, $as:24, $as:$tag)RP/0/RP0/CPU0:router(config-rpl)# set community (10:24, internet) additiveRP/0/RP0/CPU0:router(config-rpl)# set community (10:24, $as:24) additiveset cost
To set the cost attribute for a BGP extended community, use the set cost command in route-policy configuration mode.
set cost {number | parameter}
Syntax Description
number
Value assigned to a 32-bit unsigned integer. Range is from 0 to 4294967295.
parameter
Parameter name. The parameter name must be preceded with a "$."
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Release 2.0
This command was introduced on the Cisco CRS-1.
Release 3.0
No modification.
Release 3.2
This command was supported on the Cisco XR 12000 Series Router.
Release 3.3
In previous software releases, this command set the Open Shortest Path First (OSPF), cost attribute. Use the set ospf-metric command to set the OSPF cost attribute.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
In the following example, the cost attribute for BGP extended community is set to 10:
RP/0/RP0/CPU0:router(config-rpl)# set cost 10set dampening
To configure Border Gateway Protocol (BGP) route dampening, use the set dampening command in route-policy configuration mode.
set dampening {halflife minutes | max-suppress minutes | reuse seconds | suppress penalty-units} others default
Syntax Description
Defaults
half-life: 15 minutes
max-suppress: 60 minutes (four times the half-life)
reuse: 750 seconds
suppress: 2000 penalty unitsCommand Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The BGP protocol supports route dampening using an exponential backoff algorithm. The algorithm is controlled by setting the four supported BGP values: half-life, max-suppress, reuse, and suppress. Use the set dampening command to configure BGP route dampening.
Note
A value for at least one of the four keywords must be set. If the set dampening command defines values for three or fewer of the supported keywords, then the configuration must end with the others default, which indicates that any keyword value not defined in the command is set to its default value.
The keywords may appear in the command in any order.
Task ID
Examples
In the following examples, the half-life is set to 20 minutes and the maximum suppress time is set to
90 minutes. Each command must end with others default because three or fewer keywords are defined.RP/0/RP0/CPU0:router(config-rpl)# set dampening halflife 20 others defaultRP/0/RP0/CPU0:router(config-rpl)# set dampening max-suppress 90 others defaultIn this example, all four keywords are defined, which means the command does not use others default.
RP/0/RP0/CPU0:router(config-rpl)# set dampening halflife 15 max-suppress 60 reuse 750 suppress 2000The following command is invalid because it is missing others default.
RP/0/RP0/CPU0:router(config-rpl)# set dampening reuse 700set eigrp-metric
To set Enhanced Interior Gateway Routing Protocol (EIGRP) metric attributes, use the set eigrp-metric command in route-policy configuration mode.
set eigrp-metric bandwidth delay reliability loading mtu
Syntax Description
Defaults
None
Command Modes
Route-policy configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
You can use the add command to further offset an existing EIGRP metric value.
Task ID
Examples
In the following example, the EIGRP metrics are adjusted for route policy policy_1:
RP/0/RP0/CPU0:router(config)# route-policy policy_1RP/0/RP0/CPU0:router(config-rpl)# set eigrp-metric 1400 120 250 100 1500RP/0/RP0/CPU0:router(config-rpl)# end-policyRelated Commands
set extcommunity cost
To set the Border Gateway Protocol (BGP) extended community attribute for cost, use the set extcommunity cost command in route-policy configuration mode.
set extcommunity cost {cost-extcommunity-set-name | cost-inline-extcommunity-set} [additive]
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
This command replaced the set extcommunity command.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the set extcommunity cost command to either replace the extended communities on the route or add to them using the optional additive keyword.
Note
As with the other extended community forms that support inline sets, either or both portions of the community can be parameterized. Similarly to regular communities, the additive keyword can be used to signify adding these extended communities to those that are already present, as opposed to replacing them.
Task ID
Examples
The following are incomplete configuration examples using the set extcommunity cost command:
RP/0/RP0/CPU0:router(config-rpl)# set extcommunity cost (10:24)RP/0/RP0/CPU0:router(config-rpl)# set extcommunity cost (10:24, $as:24, $as:$tag)RP/0/RP0/CPU0:router(config-rpl)# set extcommunity cost (10:24, internet) additiveRP/0/RP0/CPU0:router(config-rpl)# set extcommunity cost (10:24, $as:24) additiveWithout the additive keyword, any existing extended communities for cost (other than the well-known communities) are removed and replaced with the given communities. The additive keyword specifies that all extended communities for cost already present in the route be maintained and the list of extended communities be added to them.
set extcommunity rt
To set the Border Gateway Protocol (BGP) extended community attribute for a route target (RT), use the set extcommunity rt command in route-policy configuration mode.
set extcommunity rt {rt-extcommunity-set-name | rt-inline-extcommunity-set} [additive]
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
This command replaced the set extcommunity command.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the set extcommunity rt command to either replace the extended communities on the route or add to them using the optional additive keyword.
Note
As with the other extended community forms that support inline sets, either or both portions of the community can be parameterized. Similarly to regular communities, the additive keyword can be used to signify adding these extended communities to those that are already present, as opposed to replacing them.
Task ID
Examples
The following are incomplete configuration examples using the set extcommunity rt command:
RP/0/RP0/CPU0:router(config-rpl)# set extcommunity rt (10:24)RP/0/RP0/CPU0:router(config-rpl)# set extcommunity rt (10:24, $as:24, $as:$tag)RP/0/RP0/CPU0:router(config-rpl)# set extcommunity rt (10:24, internet) additiveRP/0/RP0/CPU0:router(config-rpl)# set extcommunity rt (10:24, $as:24) additiveWithout the additive keyword, any existing extended communities for cost (other than the well-known communities) are removed and replaced with the given communities. The additive keyword specifies that all extended communities for cost already present in the route be maintained and the list of extended communities be added to them.
set isis-metric
To set the Intermediate System-to-Intermediate System (IS-IS) metric attribute value, use the set is-is metric command in route-policy configuration mode.
set isis-metric {number | parameter}
Syntax Description
number
24-bit integer number. Range is from 0 to 16777215.
parameter
Parameter name. The parameter name must be preceded with a "$."
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the set isis-metric command to set the IS-IS metric attribute value for routes that are redistributed into IS-IS.
Task ID
Examples
In the following example, the IS-IS metric attribute value is set to 1000:
RP/0/RP0/CPU0:router(config)# route-policy policy_1RP/0/RP0/CPU0:router(config-rpl)# set isis-metric 1000RP/0/RP0/CPU0:router(config-rpl)# end-policyset label
To set the Border Gateway Protocol (BGP) label attribute value, use the set label command in route-policy configuration mode.
set label {explicit-null | implicit-null | parameter}
Syntax Description
explicit-null
Sets the label to a well-known explicit value.
implicit-null
Sets the label to a well-known implicit value.
parameter
Parameter name. The parameter name must be preceded with a "$."
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Release 3.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the set label command to set the BGP label for VPN IPv4 routes. During inter-AS operation, the ASBR sends some of its own loopbacks to other its peers and labels them either implicit null or explicit null.
Examples
The following are incomplete configuration examples using the set label command:
RP/0/RP0/CPU0:router(config-rpl)# set label implicit-nullRP/0/RP0/CPU0:router(config-rpl)# set label explicit-nullRP/0/RP0/CPU0:router(config-rpl)# set label $labelset level
To configure the integrated Intermediate System-to-Intermediate System (IS-IS) level in which redistributed routes should be sent, use the set level command in route-policy configuration mode.
set level {level-1 | level-2 | level-1-2 | parameter}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the IS-IS set level command to configure the IS-IS level in which redistributed routes should be sent.
Note
This command supports parameterization of the level keyword.
Task ID
Examples
In the following example, the level is set to Level 1:
RP/0/RP0/CPU0:router(config-rpl)# set level level-1set local-preference
To set the Border Gateway Protocol (BGP) local preference attribute in a route, use the set local-preference command in route-policy configuration mode.
set local-preference {number | parameter}
Syntax Description
number
Value assigned to a 32-bit unsigned integer. Range is 0 to 4294967295.
parameter
Parameter name. The parameter name must be preceded with a "$."
Defaults
Default value is 100.
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the set local-preference command to specify a preference value for the autonomous system path. Local preference is a nontransitive (does not cross autonomous system boundaries) attribute and is the second metric considered in the BGP best path calculation (the highest local preference is chosen). Weight is the first metric evaluated for best path, but it is local to the router and propagates only to iBGP peers. See the Implementing BGP on Cisco IOS XR Software module of the Cisco IOS XR Routing Configuration Guide for information on the BGP best path calculation.
Note
The local preference is a 32-bit unsigned integer.
Task ID
Examples
In the following example, the local preference value is set to 10:RP/0/RP0/CPU0:router(config-rpl)# set local-preference 10set med
To set the Border Gateway Protocol (BGP) Multi Exit Discriminator (MED) attribute, use the set med command in route-policy configuration mode.
set med {number | parameter | igp-cost | {+ | -} {number | parameter} | max-reachable}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the set med command to set the MED value, which is a 32-bit unsigned integer.
Note
This command can take the following as argument values: an integer, a parameter, the igp-cost keyword, or a mathematical operator (either plus or minus) followed by an integer or a parameter.
The plus or minus variants allow the user to set the MED to the MED plus or minus a static offset. The variants that allow a user to add or subtract offsets to the MED value are also range checked for underflow or overflow. If the value underflows as a result of subtraction, then the MED value is set to zero. If the value overflows, the value is set to 4294967295, which is a special value for MED.
Task ID
Examples
The following two examples show how to set the MED to a value that is either specified directly (using the integer 156) or passed to the policy as a parameter:
RP/0/RP0/CPU0:router(config-rpl)# set med 156RP/0/RP0/CPU0:router(config-rpl)# set med $med_paramThe following example shows how to instruct BGP to automatically set the MED value to the cost of the IGP route that resolves the next hop of the BGP route:
RP/0/RP0/CPU0:router(config-rpl)# set med igp-costset metric-type (IS-IS)
To configure the integrated Intermediate System-to-Intermediate System (IS-IS) metric type, use the set metric-type command in route-policy configuration mode.
set metric-type {internal | external | parameter}
Syntax Description
internal
Sets metric type to internal.
external
Sets the metric type to external.
parameter
Parameter name. The parameter name must be preceded with a "$."
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the IS-IS set metric-type command to control whether IS-IS treats the metric as an internal or external metric.
Note
This command does not support parameterization.
Task ID
Examples
In the following example, the IS-IS metric type is set to internal:
RP/0/RP0/CPU0:router(config-rpl)# set metric-type internalset metric-type (OSPF)
To control how Open Shortest Path First (OSPF) computes the cost for a route, use the set metric-type command in route-policy configuration mode.
set metric-type {type-1 | type-2}
Syntax Description
type-1
Uses the cost set on the route plus the topology-related costs in the calculation for Type 1 metrics.
type-2
Uses only the cost set on the route in the calculation for Type 2 metrics.
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the OSPF set metric-type command to control whether OSPF treats the cost as a Type 1 or Type 2 metric.
Note
The value of Type 1 or Type 2 controls how OSPF computes the cost for this route. For Type 2 metrics, only the cost set on the route is used. For Type 1 metrics, the cost set on the route plus the topology- related costs are used in the calculation.
This command does not support parameterization.
Task ID
Examples
In the following example, the OSPF metric type is set to Type 1:
RP/0/RP0/CPU0:router(config-rpl)# set metric-type type-1set next-hop
To replace the next hop associated with a given route, use the set next-hop command in route-policy configuration mode.
set next-hop {ipv4-address | ipv6-address | peer-address | parameter}
Syntax Description
Defaults
No default behavior or values
Command Modes
Route-policy configuration
Command History
