Basic QoS Model
The basic QoS Model
Actions at the ingress interface include classifying traffic, policing, and marking: 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 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…
Cisco switches perform most Quality of Service (QoS) operations in hardware, while routers perform QoS functions in software. It is best practice to use the switch to perform deep packet classification and marking functionality on the switches. The router will need to re-classify the packet, but the classification can be on the DSCP marking rather than a transport layer port number. Read more…
Here are some QoS examples configured on a Cisco Catalyst 3550:
Read more…
The 3550 WRR (weighted round robin) scheduler algorithm utilises four configurable queues at each interface of the switch. Let’s consider just FastEthernet ports for simplicity in this post. For each queue, the following important parameters could be configured: Read more…