cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
902
Views
0
Helpful
6
Replies

how does shaping queue stuff for qos?

dolanduck.
Level 1
Level 1

I'm reading the official cert guild and i am confused.

does the shaper affect each queue like voice video and data?

correct me if I'm wrong you can apply a shaper to each queue ?

sending rate through the shaper does not exceed the shaping rate, that does that mean ?

6 Replies 6

balaji.bandi
Hall of Fame
Hall of Fame

you can limit the bandwidth based on the requirement or you can do the best effort basis.

 

good cisco document for reference :

 

https://www.cisco.com/c/en/us/support/docs/quality-of-service-qos/qos-policing/19645-policevsshape.html

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

so i can apply shaping to any queue right ?

and for example i can change the rate of each queue for example voice get 10mb at a constant rate ?

yes depends on the device and supported option available in the IOS.

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Joseph W. Doherty
Hall of Fame
Hall of Fame
"does the shaper affect each queue like voice video and data?"

That depends on how the QoS policy has been defined.

"correct me if I'm wrong you can apply a shaper to each queue ?"

Hmm, unsure about LLQ queues. Also, some devices have limitations when using nested QoS policies.

"sending rate through the shaper does not exceed the shaping rate, that does that mean ?"

Yes and no. Transmission rate, per frame/packet and during a single time interval, is always line rate, average rate, across a longer period, should not exceed shaping rate. Rate might also vary, during a short time period, if true Be is supported (i.e. shape peak that works correctly), but longer time period should not exceed shaping rate (i.e. shape average).

the shaping rate still confuses me, as much as i read it it does not click.

Confused how it works?

Simple example. . .

Suppose you have a metro-E connection with a 100 Mbps Ethernet hand-off, but you've only contracted for 15 Mbps of bandwidth. (Why do this? It allows for easy bandwidth growth.)

What happens if you exceed your contracted bandwidth allowance? Well, your metro-E vendor might just discard all the excess traffic or they might charge a premium for excess usage. For either reason, we decide we don't want to violate our contracted bandwidth.

So to insure we don't violate our metro-E contract, we do:

policy-map ShapeExample
class class-default
shape average 15000000

interface fastethernet 0/0
service-policy output ShapeExample

What the above does, it "counts" the transmitted bits during some time interval (for this explanation, we'll use one second intervals, but actual time intervals are usually in the 25 to 40 millisecond range), and once the logical limit is reached, excess will be queued. If there are queued packets, they will be dequeued, again as to not exceed the logical bit limit for the time interval. (Although frames/packets are what are queued/dequeued, we'll use bit counts and ignore actual frames/packets, because the bit volume of the frames/packets is what is really considered.)

To start, during the first second we "count" 10,000,000 bits. These pass straight through.

For the next/second we "count" another 15,000,000 bits, which again, we allow to pass through, but more bits want to be transmitted. We queue all of those, which are another 45,000,000.

For the next/third second, since we have 45,000,000 bits queued, we transmit another 15,000,000 and transmit no more. During this third second, we also receive another 5,000,000 bits, which are also queued. Our queue now has 45,000,000 less 15,000,000 plus 5,000,000 or 35,000,000 bits.

For the next two seconds, we dequeue 15,000,000 bits each second. During those two seconds no additional traffic is seen by the shaper. So now we have 35,000,000 bits less 30,0000,000 leaving 5,000,000 bits in the queue.

Lastly, during the next second, we dequeue the final 5,000,000 bits but we also receive another 5,000,000. Since the combination is only 10,000,000, which is still below our 15,000,00 bits per second limit, we let them pass through too.

What the shaper has done, is insure our average transmission rate has not exceeded 15 Mbps, although the circuit physically transmits at 100 Mbps.

Review Cisco Networking for a $25 gift card