In this video and hands-on lab, we
have the opportunity to practice implementing Control Plane
Policing in conjunction with dynamic routing protocols
on a Cisco router.
Let's take a look at our topology,
and then we'll get right into the lab.
This is the topology that you and I
get to play with in this hands-on lab.
And for this exercise, let's go ahead and choose R3,
where we'll implement Control Plane Policing.
And we're going to focus here on routing protocols.
So we'll implement a couple routing protocols.
Let's go ahead and use OSPF and EIGRP. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let's go ahead and use OSPF and EIGRP.
And that way, we can verify, based on matches
on the access-control list and also by doing a show command
for the policy map as applied to the control plane,
we can verify those hits are coming in, and if we have
problems or issues, we can do a Show Access List to verify
what's being hit, what's not being hit, and also the counts,
and also do the Show Policy Map to verify that,
are we having packets--
especially with OSPF or EIGRP--
that are being dropped?
Do we need to increase that?
Those are all the aspects of troubleshooting Control Plane WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Those are all the aspects of troubleshooting Control Plane
Policing when implementing with any protocol.
All right, so let's go to the CLI of R3.
We'll influent Control Plane Policing.
Then we'll enable the routing protocols.
All right, the lab is up and ready, and so are we.
Let's go to R3.
And on R3, let's go grab our notes.
Here's the Control Plane Policing practice,
and I'm going to go ahead and take--
let's make sure we have the pieces we
need for the routing protocols.
So let me bring this a little bit bigger.
So if we scroll down this list-- here we go. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if we scroll down this list-- here we go.
So here's our routing protocols.
We have-- it's all IPv4.
And it's looking for BGP established sessions
and each EIGRP, OSPF, and 13 is for PIM, and then IGMP.
Great.
So if we wanted to tweak or tune this,
we could take some out if we didn't need them,
or if we find that we're not matching on traffic that we
want to be for Control Plane Policing,
we could add them as well to our access list, which would then
already be inside the class maps and already part of the policy.
All right, so I'm going to Control-A, grab all that,
right-click, copy, and let's go back to R3. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
right-click, copy, and let's go back to R3.
So R3-- I'm going to paste that in.
[LAUGHS] I love it.
So here we have our routing class,
and we've got no matches on anything.
If we did a Show Access List, we'd have no matches,
and that's because we just don't have any routing protocols
running yet.
So if we wanted to implement a routing protocol,
we could do it across the board.
In fact, I've got some notes that
will help us do that faster.
And let's go ahead and look at OSPF first.
So we'll go Route On Route Off-- this little text document.
So here's the EIGRP--
on and off for IPv4.
Here's the EIGRP-- on and off for IPv6. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Here's the EIGRP-- on and off for IPv6.
OSPF-- let's do OSPF first.
So let's go ahead-- oh, here's OSPF with IPv6.
All right, let's do OSPF for IPv4
first, because we're not looking-- with our policy maps,
we're not looking for any IPv6 traffic yet.
So I'm going to go ahead and turn OSPF on for everything.
So just copy that.
And let's go hit the routers.
Then we'll go back to our routers.
I'll start on Router One, and we just paste it in.
Basically, all interfaces, you're in.
OSPF area-- zero.
And that'll take just a few moments for OSPF to converge, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that'll take just a few moments for OSPF to converge,
and once it does, we can do some quick checks here
to Show IP OSPF Interface Brief.
Fantastic.
And in just like 30, 40 seconds, we'll
have full adjacencies where appropriate,
and we'll have all the routing updates.
So we can go back to R3.
And here in R3, we'll do a Show Policy Map, Control Plane,
and press Enter.
What we should see as we go down to the routing class
right here--
look, hey, we have some traffic. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
look, hey, we have some traffic.
Great.
We have some traffic right here.
And this is part of troubleshooting, too,
if we didn't see any traffic here or any matches.
So our next step, maybe, is Show Access List just to verify,
are we getting hits or not?
So, ooh, here we go.
So we've got some 224.0.0.5.'s.
Great.
That's all OSPF speakers.
Then we have some 224.0.0.6.'s, which
is designated routers that are being sent messages to,
and they're tuned into that address.
All right, that's great.
And if we do a couple Up-Arrow keys to the Show Policy Map
Control Plane, we can also see that,
if we go down to our routing class-- WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
if we go down to our routing class--
and from a troubleshooting perspective,
we don't have any that have been exceeded or violated,
and so we have no drop activity, which
for our own legitimate routers, is an important thing to do.
Let's go and add EIGRP to the mix.
So we'll go back to Notepad to the document Route On Route
Off.
And let's add EIGRP for IPv4.
And because of the lower administrative distance,
it's going to be EIGRP routes here in just a moment.
So on R3, if we do a Show IP Route,
all the routes that have been learned dynamically are OSPF. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
all the routes that have been learned dynamically are OSPF.
And if we then go to all the routers and put
EIGRP in or IPv4--
EIGRP is so darn fast.
It is done.
Maybe just Show IP route.
You'll notice that there's not an OSPF to be seen,
and that's because the administrative distance
for EIGRP for internal routes is, what, 90?
Yeah?
Right there?
And OSPF is 110.
So OSPF routes are not being preferred and not
making it to the routing table, and the EIGRP ones do.
Now, also, as a result of this, if we go back to R3 and we hit WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now, also, as a result of this, if we go back to R3 and we hit
the Up-Arrow key a few times and do a Show Policy Map
for the control plane--
now if we go down to our class map called Routing Class,
we still have traffic.
Good.
Nothing's being exceeded and dropped,
and if we do a Show Access List--
this is the really fine-tuning-- we could actually identify,
OK, great, yep, we're matching here.
Now the final question I have here is,
what if we wanted to include IPv6
as part of the same policy?
Is that possible?
The answer is, yes.
We simply create access control lists for IPv6. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We simply create access control lists for IPv6.
In fact, let's do this.
In the very next video and lab, let's go ahead and implement
additionally some Control Plane Policing for IPv6,
and that way you can both see it and also get
hands-on practice doing it.
So with that in mind, I'll see you
in the next video in just a moment.
Meanwhile, I hope this has been informative for you,
and I'd like to thank you for viewing.