From: Curt Girardin (curt.girardin@chicos.com)
Date: Sun Jan 01 2006 - 17:52:31 GMT-3
Team,
I'm trying to better understand all the QoS related concepts and tools. I'm
reading the Wendell Odom Cisco QoS book (second edition) for the 2nd time. He
explains in great detail about how each queuing tool works by itself, but when
I try to visualize how they all work together, I am constantly confused by the
changing diagrams, and the inclusion of subinterfaces.
My biggest point of confusion lies in the placement of the queue, shaper, and
scheduler, as well as where an interface software queue lies in relation to
the class-based queue(s).
I'm really going out on a limb here, mostly using "intuitive-leaps" (guesses),
but this seems to be the order of operation to the best of my knowledge when
configured on a single physical interface:
1. Fragmentation (if configured)
2. Classification
3. Any nested service-policies configured
4. Compression
5. Policing
6. Drop policy (fifo, WRED)
7. Queuing
8. Shaping
9. Sheduler (between different classes?)
10. Tx-ring.
Am I looking at this all wrong? Is there a different logical way I should be
looking at this? Is there a another resource that explains this better?
TIA,
Curt
This archive was generated by hypermail 2.1.4 : Wed Feb 01 2006 - 07:45:47 GMT-3