Merging Qos Policy-Maps - Cisco ASR 9000 Series Configuration Manual

Merging QoS Policy-maps

policy-map policy1_child
class class-default
police rate 1024 kbps
commit
!!
//In the USER file in RADIUS
RoadRunner_P1@Chasing1 Cleartext-Password := "LooneyTunes_P1"
cisco-avpair += "sub-qos-policy-in=policy1 shared-policy-instance spi_1",
cisco-avpair += "sub-qos-policy-out=policy1 shared-policy-instance spi_2",
Framed-Protocol += PPP,
Service-Type += Framed-User,
Fall-Through = no
What to Do Next
Run these steps in the USER file in RADIUS:
RoadRunner_P1@Chasing1 Cleartext-Password := "LooneyTunes_P1"
Merging QoS Policy-maps
Multiple QoS policies, applied through multiple dynamic templates, can be merged and implemented on a
single subscriber. The order in which the policies are merged is important, and is determined by the value of
the sequence number configured in the dynamic template. A policy is deployed using a policy-map. A new
optional merge keyword is provided with the service-policy command under dynamic template submode to
allow for the merging of policy-maps applied through multiple dynamic templates.
When more than two policy-maps are to be merged, two policy-maps are first merged together to create a
merged policy-map. Then, a third policy-map is merged with the first merged policy-map. This continues till
all policy-maps that are to be merged are merged together. For example, let's say that policy-maps p1, p2, p3,
p4 are to be merged in that order; p1 and p2 are merged first (using the rules listed below). Next, p3 is merged
with the <p1-p2> merged policy-map. Finally, p4 is merged with the <p1-p2-p3> merged policy-map, giving
the final merged policy-map.
The rules for merging two policy-maps are:
• A merged policy-map can be created by appending the classes of the second policy-map to the classes
• If the same class (except for the default class) is configured under both the policies, the instance of that
• If the default class under the first policy contains any actions other than any child policy actions, then
• If a child policy is configured under the default class of both policies, the two child policies are merged
• If a child policy is configured under the default class of either the first or second policy (but not both),
Cisco ASR 9000 Series Aggregation Services Router Broadband Network Gateway Configuration Guide,
Release 4.3.x
200
cisco-avpair += "sub-qos-policy-in=policy1 shared-policy-instance spi_1",
cisco-avpair += "sub-qos-policy-out=policy1 shared-policy-instance spi_2",
Framed-Protocol += PPP,
Service-Type += Framed-User,
Fall-Through = no
of the first policy-map (except for the default class).
class (including all actions configured under it) in the second policy is ignored.
that default class is added to the end of the merged policy. If it contains any child policy actions, then
the default class from the second policy is added at the end of the merged policy.
using the rules above. The merged child policy is then applied as the child policy under the default class
of the merged parent policy.
then it is applied (as it is) as the child policy under the default class of the merged policy. Child policies
under classes other than the default class are never merged together.
Deploying the Quality of Service (QoS)
OL-28375-03