Well, what luck that we have another very fun lab for us to do.
I really do enjoy the QOS labs because it takes a very difficult concept and it
makes
it reality.
We kind of see it come to life when we're looking at those show commands and we
see
what the packets are doing.
And here in this lab, if you did it, you probably saw that the police are able
to block traffic.
So if you had any issues, then we're going to go through the solution together
and the
lab script is once again provided below for the solution.
So let's go through this process here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's go through this process here.
What we're going to do is we're going to get on to router two and we want to
configure
a policeor.
Now to start with, we suggested that we come over to router one and we do a
ping over
to 10.12.0.2.
With a size of 1500 bytes, we could repeat it a few times, 50 or 100 times and
we see that
all of our pings are going through because we don't have anything configured on
router
two yet.
So we're going to configure a policy map as a policeor and we're told to start WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we're going to configure a policy map as a policeor and we're told to start
with a
two color just sort of that basic policeor concept.
So the way we're going to do that is by simply creating a policy map and we'll
call this
policeor, we'll call it, this is the single rate dual, we'll just call this
basic.
Police are basic, we'll keep it simple.
And we'll get on to our class default, just to block all traffic here, we're
going to
use the police command and we were told to block it down to eight kilobits per WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
use the police command and we were told to block it down to eight kilobits per
second.
Now if we do a question mark, we'll see that the CIR, that's the lowest rate
possible.
And we're sending 1500 byte pings, 8000 isn't a whole lot.
So feel free to play with this number a little bit, see how that impacts things
.
I'll also stick with the lab script here and say we're going to do 8000.
And that CIR parameter is actually optional as we talked about.
And then we want the bucket size to be 2000.
So I can just say 2000 here.
And that's the entirety of the command. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that's the entirety of the command.
Now I could keep going on this one line and say my conform action.
I usually like to hit enter here and add the conform action within the police
configuration.
And so we know we want to transmit our conform action and our exceed action.
We want this to drop.
So let's go and apply that to the interface and gig one zero service policy.
And we'll say police are basic.
And I didn't specify the direction. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And I didn't specify the direction.
This police is going to go in the input direction.
So show policy map interface gig one zero.
And we see our policing configuration with the CIR and the BC and how many
packets have
conformed and exceeded.
So now if I come back here and do my pings, we're going to start to see that we
're dropping
packets.
This is what we demoed earlier on with that's about every other packets going
through. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
through.
And over here now when we run this command again, we will see that we are
having some
packets fall into that exceeded bucket.
So that's the basic police.
And our ones, you know, I'm just going to go ahead and stop that with control
shift six.
And that makes it so that we don't have to ping all 50 times.
But we do see that that ended up making an impact.
Now the three color police are is going to be a little bit different going to
involve
some additional parameters.
So for this, we're going to create a different policy map. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So for this, we're going to create a different policy map.
We'll call this police are advanced or adv there and then do a class class
default to put
everything into the default queue.
And now we're told to once again, use the police command, we're told traffic
less than
eight kilobits per second.
So I could just say 8k here, 8000.
We've got so many different ways of doing things.
And it's going to be classified one way and then between eight and 10 as
another.
So we're talking about between two rates. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we're talking about between two rates.
Now we have a two rate police are so we're going to have two buckets BC and B
we're going
to have the two different rates of tokens flowing into those buckets and our
packets
are going to try to consume both of those tokens if they're available.
Otherwise it's going to drop down to exceeding if there's a B E token available
and if there's
no tokens available, it's going to be a violating packet.
So when we can use question mark to kind of figure out what we're doing here.
In fact, let's just go and be clear.
We're going to enter all the parameters this time. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We're going to enter all the parameters this time.
So I'm going to say CIR of 8000 BC, we were told to use bucket sizes of 2000
bytes.
And then we can specify the PIR to be that 10,000 or 10k and then be to be 2000
as well.
Now once again, I can hit question mark and see I can specify my actions on the
same line
or I can hit enter and start to do that.
So we're going to do our conform action transmit our violate action is going to
be drop. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
be drop.
And then in the middle here, our exceed action, what are we going to do?
Well, we were told to wipe the DSCP tag.
So I'm going to say set DSCP transmit.
And then the tag that I want is again, either zero here, so I can just enter
the raw number
or I can use default, which is also zero.
So I'm just going to say default here, exit out.
And now we could apply this into gig one slash zero. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And now we could apply this into gig one slash zero.
So we should have to remove the previous service policy.
Basic and now say service policy input, please or a DV.
All right, so show policy map interface will show us pretty much the same type
of configuration,
but we do now see that we have dual rates happening here.
We've got PIR and CIR, we have BC and BE. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We've got PIR and CIR, we have BC and BE.
Notice if we had BC and BE, but not a second rate, that would be a single rate
three color
policeor and it would use the overflow bucket method.
So now we have conformed, exceeded and violated.
Let's go ahead and generate some traffic here.
We see that we are still losing some packets.
So those would be packets that classify as violated.
Let's see if we nailed the.
Yeah.
We're not going to have a whole lot falling into the exceeded range just
because those
ranges are so close to each other, but we should occasionally get an exceeded WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
ranges are so close to each other, but we should occasionally get an exceeded
packet
in here.
Doesn't look like we're going to get any this time, but we could actually tweak
that
configuration to see if we are getting any packets that fall into that category
.
So let's do a config T and actually what we want to do next is we want to
configure the
shaper on router one, so we're going to flip over to router one and create that
policy
map.
This will be very similar to what we did in the video, but that's fine. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
This will be very similar to what we did in the video, but that's fine.
Good exercise.
Get onto that class default to do a shape average command.
And we were told to shape it to match the eight kilobits per second.
So I'm just going to say eight thousand here and we don't worry about BC or
anything like
that.
We're going to get a shape average eight thousand.
Yeah, actually we're supposed to use the 2000.
So let's go and do that.
So one of the key things here again is that it's in bits.
So we multiply it by eight to get bits instead of bytes. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we multiply it by eight to get bits instead of bytes.
So our 2000 becomes a 16,000 for both of those bucket sizes.
Now we can get onto our interface gig zero zero service policy output shaper.
And then we're just going to ping and see if things operate a little bit better
.
Probably not in this case for the most part.
It looks like we did get a little bit.
Oh, yeah, look at that. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Oh, yeah, look at that.
We've actually got some things coming through now at a slower pace.
Notice how it's going at a slower pace than what it would otherwise.
But the reality is that at 1500 byte pings, we should be able to get every one
of those
through if we go slow enough.
So this is what we're talking about here.
If we're just firing them off as fast as we can, packets are going to drop
because we
don't match the police.
So now we see every packet is actually going through.
I think this is really cool actually.
So they're all going through, but they we have had to slow down our rate to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So they're all going through, but they we have had to slow down our rate to
match the
eight kilovits per second that the police are is.
But because we've matched that rate, even though we got off to a rough start,
we did
find equilibrium and we're now sending all of those packets in a way that they
're not
getting dropped by the upstream police.
So make sure you take the time to play in this lab as much as needed to drill
that or
drive these points home, build the different types of police.
Make sure you can form a shaper that works and all of these different WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Make sure you can form a shaper that works and all of these different
configurations are
going to be important because we're going to want to be able, as the blueprint
says,
to interpret QOS results or QOS configurations.
And it all comes down to all of these class maps and policy maps and policing
and shaping.
I hope there's been informative for you and I'd like to thank you for viewing.