593
Configuring QoS
QoS Treatment for Performance-Monitoring Protocols
When the cpu traffic qos dscp global configuration command is configured with table maps, you can configure only
one map from value at a time—DSCP, precedence, or CoS. A new configuration overwrites the existing configuration.
Packets marked by this command can be classified and queued by an output policy map based on the marked DSCP
or precedence value.
When the cpu traffic qos precedence global configuration command is configured with table maps, you can
configure only one map from value at a time—DSCP, precedence, or CoS. A new configuration overwrites the
existing configuration. Packets marked by this command can be classified and queued by an output policy map
based on the marked precedence or DSCP value.
You cannot configure a map from value of both DSCP and precedence. A new configuration overwrites the existing
configuration.
When the cpu traffic qos cos global configuration command is configured with table maps, you can configure two
map from values at a time—CoS and either DSCP or precedence.
If the cpu traffic qos cos global configuration command is configured with only a map from value of DSCP or
precedence:
— The CoS value of IP packets is mapped by using the DSCP (or precedence) value in the packet and the
configured table map. Packets can be classified and queued by an output policy map based on the marked CoS
value.
— The CoS value of non-IP packets remains unchanged.
If the cpu traffic qos cos global configuration command is configured with a map from value of CoS:
— The CoS value of IP packets is mapped by using the CoS value in the packet and the configured table map.
Packets can be classified and queued by an output policy map based on the marked CoS value.
— The CoS value of non-IP packets is mapped by using the CoS value in the packet and the configured table map.
Packets can be classified and queued by an output policy map based on the marked CoS value.
If the cpu traffic qos cos global configuration command is configured with a map from value of DSCP or
precedence and CoS:
— The CoS value of IP packets is mapped by using the DSCP or precedence value in the packet and the configured
table map. Packets can be classified and queued by an output policy map based on the marked CoS value.
— The CoS value of non-IP packets is mapped by using the CoS value in the packet and the configured table map.
Packets can be classified and queued by an output policy map based on the marked CoS value.
The cpu traffic qos qos-group global configuration command can be used to configure QoS group marking for
CPU-generated traffic only for a specific QoS group. The table-map option is not available.
Congestion Management and Scheduling
Cisco Modular QoS CLI (MQC) provides several related mechanisms to control outgoing traffic flow. They are
implemented in output policy maps to control output traffic queues. The scheduling stage holds packets until the
appropriate time to send them to one of the four traffic queues. Queuing assigns a packet to a particular queue based
on the packet class, and is enhanced by the WTD algorithm for congestion avoidance. You can use different scheduling
mechanisms to provide a guaranteed bandwidth to a particular class of traffic while also serving other traffic in a fair way.
You can limit the maximum bandwidth that can be consumed by a particular class of traffic and ensure that
delay-sensitive traffic in a low-latency queue is sent before traffic in other queues.
The switch supports these scheduling mechanisms:
Traffic shaping