This section describes the Class of Service (CoS) Queue Mapping and Traffic Shaping features. In this
chapter, the following examples are provided:
•
"Show classofservice Trust" on page 13-3
•
"Set classofservice trust Mode" on page 13-3
•
"Show classofservice ip-precedence Mapping" on page 13-5
•
"Configure Cos-queue Min-bandwidth and Strict Priority Scheduler Mode" on page 13-6
•
"Set CoS Trust Mode of an Interface" on page 13-9
•
"Configure Traffic Shaping" on page 13-10
Each port has one or more queues for packet transmission. During configuration, you can determine the
mapping and configuration of these queues.
Based on service rate and other criteria you configure, queues provide preference to specified packets. If a
delay becomes necessary, the system holds packets until the scheduler authorizes transmission. As queues
become full, packets are dropped. Packet drop precedence indicates the packet's sensitivity to being dropped
during times of queue congestion.
Select per interface configuration scheme:
CoS mapping, queue parameters, and queue management are configurable per interface.
Queue management is configurable per interface.
Some hardware implementations allow queue depth management using tail dropping or Weighted random
early discard (WRED).
Some hardware implementations allow queue depth management using tail dropping.
The operation of CoS Queuing involves queue mapping and queue configuration.
CoS Queue Mapping
CoS Queue Mapping uses trusted and untrusted ports.
Trusted Ports
•
System takes at face value certain priority designation for arriving packets.
•
Trust applies only to packets that have that trust information.
•
Can only have one trust field at a time - per port.
Class of Service (CoS) Queuing
v1.0, November 2008
Chapter 13
13-1