Modular QoS Deployment Scenarios on Cisco ASR 9000 Series Routers
MLPPP QoS/MLFR QoS
QC-172
Cisco ASR 9000 Series Aggregation Services Router Modular Quality of Service Configuration Guide
OL-23108-02
QoS statistics are not retained for the policy that transitions from an active state to a suspended state. If
the policy is reactivated, all the previously collected statistics are lost and only the packets that pass
through the interface after the reactivation are counted. The suspended policy can be modified to reduce
its bandwidth requirements, so that it can be reactivated. A suspended policy can be modified while still
attached to the interface.
Multiclass MLPPP with QoS
Multiclass Multilink Point-to-Point Protocol (MLPPP) can be used with QoS and configured using the
encap-sequence command under a class in a policy map. The encap-sequence command specifies the
MLPPP MCMP class ID for the packets in an MQC defined class.
The valid values for the encap-sequence ID number are none, 1, 2, or 3. The none value is applicable
only when the priority level is 1 and indicates that there is no MLPPP encapsulation. The values 1, 2, or
3 can be used with priority 1 or 2 classes or other classes with queuing actions. An encap-sequence ID
number of zero (0) is used by the system and is reserved for the default class; it cannot be specified in
any other classes.
Note The encap-sequence ID numbers must be configured in numeric order. For example, you cannot assign
an ID number of 3 unless you have already assigned 1 and 2.
The number of encap-sequence ID numbers must be less than the number of MLPPP classes that are
negotiated between the peers via the multilink header. The user must ensure that the configuration is
consistent as the system does not verify this.
The ppp multilink multiclass remote apply command provides a way to ensure this. You can ensure
that the number of classes using an encap-sequence ID number (including the default of 0) is less than
the min-number value in the ppp multilink multiclass remote apply command. For example, if the
min-number value is 4, you can only have three or fewer classes with encap-sequence ID numbers.
The QoS policy validates the following conditions. If these conditions are not met, the policy is rejected:
• The encap-sequence ID number is within the allowed values of 1 to 3.
• When encap-sequence is configured for any class in a policy map, all classes in that policy map with
priority level 1 must also contain an encap-sequence ID number.
• The encap-sequence none configuration is restricted to classes with priority level 1.
• The class-default does not contain an encap-sequence configuration.
• Only classes containing a queuing action have the encap-sequence configuration.
Note Classes that share the same encap-sequence ID number must have the same priority.
A QoS policy map is configured as follows:
config
policy-map type qos
policy-name
class
class-name
action
action
action
. . .
To Next Page
Loading...
Need help?
General
