Feature History For Per Session Rate Limiting; Restrictions And Limitations For Per Session Rate Limiting; Per User Multiservice Rate Limiting - Cisco 10000 Series Configuration Manual

Subscriber-Based IP Quality of Service

Feature History for Per Session Rate Limiting

Cisco IOS Release
Release 12.2(16)BX
Release 12.2(28)SB

Restrictions and Limitations for Per Session Rate Limiting

Do not apply service policies with CBWFQ actions to a VAI using a virtual template. The Cisco 10000
series router supports queuing only when you apply the service policy to a VC.

Per User Multiservice Rate Limiting

The per user multiservice rate limiting feature allows you to control the maximum rate of traffic for each
user behind a multiservice subscriber. This rate limiting feature uses the modular QoS CLI to provide
input and output policing rates for each user.
The configuration of per user multiservice rate limiting involves the following components:
•
•
•
•
For PPPoA, PPPoE, and PPP in L2TP sessions, apply the service policy to a virtual template interface,
which is used to create and configure a VAI. The VAI uses the virtual template interface to create a
uniquely configured user session. All of the VAIs that use the virtual template interface inherit the
service policy applied to it.
For RBE sessions, apply the service policy to the ATM virtual circuit (VC) or subinterface.
Do not apply service policies with CBWFQ actions to a VAI using a virtual template. The Cisco 10000
Note
series router supports queuing only when you apply the service policy to a VC.
Cisco 10000 Series Router Quality of Service Configuration Guide
18-4
Description
The per session rate limiting feature was introduced on the
PRE2.
This feature was integrated in Cisco IOS
Release 12.2(28)SB for the PRE2.
Access Control Lists (ACLs)—Create a unique ACL for each user behind the subscriber. The criteria
you specify, such as a user IP address, is used to filter the traffic coming into or leaving the
Cisco 10000 series router interface.
Class map—Classifies the traffic on an inbound or outbound interface. The class map uses the match
statements that you define to classify subscriber traffic.
Policy map—Defines QoS actions and rules and associates these to a class map. The policy map
specifies the class map for a session and also indicates the policing actions to perform.
Service policy—Attaches a policy map to an interface and specifies the direction (inbound or
outbound) that the policy should be applied.
Chapter 18 Regulating and Shaping Subscriber Traffic
Required PRE
PRE2
PRE2
OL-7433-09