So for our first IP SLA, we're going to focus on ICMP jitter.
And before we go to the CLI on the routers, let's go ahead and configure R8 as
a responder.
So syntax there is going to be IP SLA space responder.
And as a result, for many of these SLAs that we set up, it'll be able to
respond and give the information back to R1.
And even though the IP SLA responder isn't required for every single possible
SLA,
for the ones where it is required, it'll be enabled.
And an example where it wouldn't be required if we're just doing a connectivity WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And an example where it wouldn't be required if we're just doing a connectivity
test with a ping,
it's just ICMP connectivity testing.
So we wouldn't need the IP SLA responder for that.
But for other features, like ICMP jitter, R8 as a responder can identify when
it received that request with a timestamp.
It can also document when it sent the response back with another timestamp.
And so if we can figure R1 as the probe right here, and let's source the
traffic from 1.1.1.1.
That's a reachable loop back here on R1. And for the responder down here, we'll
use its loop back of 8.8.8.8. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
use its loop back of 8.8.8.8.
And so when the probe sends out the ICMP jitter probes down to R8, it's going
to be doing its initial timestamp,
so it'll be one of them. When R8 receives it, it'll put a timestamp to one.
And then when it processes it and says back, it'll send yet another timestamp.
So the final response coming back to R1 will include three timestamps.
We can also specify the number of packets we want to send in our probe.
We can also specify the frequency.
So let's go ahead for the number of packets that send three at a time.
And for the frequency, let's go ahead and say every 30 seconds. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And for the frequency, let's go ahead and say every 30 seconds.
We can also give an example of setting up a threshold.
So let's imagine that the round trip time, even though we're measuring ICMP j
itter,
we're also going to have information about the total round trip time.
Let's set a threshold of 100, meaning 100 milliseconds.
And if it's above that number, it would be considered out of compliance or the
IPSLA would say fail.
So we set a threshold of 100 and the actual round trip time ends up around 125
or 130.
That would be considered a fail.
Or if we're underneath the threshold, that SLA would be considered in WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Or if we're underneath the threshold, that SLA would be considered in
compliance.
So the three parts of configuring this would be one to tell R8, it's an IPSLA
responder.
Then on our one, we'll create an IPSLA.
And let's go ahead and start with IPSLA number one.
As our first example, we'll specify we're measuring ICMP dash jitter.
We'll specify the source address, the target address, the frequency, the
threshold.
And then the second thing we're going to do is we're going to go ahead and
start it.
So what that means is that we're going to create the IPSLA here and we're going
to go ahead and tell it to start. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now, as far as starting the IPSLA, we can say start now or we can specify a
date or a time.
We can also control how long it's going to run.
Do we want it to run forever or do we want it to run for, for example, 10,000
seconds or 1000 seconds or 500 seconds.
And that's all specified when we schedule that IPSLA to begin running.
So without further ado, let's go to our lab topology and let's begin the
configuration of an IPSLA for ICMP jitter.
So here in our lab environment, let me go ahead and double click on the lab top
ology,
making sure we're on the right lab based on the title. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
making sure we're on the right lab based on the title.
We're looking good.
And there's our topology, great, great, great.
So let's go down to our right.
Another way we get to our consoles for each of the devices is going to server
one nug.
So we'll double click on server one nug.
And that will give us console access to our routers.
All right.
So here comes server one.
We'll give that a moment to initialize.
And there it is.
So let's start with our eight.
In fact, here at our eight, we'll click on the our eight tab.
Let me just verify that we have connectivity up to our one.
We'll do a show IP route.
And sure enough, we have a route to 1111. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And sure enough, we have a route to 1111.
So let's go to a ping to 1.1.1.1.
We'll source it from our loop back zero interface, which is eight.
Eight to eight.
Today.
And we have connectivity.
That's also a trace.
So we can verify the path as well.
So trace up to one dot one dot one dot one.
And there's our path.
So it goes from our eight to six, four, two and one.
And that path is right here from eight to six to four to two and then to one.
All right.
So here on our eight, we'll go into configuration mode and we want this to be a
responder.
So we'll type in IP, SLA space, question mark, and we want this option right WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we'll type in IP, SLA space, question mark, and we want this option right
there.
So we'll type that in press center.
So now our eight is ready, willing and able to respond to the request from the
probe.
And for the probe, we want to go ahead and use our one.
So we'll head over to our one by clicking on the tab for our one.
We've already verified connectivity.
So go into configuration mode, I'll type in IP, SLA space.
And let's go ahead and use start with number one for IPS, LA number one.
We have a wide range of numbers there.
So we'll put in one space and then we'll press enter. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So now we have this IP, SLA one.
It's just now asking us, Hey, what do you want to measure?
DHP DNS FTP, HTTP, ICMP, echo and ICP jitter.
That's the one we want right there.
We want to measure ICMP jitter.
So we'll go ahead and copy paste that in as part of this IP SLA number one.
We'll do a space question mark and then we'll specify the target is going to be
our
eight at eight, eight, eight, eight, eight, eight, sorry Google for using your
DNS IP address.
But this is just an elaborate environment.
And then we'll do a space question mark and the source IP address we want to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then we'll do a space question mark and the source IP address we want to
use
is our one that's one dot one dot one, one space and question mark.
And the number of packets we want to use based on our goal here, we had three.
So let's go ahead and put three based on our game plan space question mark.
And then we can specify an interval here or we can go ahead and simply now that
we're
in the ICMP jitter SLA configuration mode here, we can specify the frequency.
Let's go ahead and put the frequency of 30, meaning every 30 seconds is going
to go
ahead and send those three packets.
And it's also here, specify the threshold. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And it's also here, specify the threshold.
So put in threshold and it's going to be in milliseconds, so say 100
milliseconds
based on our plan and boom, we are now set.
Now if we type in exit and we do a do show IP SLA summary just like that.
Here we have the idea is one.
That's the SLA that we can figure out.
SLA number one for the type.
It's ICMP dash jitter.
The destination is eight dot eight dot eight dot eight.
The current status is unknown.
It has no information regarding milliseconds.
And it says right here, last run, which is kind of crazy because it's not WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And it says right here, last run, which is kind of crazy because it's not
running at all.
Um, we need to actually tell it to start if we wanted to go ahead and run.
Oh, you can tell it's not running by this little carrot symbol right here.
So here are the codes.
Asterisk means it's active, the little carrot symbol means it's inactive and
the
little tilde symbol means it's pending, meaning it's going to run, but not yet.
So we need to actually tell this IP SLA number one to start.
So to do that, we're going to type in the command IP SLA schedule space
question mark.
Then we'll specify our SLA ID, which is one space and question mark. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Then we'll specify our SLA ID, which is one space and question mark.
And then we can specify when we want to start.
So I'm going to put in the keyword start time.
And I'm going to say, instead of like after a certain amount of time or a
certain
time of day, I'm going to say now, and then furthermore, we can specify how
long
it's going to run.
So we could say, for example, life space question mark, and then we can say
forever
or we could say a certain number of seconds.
And if we don't specify, you know, how long it should live or how long it
should run,
we can go ahead and press enter and the default time is 3600 seconds to run for
.
So now it's running. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So now it's running.
So now we do a show IP SLA summary and press enter.
Now we have an asterisk there.
It shows the round trip time 173.
And look at this, it says over threshold.
So if we did a show IP SLA statistics and the idea of one and then said detail
and press enter, it'll give us more information on that.
So it had two successes and one failure.
And it has, as of this moment of the show command, it has 3534 seconds to go.
Also, if we do that same show command of show IP SLA summary again, now it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Also, if we do that same show command of show IP SLA summary again, now it
shows
this test is okay.
And every 30 seconds in the background, it's sending new probes out.
So we do a show IP SLA statistics, one details.
It looks like we need a few more samples for this to populate.
So while this is populating and gaining information about the IC&P jitter
information
between R1 and R8, let me take you behind the scenes.
I'm going to do a little packet capture of the link right here between R1 and R
2.
That's the path we're taking from R1 as we go down to R8.
I just want to show you the back and forth traffic that's happening with those WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I just want to show you the back and forth traffic that's happening with those
probes
from the Pro Bar 1 going down to R8.
So I'm going to let this capture run for a second or two.
And there we go.
We have traffic from 1.1.1.1 going to 8, 8, 8, 8 right there.
So I'll go ahead and stop the capture and let's take a look at one of those.
Let's scroll up a little bit.
In fact, let me go ahead and just do a filter based on ICMP, a display filter
here in Wireshark.
And great.
There we have a few of them.
So let's take this one right here.
This is a request double click on it to bring it up, make that a little bit WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
This is a request double click on it to bring it up, make that a little bit
bigger here.
So R1 is acting as the probing device and R8 is acting as the IP SLA responder.
And if you take a look at the contents here in the ICMP payload, let's go ahead
and drop this down a little bit.
You'll notice on the outgoing packet, it has an originate timestamp that was
put there by R1.
And then the next two will be filled in in the responses coming back from R8,
including when it received the request and then when it sent that response back
.
So if we close this and we go to one of the responses here from 8, 8, 8, 8, 8,
coming back to 1.1.1.1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
coming back to 1.1.1.1.
We'll go ahead and double click on that to open it up and make that a little
bit bigger.
And I'll scooch down the byte pane here so we can see.
So here's the original timestamp set by R1.
And then we have the timestamp that was received and then the timestamp when it
sent the response back.
And so R1 can take that information and probe after probe after probe.
It can identify what the variance is in the delay or the jitter.
So now if we go back to R1, let's do a show IP SLA summary and it is still
running fantastic.
The RTT here is now showing S60. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
The RTT here is now showing S60.
That's great.
And as to show IP SLA statistics, then the ID for SLA, which is one.
And then the keyword details press center and now we have some additional
information.
So here's our round trip time being shown now, min, average and max, all of it
under 100.
That's why it says over threshold counts occurred.
False because things are within the threshold right now.
And if we scroll down a little bit further, we have our jitter time information
right here below.
And if we continue to go down, it's showing here that this SLA based on the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And if we continue to go down, it's showing here that this SLA based on the
default is going to run for 2,545 seconds or until we tell it to stop or until
we remove the SLA.
So now that we have the opportunity to sit up an IP SLA for ICMP jitter, let me
go ahead and walk you through a very similar function, but this time, measuring
jitter based on UDP.
So we'll do that the next video and I'll see you there in just a moment.