So up to this point, we did an IC&P jitter probes and UDP jitter.
And now we get to focus our attention on an application layer service
monitoring with an
IPSLA using HTTP. So I just so happen to have a server right here. This is
actually the server,
server one nug that we use to get console access to all of our other devices.
And it's also running
a basic HTTP service based on its services available as a Microsoft server. So
it's running as a web
server. What I'd like to do here is set up a probe from R1 and test that HTTP
service just to verify
that it's able to respond back. And so for the details, let's go ahead and for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that it's able to respond back. And so for the details, let's go ahead and for
our test, let's use
a get for HTTP colon, WACWAC, and we'll go ahead and use the IP address there
192.168.1.100. And
that'll just be the default web page for the web services running there on that
server. Let's go
ahead and set up the frequency so that we test every 60 seconds. And then we'll
take a look at the
results. So let's head over to R1 and set up the probe to verify that HTTP
services are alive and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
services are alive and
well down to the server. And again, the server's IP address is at 192.168.1.100
. So we're still R1.
So let's do a show IPSLA summary to see where we're at. So we have two SLAs in
place, one and two.
Let's go ahead and make a third one. We'll do config T IP SLA and we'll use
three and press enter.
And for this one, we want to use HTTP. So we'll go ahead and type in HTTP space
. And then we'll do a
get and then we'll go ahead and put in the URL. So it's going to be HTTP colon
slash slash 192.168.1.100. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
slash slash 192.168.1.100.
And then for the frequency, and it says the frequency can be between one and
six hundred and four
thousand seconds ish. But let's go ahead and try 30. But it's not going to like
that because the
default timeout for the HTTP testing is 60 seconds itself. So we'll go ahead
and say the frequency
is going to be 60 seconds. And it likes that. Okay, so every 60 seconds once
this
SLA is scheduled and running, it'll probe that server and validate that they
can get content back.
So type in exit, we'll just do a do show IP SLA summary. And it is currently WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So type in exit, we'll just do a do show IP SLA summary. And it is currently
not running. Again,
that little carrot on the far left indicates that also an IP SLA schedule. The
ID number of our
SLA is three. And that's going to do a start time. Say now, let's also run this
forever as well.
So life space, then we'll exit up configuration to a show IP SLA summary. And
it is running right
there. So look at that round trip time. That is pretty massive. That could be WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
there. So look at that round trip time. That is pretty massive. That could be
for like the initial
request or something. So that probably will go down. But let me also take you
behind the scenes
and let's do a packet capture on our network somewhere between R1 and server
one. So we could
capture on this ethernet segment between our six and our eight or between our
two and our four
or between our one and our two. That's the path we're taking to get to the
server. We also verify
that with a trace down to 192.1 state dot 1 dot 100 just to verify the path.
And that looks great. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that looks great.
So the last octet represents the router. So our two are four, then our six,
then to our eight,
then to the server itself. All right, let's take a look at the capture. All
right. So that capture
is running. And as soon as I see some HTTP traffic, we'll go ahead and we'll
stop the capture. We
shouldn't have to wait more than 60 seconds for that to happen. So still
waiting, still waiting.
In fact, let's put a filter in for HTTP. So type in HTTP up here as a display
filter. And as soon
as it pops up here, we'll go ahead and stop the capture. All right. And there
it is. So we'll go WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
it is. So we'll go
and stop the capture and take a look at the details. So so here's the initial
probe from 10 dot 0
dot 12 dot one. That's our one going to the server. It's an HTTP get request.
If we look at the details
of that, I'll make that a little bit bigger and scroll down the byte
information here. We'll look
at the payload here. It is a get request. And then the next frame for the
response, let's go ahead
and close that and look at the response here. Here we have the response coming
back. So in our
probe, if we're looking for some specific element or component of a website, we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
probe, if we're looking for some specific element or component of a website, we
could probe for that
as well. And with an HTTP probe, there's also additional options of what we can
look for and
specify as part of that probe. But for this one, we just want to verify that
the basic website is
up and running. And if we wanted to, we could actually do a specific URL that
drills further
in the server and to make sure we get a response from it. But because we got
the response 200, okay,
which is feeding us back the content, we consider to be up. So if we go back to
our one,
and we do the show IPS lay summary again, and now our round trip time is better WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and we do the show IPS lay summary again, and now our round trip time is better
than it was.
So it's had a few opportunities and traffic. So now we do a show IPS lay
statistics, and we put a
three there and the keyword details and press center, it'll give us the details
for that IPS
la. So it's going to run forever, because we told it to there's the latest
round trip time.
And because we didn't specify a threshold, we're not over the threshold. If we
'd put a DNS name
instead of an IP address, it would also have information on how long it took to
resolve that
DNS information. Here's the TCP connection round trip time, and then the HTTP
information, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
information,
which is what we're after to begin with. And speaking of DNS, if we wanted to
have a specific
probe and IPS la just for DNS, we could do that as well. And the great news is
that that's exactly
what you and I get to do in the very next video. So I'll see you there in just
a moment.