Configuring MQC Support for IP Sessions
Restrictions for MQC Support for IP Sessions
2
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, page 2
• ISG Policers, page 2
• Precedence Order in Policy Maps, page 3
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.
To Next Page
Loading...
Need help?
General