Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

QoS on ACE Module


Does anyone know if it is possible to apply a 6500 QoS service-policy to a ACE module interface? I would like to leverage CBQOS to apply policing to traffic entering/leaving the ACE module.




Re: QoS on ACE Module

HI Collin,

You can use this by Configuring Control Plane Policing (CoPP).

CoPP uses a dedicated control plane configuration through the modular QoS CLI (MQC) to provide filtering and rate-limiting capabilities for the control plane packets.

CoPP is disabled by default.

CoPP is only supported on ingress (service-policy output CoPP cannot be applied to the control plane interface). Neither egress CoPP nor silent mode is supported.

Just follow the CoPP Configuration Guidelines and Restrictions .

CoPP uses MQC to define traffic classification criteria and to specify the configurable policy actions for the classified traffic. You must first identify the traffic to be classified by defining a class map. The class map defines packets for a particular traffic class. After you have classified the traffic, you can create policy maps to enforce policy actions for the identified traffic. The control-plane global configuration command allows the CoPP service policies to be directly attached to the control plane.

Use the below mentioned URL for Defining Traffic Classification

the commonly required traffic is identified with these ACLs:

•ACL 120-Critical traffic

•ACL 121-Important traffic

•ACL 122-Normal traffic

•ACL 123-Explicitly denies unwanted traffic

•ACL 124-All other traffic

Use the control plane commands as follows:


To enter control-plane configuration mode, which allows users to associate or modify attributes or parameters (such as a service policy) that are associated with the control plane of the device, use the control-plane command in global configuration mode. To remove an existing control-plane configuration from the router, use the no form of this command.

Syntax for T Releases

control-plane [host | transit | cef-exception]

no control-plane [host | transit | cef-exception]

Syntax for 12.0S Releases

control-plane [slot slot-number] [host | transit | cef-exception]

no control-plane [slot slot-number] [host | transit | cef-exception]

Syntax for 12.2S Releases for Cisco 7600 Series Routers


no control-plane

Syntax for ASR 1000 Series Routers

control-plane [host]

no control-plane [host]

The below link can be of huge information and config examples for control plane configuration:

Get back to me if you find this information relevant and useful to you.

Sachin garg