In this video, we're going to design, configure, and verify
an IP SLA that's verifying reachability
to a given network.
And here's our game plan for this lab.
Let's imagine our target network is 10.0.1.0.
And at the moment, R8 has one path
going up to R6 as the next hop to get to 10.0.1.
In fact, let's verify that first,
and then we'll create an SLA that can
check for that reachability.
So here in the hands-on lab, let's go ahead and do a show ip WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here in the hands-on lab, let's go ahead and do a show ip
route, or let's do 10.0.1.0.
And we have a route that's going to 10.2.68.6.
That's our next hop, which is fantastic.
Let's look at the topology.
That's R6.
And I'm just going to shut down fa 4/1
just for a moment to verify we're going to lose that route,
and we don't have reachability some other way.
Let's do that.
So we've got to show cdp neighbors so I make
sure I get the right interface.
Config t.
And that would be interface fa 4/1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that would be interface fa 4/1.
We'll do a shut.
We're going to lose some neighborships there
with OSPF, and with that IPv4 and IPv6.
And let's do a show ip route.
And the 10.1 network is no longer in the routing.
In fact, we don't-- let's say we have no OSPF neighbors.
So we definitely don't have reachability to the 10.1
anymore.
So let me bring that interface up.
And interface, let's go back to the same interface.
We'll do a no shut. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We'll do a no shut.
Let's create an IP SLA that's checking
for reachability from R8 going up to the 10.0.1 network.
And R1's address is 10.0.1.1.
We'll do a config t.
And the syntax is ip sla.
And then we're going to go ahead and give this a number.
So let's call this--
just to remind myself where it is, I'm going to do 10011.
So that's 10.0.1.1, but it's just a number here.
But that'll help me remember what I'm targeting here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But that'll help me remember what I'm targeting here.
So ip sla 10011.
And then we're going to specify what is the type of SLA
that we're setting up.
What are we testing?
And if we're going to do just an icmp echo,
we just put icmp echo.
And then we can specify the destination address,
which is going to be 10.0.1.1.
And then if we want to, we can specify a source IP address
or a source interface for reachability
back so that when they respond to this ping,
we can specify where it should come back to.
And if you just want to use the default, just press Enter. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And if you just want to use the default, just press Enter.
And then we can specify other details,
such as-- the frequency would be great.
So how often do we want this to happen?
So let's say we want it to happen every 5 seconds.
So this ping is going to happen every 5 seconds.
Hopefully, we'll get a response every 5 seconds.
And it can show us the success or failure of this SLA.
So let's do a do show run pipe section sla
and see what we have so far.
We have SLA number 10011.
It's going to do echo 10.0.1.1.
It's going to do it every 5 seconds.
And also, I should point out, if we're WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And also, I should point out, if we're
curious about, what does my router
support as far as the SLA?
We can do a do show ip sla and application.
And it'll go ahead and show us what the options are.
So there's icmpEcho.
There's path-echo, path-jitter, dns, dhcp, ftp,
http, lots of options here.
So right now, all we're doing is we're just
doing a quick SLA based on IP connectivity with echo.
So now the challenge is we have this SLA, but it's not running.
We also need to schedule it. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We also need to schedule it.
So we'll do an IP SLA schedule.
Then we'll specify the SLA number, which is 10011.
And then we can specify when it should start,
how long it should run.
So if we wanted it to run at certain times of the day,
or if we wanted it to run in so many seconds, or minutes,
or hours from now, we could set that all up.
For the demo, I'm going to go ahead and specify
the start time is now.
And the lifetime is going to be, let's say--
not forever.
We're going to say 1,000 seconds-- actually, 10,000
seconds. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
seconds.
The lab's not going to run that long,
but that'll run from now until I'm done with this lab.
So now that it's running, and then we
do a show ip sla statistics, it's
going to show us the details for that SLA.
So here is SLA 10011.
And it has two successes.
And if we hit the Up Arrow key, now it's four,
and now it's five, because it's happening
based on the frequency that we specified.
So on the router, router 1, we didn't
have set up anything as far as a responder,
because it's just an ICMP echo request. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
because it's just an ICMP echo request.
So to R1, it just looks like a ping request.
And it does a response.
And it's good to go.
So the power of the SLAs is the fact
that we now have some historical information about successes
and failures, but we can also-- when
we get to tracking, we can do the tracking on this SLA,
and then change the behavior of things like HSRP,
or routing protocols, or static routes
that are using tracking to influence their behavior as
well.
So I'm going to reset this lab.
And in the next video, a hands-on lab,
what you and I get to do is we are
going to set up another SLA, but this time we're WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
going to set up another SLA, but this time we're
going to base it on looking for jitter using UDP,
and also setting up the target R1
to be willing to respond to our UDP probes.
So I'll see you in the next video and lab for that.
Meanwhile, I hope this has been informative for you.
And I'd like to thank you for viewing.