Parameterization At Attach Points; Global Parameterization - Cisco ASR 9000 Series Configuration Manual
Aggregation services router
Hide thumbs
Also See for ASR 9000 Series:
- Command reference manual (1138 pages) ,
- Routing configuration manual (702 pages) ,
- Reference manual (696 pages)
Table of Contents
Advertisement
Implementing Routing Policy
The effect of the origin-10 policy is that it adds the community 1234:10 to all routes that pass through this
policy and have an AS path indicating the route originated from autonomous system 10. The origin-20 policy
is similar except that it adds to community 1234:20 for routes originating from autonomous system 20.
Parameterization at Attach Points
In addition to supporting parameterization using the apply statement described in the
page
480, policies can also be defined that allow for parameterization the attributes at attach points.
Parameterization is supported at all attach points.
In the following example, we define a parameterized policy "param-example". In this example, the policy
takes two parameters "$mymed" and "$prefixset". Parameters always begin with a dollar sign, and consist
otherwise of any alphanumeric characters. Parameters can be substituted into any attribute that takes a parameter.
In this example we are passing a MED value and prefix set name as parameters.
route-policy param-example ($mymed, $prefixset)
if destination in $prefixset then
set med $mymed
endif
end-policy
This parameterized policy can then be reused with different parameterizations as shown in the example below.
In this manner, policies that share a common structure but use different values in some of their individual
statements can be modularized. For details on which attributes can be parameterized, see the individual
attributes for each protocol.
router bgp 2
neighbor 10.1.1.1
The parameterized policy param-example provides a policy definition that is expanded with the values provided
as the parameters in the neighbor route-policy in and out statement.
Global Parameterization
RPL supports the definition of systemwide global parameters that can be used inside policy definition. Global
parameters can be configured as follows:
Policy-global
glbpathtype 'ebgp'
glbtag '100'
end-global
The global parameter values can be used directly inside a policy definition similar to the local parameters of
parameterized policy. In the following example, the globalparam argument, which makes use of the global
parameters gbpathtype and glbtag, is defined for a nonparameterized policy.
route-policy globalparam
if path-type is $glbpathtype then
endif
end-policy
OL-30423-03
remote-as 3
address-family ipv4 unicast
route-policy param-example(10, prefix_set1)
route-policy param-example(20, prefix_set2)
set tag $glbtag
Cisco ASR 9000 Series Aggregation Services Router Routing Configuration Guide, Release 5.1.x
Parameterization
Parameterization, on
481
Advertisement
Table of Contents
