42-39
Software Configuration Guide—Release IOS XE 3.6.0E and IOS 15.2(2)E
OL_28731-01
Chapter 42 Configuring Quality of Service
Configuring VSS QoS
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
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.
Qos Action Restrictions
• 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.
Qos Policy priorities
• 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.
Table 42-1 Table QoS Policy Associations
Object Action
Physical port Policing, marking, and queuing
VLAN Policing and marking
Port and VLAN (PV) Policing and marking
EtherChannel Policing and marking
EtherChannel member port Queuing
To Next Page
Loading...
Need help?
General
