175 Words. Plan about 0 minute(s) to read this.
Okay. One last thing, and I’m done blogging about scenario 7. Really, I promise. The last major task I was working through was a Cat3560 QoS nested policy map that would mark traffic, map it to a specific queue, and police various traffic to various rates. Not too hard (a little hard) in concept, mostly a syntax exercise to make sure you’re meeting all the scenario requirements. This was all syntax I had seen before, and yet one thing still threw me. I was instructed to map AF11, AF12 and AF13 packets to ingress queue 2. The answer key showed a solution as follows:
mls qos srr-queue input dscp-map queue 2 threshold 1 10
mls qos srr-queue input dscp-map queue 2 threshold 1 12
mls qos srr-queue input dscp-map queue 2 threshold 1 14
I thought I was losing my mind. They requested AF11, AF12 and AF13, and yet they were mapping 10, 12 and 14 instead of 11 through 13! Why? The answer, of course, is that the assured forwarding class number has nothing to do with the corresponding DSCP number.
Ethan Banks writes & podcasts about IT, new media, and personal tech.
about | subscribe | @ecbanks