Deciding upon a QoS Classification and Marking strategy can be a difficult task. Cisco have provided certain recommendations which may be implemented as a baseline QoS strategy and then altered over time: Read more…
The basic QoS Model
Actions at the ingress interface include classifying traffic, policing, and marking: Read more…
RFC 4594 describes some example and provides guidelines for DiffServ service classification which may be used as guidelines or as a basis for a QoS Classification Strategy: Read more…
The Modular QoS CLI (MQC) command structure found in Cisco IOS® Software requires a class map is built incorporating the ACLs that identify the traffic that will have QoS applied to them. Read more…
The first element to a QoS policy is to classify/identify the traffic that is to be treated differently. Following classification, certain “marking tools” can set an attribute of a frame or packet to a specific value. Such marking (or remarking) establishes a trust boundary that scheduling tools later depend on. Read more…
