To implement control plane policing,
we're following the MQC--
the modular quality service command line
interface-- that involves three major components-- identifying
the traffic with the class map, which
we did in the previous video.
And now, it's time to take a look
at manipulating or controlling that traffic with a policy
map, which is the focus of this video.
And as we continue the story, we've
already created our class maps-- we did that in previous video.
Let's go ahead now and use a policy map
that says what we want to do when we match on that traffic. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that says what we want to do when we match on that traffic.
And to specify the actions to take
when we see that traffic identified by the class map,
we're going to do that in the confines
or in the construct of a policy map
to say what we want to do with that traffic.
So I've got that also here in Notepad
to save me a little bit of typing,
and let me scroll this over to the left a little bit.
So here's the basic construct for a policy map.
The keyword policy desk map, space, and then
the name of the policy.
I'm going to call this one policy COPP,
and it is case sensitive dash policy.
So when we go to apply this later. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So when we go to apply this later.
I want to make sure I get the typing on that exactly correct.
And then I call in a class.
So in this policy map, the first class we're calling on
is class, ICMP class, which is looking for the class
map called ICMP class, and the respective axis
lists that's matching on the traffic
that we specified in that ACL, and if it
sees it, here's the action.
We are going to police that traffic
to 8,000 bits per second.
Now, if the traffic is less than 8,000 bits per second,
the conform action is going to be a transmit, which WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the conform action is going to be a transmit, which
means go ahead and send it.
And then we can also set up a burst.
Now in my environment here, I haven't set up
a burst size-- you can set up a burst
so that if you have temporary small amounts of traffic
over that allowed amount, it could be allowed
if it's still within the burst.
And then we can specify what the exceed action is as well
as the violate action, and the actions
for the exceed and the violate make it more flexible if you
are using a burst.
If you're not using a burst at all, like I'm not here,
you can say exceed action drop, violate action drop,
and simply if it's more than 8,000 bits per second WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and simply if it's more than 8,000 bits per second
for that type of traffic that's matched in the class map,
it's simply going to be dropped.
That's part of the benefit of control plane policing.
We can drop the traffic before the CPU has
to get involved and actually start
processing all those packets.
And then I've typed in exit-- now that exit's just
out of that specific class, and the action for that class,
and we're still in the same policy, called CoPP-Policy,
and now we're specifying, OK, for the class called IP sec
class, here's what we want to do.
And then we can have a police action and a conform action,
and then, if it's exceeded or the policy is violated, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and then, if it's exceeded or the policy is violated,
what do we want to do with that traffic that's over the limit?
And then as we scroll down, we've
got a similar thing for the management class,
and then a similar thing for the routing class.
And now in production environments,
it'd be a great idea to find out what your baselines are
for that type of traffic before you
start putting in these limits, because if you put them
in artificially low, and you're limiting your routing traffic,
you can have neighborships that break with OSPF because they
didn't have enough bandwidth or processing power
to go ahead and send all the updates
and receive all the packets that they needed to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and receive all the packets that they needed to
for their routing protocol.
So these are examples of how we could manipulate what's
going to happen based on the class of traffic that's seen,
and this is done in the form of a policy map.
Now in this policy map, what we're doing policing,
we're specifying OK, here's what to do
if we get over a certain level.
It's not really doing anything yet because the third step
of the modular equality of service CLI
is to apply this policy somewhere.
We can apply it to an interface, or we
can pledge to the logical control plane,
and that's done with the service policy command, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and that's done with the service policy command,
and we'll take that third step in the very next video.
So I'll see you there in just a moment.
Meanwhile, I hope this has been informative for you,
and I'd like to thank you for viewing.