All right, it's time for our last video and lab,
as part of this set of videos with IP SLAs.
And it's probably my favorite, because we're
going to leverage the SLAs, as part of tracking,
to influence network behavior.
So let's take a look at the topology, we'll lay out a plan,
we'll implement that plan, and verify
that the IP SLAs and the tracking of those SLAs
is working as expected.
So here's what I'd like to do in this lab.
Right now, I've got a combination of OSPF,
or IPB4 and IPB6, running.
And what I would love to do is, let's just drop in EIGRP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And what I would love to do is, let's just drop in EIGRP
on the entire topology, or all networks.
And that way, all these networks and all these paths
will be available to us.
So let's do that, just to make sure we
have all the possible routes available to us.
And then once we do that, R8 is going
to have to paths to get to the 10.0.1 network.
It's going to go either this way or it's going to go this way.
And we can verify that with the show IP route, and verify that.
Here's what I propose we do, EIGRP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Here's what I propose we do, EIGRP
has an administrative distance of 90.
Let's create a static route that says,
to get to the 10.0.1 network, that it should
use the next hop of 10.2.68.6.
So basically, this right here.
So static route is going to win.
It's going to be like, I win!
I'm the best one!
And then, let's make a floating static route,
FSR I'm going to call it, floating static route,
that uses this path with 10.78.0.7. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that uses this path with 10.78.0.7.
And we'll give it administrative distance of 10.
So once we do that, if we set that up that way,
the primary path will be Northbound,
as we try to get a 10.0.1.
And if that--
[INAUDIBLE] how that interface fails,
we can't get to the next hop, it will then choose us.
But what we can do to tweak this is, if we set tracking,
we can have R8 say, let's track this IP address, which is,
let's see, that's going to be 10.2.46.6. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
let's see, that's going to be 10.2.46.6.
We could have tracking say, OK, I'm
going to do a SLA looking for 10.2.46.6, make
sure it's reachable.
And if it's not reachable, what we can do
is we can do tracking against that SLA and associate that
tracking with this static route.
So it would be something like this,
static route, you get to 10.0.1, with a 24-bit mask,
use this next hop, and we could say tracking, and then
the tracking number.
Not like a FedEx tracking number,
like the tracking number that's paying attention to the SLA, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
like the tracking number that's paying attention to the SLA,
looking for that specific IP address being reachable.
So if we did that, here's what would happen.
The static route would be fine, as long
as the SLA and the tracking was up, up, up.
But the moment that that IP address becomes
unreachable, from the perspective of R8,
it's going to say, whoa, this static routing that I've
been tracking on, boom, I can't use it.
And at that point, the floating static route
would be the next best option.
And our traffic would start going that way.
So this is going to be a little bit of configuration to do. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So this is going to be a little bit of configuration to do.
But I think it's going to be totally worth it
and a lot of fun.
So if you're sitting at a computer,
and you have access to the CBT Nuggets website right now,
click on the link for the virtual lab
associated with this video, and let's do this together.
All right, let's start.
And I'm going to bring up notepad,
it's the fastest way to do it, based on the tools
available right here.
Config t router, EIGRP, we'll use
autonomous system 1, and network everything,
and end, copy that, and just go to R8, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and end, copy that, and just go to R8,
boom, R2, all the routers.
One thing about EIGRP, oh, my gosh, is it fast?
Oh, my gosh, it's so fast.
I just put those commands in, then
we do a show IP route for EIGRP in our routes.
Everything, it's all there.
OK, so let's create our static routes.
So if we do a IP route for the 10.0.1 network
with a 24-bit mask. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
with a 24-bit mask.
And the next hop is going to be, it's going to be 10.2.68.6.
That's R6 in the topology, let me show you real quick.
That's this guy, right here, the Fa 4/0 interface on R6.
And when we come back, we're going to add a tracking to this
as well, so that this route will only take place,
assuming the tracked SLA is happy, happy.
So let's create that, the default
AD is going to be 1 there, so that's just 1
in the routing table.
And let's also create a floating static route.
And let's use 10.78. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And let's use 10.78.
And let me just verify that's in EIGRP as well.
So do show IP EIGRP interface, oh, yeah, it's
there, CRL 3/2, great.
So we'll do an IP route, in fact,
I'm going to use the up arrow a few times.
And we want to go to 10.0.1 with a 24-bit mask,
and the next hop is going to be 10.78.0.7, that's R7's address.
And let's give this an artificially higher AD of, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And let's give this an artificially higher AD of,
let's go 5.
So now if we a do a show IP route, our 10.0.1.0,
for our center, we have one route that's going through R6.
So if this next hop isn't reachable,
and this route's no longer good, the floating static route
will take over.
So what we'll do is, let's create an SLA.
And let's plan on targeting serial 3/1, which is 10.2.46.4.
So we'll do an SLA, check whether or not
that interface is reachable. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that interface is reachable.
So we'll go back to the CLI and config t, IP SLA.
And let's call us 10.2.46.4.
And let me just confirm that address, 10.2.46.4, yes,
that's the correct address.
And I'm just making the SLA number help me, remind me
of what it is I'm tracking.
So IP SLA 102464, icmp-echo is what we want to do.
And we want to target 10.2.46.4. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And we want to target 10.2.46.4.
And I'm not going to worry about the source IP address.
And for the frequency I want this to happen every 3 seconds.
The minimum is 5,000 milliseconds,
which is 5 seconds.
All right, so I will set it to the minimum for this SLA.
So we'll start on IP SLA.
I'm so excited about turning it on.
IP SLA schedule, and it is 102464,
and we'll go ahead and just start it now. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and we'll go ahead and just start it now.
And we'll say lifetime, or 10,000 seconds, great.
That'll be long enough for this demonstration
and for our lab time together.
All right, so now that it's running,
show IP SLA statistics, and show IP SLA configuration,
and show IP SLA applications.
So we've got it going.
We also had some successes in there that I saw,
as far as it working.
Now, now, here's the magic, we have the SLA. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now, now, here's the magic, we have the SLA.
Now we can set up tracking on that SLA
and include that tracking as part of our static route.
So if we do a show track, at the moment, no tracking whatsoever.
So now that we have this SLA that's running,
we verified it's working, let's now track it.
And to track it, we're going to use the command, track space.
And then we're going to create-- this is a new tracking number
just for tracking this SLA.
So let's use 6783, make it very visually different.
So our tracking is 67--
oh, you know what, the range is 1,000. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
oh, you know what, the range is 1,000.
So I'll use tracking number 123, how about that?
Because it'll fit.
Next it's asking us what we want to track.
Now, we could track on an interface,
but we want to track on the IP SLA that we just created.
So IP ?, SLA ?, and then the SLA that we have that's currently
running, which is this guy right here.
I'm going to copy paste that.
And I'm going to specify reachability.
So this tracking object, 123, is looking at the SLA 102464,
which is doing the pings. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
which is doing the pings.
And if it sees that there's reachability,
meaning it's successful, it's going
to go ahead and be considered up.
So now, we do a show track, check this out.
There's more than one command that starts with TRA.
All right, show track and press Enter.
Here, it's showing us the details.
This track of 123 is paying attention to the SLA, that guy,
and it's currently showing that the status is up.
Now, if for whatever reason, that SLA
is no longer able to successfully ping
that interface on R4, this would show as down. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that interface on R4, this would show as down.
Now the beautiful thing is, we can tie this tracking
to a static route.
And if the tracking says down, that static route
falls out of the routing table and won't be used anymore.
So let's do a show run, include route.
There's a config t--
I'm going to remove that static route, it's gone.
So now the route to 10.0.1 is going over to R7,
over the bottom left.
And now, let's add that route back in.
But this time, check it out, we can include the key word track WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But this time, check it out, we can include the key word track
and it wants the tracking number.
So the tracked object is 123, press Enter.
And now, if we do a show track, now it's
showing us-- oh, this is so cool.
Now it's showing us that we have this tracked object, 123.
It's paying attention to this SLA, looking for reachability,
and the current status is up, and we're also
including this tracking as part of at least one static route.
So if we had HSRP or some other service that was also
watching an SLA be a tracked object, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
watching an SLA be a tracked object,
it would show there as well.
And so here is a router that is currently--
if we do a show track, and we just verify it, and show track.
So it has a tracking object of 1,
it's tracking an SLA of 1111, currently it's showing as up,
and it's also being used by HSRP.
So if we did a show standby, and here
it's showing us that it's tracking on that tracking
object number, 1.
so right now, it's up.
But what this says is, if it's not up,
it's going to decrement the priority for HSRP by 10.
So if we look at the standby router, who WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if we look at the standby router, who
has a priority 105 and preempt is enabled,
if that tracked object goes down,
it's going to flip the active and standby roles
on this router.
So that's another great example of how we can use tracking.
Let's go back to our lab.
Now that we have this tracked, let's do a show IP route,
and let's go for 10.0.1.0.
And right now, we have a static route using dot 6
as the next hop.
And if you do show IP SLA statistics,
here it's showing us that it has not had a failure yet.
It's last operation it was OK, and a show track WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
It's last operation it was OK, and a show track
indicates that it's up.
So if we wanted to change that, all we'd have to do
is, if we go to R4 and we turn off this interface, serial 3/1,
it will no longer be reachable.
And as a result, that route, that is now using the tracking,
will drop out of the routing table.
So that is serial 3/1, that is 10.2.46.4.
So let's go back to R8 for a moment.
Let's do a debug IP routing, that's always-- WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let's do a debug IP routing, that's always--
--ing, that's always fun.
And let's go to R4 and do a show IP interface brief,
and make sure we turn off the right interface.
We'll get interface serial 3/1, we'll do a shutdown.
And with that shut down, let's go down back to R8.
So I just realized that EIGRP just went crazy too,
because we lost a whole bunch of routes that way.
But what we also can do is take a look at these messages
right here, and scroll up just a little bit.
So the tracking state for 123, that's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So the tracking state for 123, that's
the tracking object, working with SLA 102464,
reachability went to down.
And so if we do a show IP route, our route
now to the 10.0.1 network, this bad boy,
is using the next hop of 10.87.0.7.
And that's because the static route with the tracking
is no longer being used, because the tracked object is
showing it is down.
So we'll do a show track, press Enter, right here,
it's showing reachability is down. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
it's showing reachability is down.
And as a result, the static routing
that was tied to that tracked object
is causing that static route to no longer
be used in the routing table.
Thank you for joining me in this set of videos regarding
IP SLAs, looking for a variety of things, the network, as
far as reachability, or jitter, or services that are available,
and the ability to track using those SLAs to modify
our network behavior to keep our network flowing when it needs
to, even if there's a failure or disruption in one
little part of our network.
So I'll see you in the next set of videos.
Meanwhile, I hope this has been informative for you WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Meanwhile, I hope this has been informative for you
and I'd like to thank you for viewing.