All right, let's go ahead and do a quick configuration demonstration, seeing
all the
different ways that we can carve up the bandwidth on our interface.
So we're going to do a config T, create a policy map here, we'll just call this
policy
map test, and we'll get on to the class default queue.
And now what we can look at here is the different options that we have.
So that priority command, remember, I, first of all, I can't configure the
class default
as a priority queue. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
as a priority queue.
But we do start to see some of the commands that we can use here.
So as we've seen before, we can use the priority command to specify the
bandwidth that not
only is reserved, but also turns into that limit.
If we don't just hit enter, if I just hit enter here, this will turn the queue
into a strict
priority queue.
We have to be very careful about deploying that into an environment with
intentionality.
We definitely don't want to do it accidentally.
So we should usually specify our bandwidth.
Here's where we can specify the level. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Here's where we can specify the level.
If I say priority level, now we get the one or two.
So we'd want to configure this as level one, if it's for voice and level two,
if it's for
anything else, basically.
And again, we have to be careful about deploying a second priority queue into
the environment.
That's not necessarily a recommendation every case.
And here's where we can do percent as well.
So if I do percent question mark, we're going to see that I can specify a
percentage of
the link bandwidth.
I'm on a burst in there, but or we could just hit enter and allow us to reserve WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I'm on a burst in there, but or we could just hit enter and allow us to reserve
50%.
So that's the priority statement.
So let's say I reserve 50% of the link for the priority queue.
And now I'm on class with this other class.
Now I can look at the bandwidth command.
When I look at bandwidth, a lot of the same options exist.
It's just no longer a priority situation.
So I can't set a level, but I do number one, have the ability to specify kilob
its per
second as a raw value.
I can also say percent.
So same thing.
I could say, hey, for this queue, I want to reserve 25% of my bandwidth, right? WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I could say, hey, for this queue, I want to reserve 25% of my bandwidth, right?
And hit enter.
And there we go.
Or I can use this bandwidth remaining command.
So remaining, I just have to say percent.
And now I can perform my logic as if I'm talking about 100% outside the
priority queue.
So just to be clear about this, if I'm doing a raw percent and I said, hey,
that priority
queue gets 50% of the link bandwidth.
And let's say I have two other queues that I want to divide the bandwidth among WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And let's say I have two other queues that I want to divide the bandwidth among
Q1 here
and then Q2, which is probably our class default.
So if I'm doing a raw percentage, I do 50% of the priority queue.
Q1 would be 25%.
Q2 would be 25%.
And there is my 100%.
If I'm doing a remaining methodology, the remaining percent, my priority is
still going
to be 50% because this is still specified as a raw value. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to be 50% because this is still specified as a raw value.
But the remaining, remember, it removes the priority queue from the calculation
.
So if I want to divide the rest of the interface bandwidth between those two
queues, Q1 would
get remaining 50% and Q2 would get remaining 50% as well.
And so this just makes the math a little easier where here with the raw, this WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And so this just makes the math a little easier where here with the raw, this
whole thing adds
up to 100%.
With remaining percent, it's all of these non-priority queues that add up to
100%.
And so this can make it easier, for example, what if I had a situation where,
yeah, the
priority queue gets 50%, but now I actually have three queues and I want to
divide things
up evenly among these three queues.
Well with the raw percentage, I'm going to have to take a third of 50% and so WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Well with the raw percentage, I'm going to have to take a third of 50% and so
that is
like 16ish percent, something like that is 16.5% and try to get maybe 16, 16,
17, something
like that.
Or with the remaining side, I could just say, hey, you know what?
I just want all of these to have 33% and I'll assign one extra percent to one
of the other
queues.
This math is typically a little bit easier with the remaining concept rather
than the
raw over here, which has to take into account the percentage that was reserved WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
raw over here, which has to take into account the percentage that was reserved
for the priority
queue.
So it's a little bit of a shortcut method and we do see a lot of remaining
percent out there
in the real world, but again, just find the configuration you're most
comfortable with
that makes the most sense for you and the environment that you're configuring
this in.