Policy Associations - Cisco Catalyst 4500 series Administration Manual

Chapter 42 Configuring Quality of Service

Policy Associations

The supervisor engine supports per-port, per-VLAN policies. The associated policies are attached to the
interface, VLAN, and a specific VLAN on a given port, respectively.
A policy can be associated with a variety of objects. The following table lists the objects and the actions
allowed.
Table 42-3
Object
Physical port
VLAN
Port and VLAN (PV)
EtherChannel
EtherChannel member port
Qos Action Restrictions
•
•
•
•
Qos Policy priorities
•
•
OL_28731-01
Configuring QoS on a Standalone Supervisor Engine 6-E/6L-E or Supervisor Engine 7-E/7L-E/8-E
Class-map: c1 (match-all)
0 packets
Match: cos 1
Match: access-group 100
QoS Set
dscp 50
police:
cir 200000000 bps, bc 6250000 bytes
conformed 0 bytes; actions:
transmit
exceeded 0 bytes; actions:
drop
conformed 0000 bps, exceed 0000 bps
Table QoS Policy Associations
The same actions cannot be performed multiple times in a given direction on different targets. In
other words, it is not possible to police the packets both on port and VLAN in the input direction.
However, the user can police on the input port and on the output VLAN.
Queuing actions are only allowed in the egress direction and only on the physical port.
Percentage-based actions like policer cannot be configured on a VLAN, Port and VLAN (PV) and
EtherChannel.
Port channel or VLAN configuration can only have a policing or a marking action, not a queueing
action.
If a policy on a port and a VLAN are configured with conflicting actions (such as policing or
marking actions on both a port and VLAN), the port policy is picked.
If policy on a VLAN on a given port must be over-written, the user can configure PV policy.
Action
Policing, marking, and queuing
Policing and marking
Policing and marking
Policing and marking
Queuing
Software Configuration Guide—Release IOS XE 3.6.0E and IOS 15.2(2)E
42-73