Intelligent Services Gateway Configuration Guide, Cisco IOS XE Release 3S

Configuring MQC Support for IP Sessions

The MQC Support for IP Sessions feature provides modular quality of service (QoS) command-line interface (CLI) provisioning on Cisco Intelligent Services Gateway (ISG) IP sessions. It makes the full set of modular QoS CLI (MQC) syntax available for the sessions, whether they are configured locally or downloaded from a remote authentication, authorization, and accounting (AAA) server.

Finding Feature Information

For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for MQC Support for IP Sessions" section.

Use Cisco Feature Navigator to find information about platform support and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Contents

•Restrictions for MQC Support for IP Sessions

•Information About MQC Support for IP Sessions

•How to Configure MQC Support for IP Sessions

•Configuration Examples for MQC Support for IP Sessions

•Additional References

•Feature Information for MQC Support for IP Sessions

Restrictions for MQC Support for IP Sessions

The following restrictions apply to the MQC Support for IP Sessions feature:

•Creation of IP sessions over PPP sessions is not supported.

Note This document uses the generic term PPP to cover all protocol types. Examples of protocols include PPP over Ethernet (PPPoE) and PPP over ATM (PPPoA).

•Only the marking and policing features work in upstream traffic, All queueing, policing, and marking MQC features work in downstream traffic.

•Class-level queues are allowed only at the child level in session policy maps. All other levels must have a single-level policy and use the default queues.

•IP sessions over Gigabit EtherChannel (GEC) are not supported.

•Because IP sessions cannot be load-balanced, load balancing is not supported on any system.

Information About MQC Support for IP Sessions

To use and troubleshoot the MQC Support for IP Sessions feature, you should understand the following concepts:

•Supported Interfaces

•ISG Policers

•Precedence Order in Policy Maps

Supported Interfaces

MQC is not supported on the following interfaces:

•Bridge-Group Virtual Interface (BVI)

•GEC

•Interfaces configured for Layer 2 Tunnel Protocol (L2TP) sessions (on L2TP Network Servers (LNS))

ISG Policers

You can create configurations to work on an IP session with multiple traffic classes, and with one or more of the traffic classes acting as a policer. ISG policer is retained for backward compatibility and is fully supported if you do not want to migrate to MQC now. Note that ISG policing is supported on traffic classes, but MQC is not supported for traffic classes.

An ISG session can be configured with the ISG policer (also called dynamic rate limiting) or MQC, but not both. You should either use the ISG policer or migrate fully to MQC. If you do not migrate fully from ISG policer to MQC, a misconfiguration will occur.

Precedence Order in Policy Maps

A policy map can be attached to one or more interfaces to specify a service policy. Configuration sources combined with context determines which QoS policy map is applied. The three configuration sources and their general order of precedence are as follows:

1. Per-user (per-subscriber) configuration

2. Service profile

3. Interface configuration

This order of precedence shows the general condition, that is, service profiles and per-user configurations have higher priority than interface configurations.

However, a change of authorization (CoA) per-user push replaces the current per-user configuration for any overlapping or common feature. Similarly, when a new service logs in, its configuration replaces any overlapping feature, from previously configured service profiles, that is not already in effect from a per-user configuration source

If the new service then logs off, the previously existing configuration is reapplied if no higher-precedence configuration source is in effect.

Given those precedence qualifications, the policy map is determined as follows:

•If there is no policy map on the session, the incoming policy map is not applied.

•If an existing policy map is configured from a higher priority source than an incoming one, the incoming policy map is not applied.

•If an existing policy map is configured from a lower priority source than an incoming one, the incoming policy map replaces it.

How to Configure MQC Support for IP Sessions

This section contains the following procedures:

•Local Subscriber Profile MQC Support

•Configuring ISG QoS to IP Sessions

See the section "Configuring Per-Session QoS Using the ISG Framework" in the "Configuring ISG Control Policies" chapter in Cisco IOS XE Intelligent Services Gateway Configuration Guide for information about configuring a local service profile.

Local Subscriber Profile MQC Support

To configure QoS policy maps on service profiles, perform the steps in the following procedure:

SUMMARY STEPS

1. enable

2. configure terminal

3. policy-map type service service-name

4. service-policy policy-name

DETAILED STEPS

Configuring ISG QoS to IP Sessions

To associate a previously configured traffic class with a policy map, perform the steps in the following procedure:

SUMMARY STEPS

1. enable

2. configure terminal

3. policy-map type service service-name

4. class type traffic class-name

DETAILED STEPS

Router# (config)# policy-map type service

Configuration Examples for MQC Support for IP Sessions

This section provides the following configuration example:

•QoS Policy-Map, Service Profile, and Command Policy-Map Configurations: Example

QoS Policy-Map, Service Profile, and Command Policy-Map Configurations: Example

The following example shows how to configure a QoS policy map, a service profile, and a command policy map. The command policy map is then configured onto interface GigabitEthernet 0/0/0 with the service-policy keyword.

Router# configure terminal 
Enter configuration commands, one per line. End with CNTL/Z.

 
Router(config)# class-map match-any EF-customer 
Router(config-cmap)# match access-group name CUSTOMER-EF 
Router(config-cmap)# class-map match-any EF-WAN 
Router(config-cmap)# match qos-group 6 
Router(config-cmap)# policy-map PREMIUM_MARK_IN 
Router(config-pmap)# class EF-customer 
Router(config-pmap-c)# set cos 6 
Router(config-pmap-c)# set dscp ef 
Router(config-pmap-c)# set qos-group 6 
Router(config-pmap-c)# class class-default 
Router(config-pmap-c)# set dscp af11 
Router(config-pmap-c)# set qos-group 1 
Router(config-pmap-c)# set cos 1 
Router(config-pmap-c)# policy-map PREMIUM_UB_OUT 
Router(config-pmap)# class EF-WAN 
Router(config-pmap-c)# police cir 200000000 
Router(config-pmap-c-police)# priority 
Router(config-pmap-c)# class class-default 
Router(config-pmap-c)# policy-map type service PREMIUM_SERVICE 
Router(config-service-policymap)# service-policy input PREMIUM_MARK_IN 
Router(config-service-policymap)# service-policy output PREMIUM_UB_OUT 
Router(config-service-policymap)# policy-map type control INT 
Router(config-control-policymap)# class type control always event account-logon 
Router(config-control-policymap-class-control)# 1 service-policy type service name 
PREMIUM_SERVICE 
Router(config-control-policymap-class-control)# interface GigabitEthernet0/0/0  
Router(config-if)# ip address 10.0.0.1 255.255.255.0 
Router(config-if)# pppoe enable group global 
Router(config-if)# service-policy type control INT 

Additional References

The following sections provide references related to the MQC Support for IP sessions feature.

Related Documents

MIBs

Technical Assistance

Feature Information for MQC Support for IP Sessions

Table 1 lists the features in this module and provides links to specific configuration information. For information about a feature in this technology that is not documented here, see the "Intelligent Services Gateway Features Roadmap."

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS XE software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Note Table 1 lists only the Cisco IOS XE software release that introduced support for a given feature in a given Cisco IOS XE software release train. Unless noted otherwise, subsequent releases of that Cisco IOS XE software release train also support that feature.

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2009 Cisco Systems, Inc. All rights reserved.