QoS on ACE Module

Unanswered Question
Sep 17th, 2009
User Badges:

Hello,


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.


Thanks!

Lee

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
sachinga.hcl Thu, 09/17/2009 - 14:00
User Badges:
  • Silver, 250 points or more

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



http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/copp.html#wp1141968



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



http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/copp.html



Use the control plane commands as follows:


control-plane

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


control-plane


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:


http://www.cisco.com/en/US/docs/ios/qos/command/reference/qos_a1.html#wp1047593


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

Sachin garg

Actions

This Discussion