So in our previous video, we implemented ICMP jitter with R1 as a source and R8
as the destination acting as a responder.
And in this video, I'd like to walk you through very similar configuration, but
this time it'll be based on UDP jitter as opposed to ICMP.
Again, the benefit of testing and probing with protocols that are similar to
what you're using, for example, like for voiceover IP,
is that it'll give you a better representation of what really will happen with
that protocol when it's used.
So with that in mind, let's go ahead and do a very similar treatment with j
itter, but this time with UDP, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
aka with R1 being the source and R8 being the target.
So back to the lab we go, still here at R1.
Now we already set up on R8.
We already told it to be a responder.
So if we do a show, run section SLA and press enter, it's already set up as an
IP SLA responder, and if we go to R1,
and do that same thing on the show, run, type, section SLA and press enter, it
's going to show us that we have one SLA in place,
and there are the details that we specified.
So we'll go into configuration mode, and let's create IP SLA to, so we'll type WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we'll go into configuration mode, and let's create IP SLA to, so we'll type
in IP SLA to press enter,
and then we get to choose on the type of SLA we want to set up.
So if we want to set up a UDP jitter SLA, we just go ahead and type that in
next, space question mark,
specify the target, which is 888 space question mark, specify the port, we'll
use any port we want,
let's go ahead and use 6783, a space question mark, and then for the number of
packets, let's go ahead and use 3,
and for the source IP, let's go ahead and use 1111, and that looks good, and
then we'll set up the frequency here, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we'll set up for every 30 seconds.
So the three packets, every 30 seconds, monitoring jitter.
What they've been do show IP SLA summary, and you'll notice that IP SLA2 is not
running,
and you'll notice we have that little carrot symbol there, indicating that it's
inactive,
so we want to go ahead and schedule that to run, so we'll type in IP SLA
schedule, our SLA number,
which is 2 for this demo, space question mark, and I'll say start time now,
and I'm going to go ahead and somebody tell it as far as lifetime to go ahead
and run forever, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and run forever,
and that way it'll just keep running and running until we do something to make
it stop.
So now we do a do show IP SLA summary, and there we have our UDP jitter,
round trip time looks pretty good, and if we do a show IP SLA statistics this
time too,
to look at that specific one, detailed and rest center, here's the information
for hearing that SLA.
There's the latest round trip time, we didn't specify any thresholds, so we're
not going to be over a threshold,
there's our round trip min average in max, and as we continue to scroll down,
here it has the jitter information. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
With the average jitter right there being 12, and if we continue to scroll down
, we have a number of successes too,
but if we hit the upper key and wait at least 30 seconds there, and do that
again, we now have number of successes 3.
So up to this point, we've now implemented two SLAs, SLA 1 and 2, the first one
looking at jitter based on ICMP traffic,
the second one looking at jitter based on UDP traffic.
So in the next video, let's modify a little bit further, and let's do an SLA
that is actually measuring on an application layer service, like HTTP,
and that's exactly what we'll do in the next video, so I'll see you there in WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and that's exactly what we'll do in the next video, so I'll see you there in
just a moment.