18-18
Cisco 10000 Series Router Quality of Service Configuration Guide
OL-7433-09
Chapter 18 Regulating and Shaping Subscriber Traffic
MQC Support for IP Sessions
MQC Support for IP Sessions
The Modular QoS CLI (MQC) Support for IP Sessions feature extends the router’s QoS functionality to
support per-user QoS on IP sessions. Using this feature, you can configure queuing and non-queuing
features on IP sessions, either locally on the router or remotely using a authentication, authorization, and
accounting (AAA) server such as RADIUS. This feature also supports dynamic interface association
(interface redundancy) for IP sessions, L2TP Network Server (LNS) sessions, and L2TP Access
Concentrator (LAC) sessions.
IP sessions provide a way to create subscriber sessions for hosts and subscribers based on an IP source
address or subnet. MQC for IP sessions supports the following session categories:
•
IP single-host session—An IP session that represents a single host. This session is based on an IP
source address.
•
IP subnet session—An IP session that represents a set of end users. This session is based on an IP
subnet.
•
IP interface session—A single session that is created for one subscriber interface. The router applies
all MQC features attached to the interface to all traffic arriving and leaving through that interface.
MQC for IP sessions supports policing on an IP session, whether the policing action is configured on
one or more traffic classes of the session or directly on the session. For example, you can configure
shaping on an IP session and configure policing on one or more traffic classes of the IP session. You can
also configure policing statically on an IP session.
MQC for IP sessions supports the dynamic configuration of IP sessions using a RADIUS user or service
profile. The router applies the incoming dynamic policy to the IP session if no policy map exists on the
IP session or the existing policy map is configured from a lower priority source.
Note
The router removes the existing, lower-priority sourced policy map before adding the incoming
dynamic policy.
The router ignores the incoming dynamic policy if a policy map exists on the IP session and it is
configured from a higher priority source.
The following sections describe MQC on IP sessions:
•
Feature History for MQC Support for IP Sessions, page 18-19
•
QoS Actions Supported in IP Session Policy Maps, page 18-19
•
Interface Support for MQC on IP Sessions, page 18-19
•
Service Policy Maps and Service Profiles, page 18-20
•
Restrictions and Limitations for MQC Support for IP Sessions, page 18-20
•
Configuring MQC on IP Sessions, page 18-21
•
Configuration Examples for MQC on IP Sessions, page 18-23
•
Verifying Service Policies on IP Sessions, page 18-24
For more information, see the ISG: Flow Control: QoS Control: MQC Support for IP Sessions,
Release 12.2(33)SB feature guide.