WEBVTT

1
00:00.000 --> 00:04.000
Prior to implementing our IPSLA, let's put a game plan together and then we'll

2
00:04.000 --> 00:05.300
walk through it step by step.

3
00:05.300 --> 00:08.000
So here's why I propose. Let's go ahead and set up our

4
00:08.000 --> 00:12.160
Let's set up our eight as a target and we'll set up our one as the device who's

5
00:12.160 --> 00:13.700
initiating probes down to that target

6
00:13.700 --> 00:17.770
And let's configure the following video by video. We'll go ahead and we'll set

7
00:17.770 --> 00:19.300
up an IPSLA for ICMP

8
00:19.300 --> 00:25.090
Jitter and we can also set up one for UDP based jitter. Now, why would we want

9
00:25.090 --> 00:27.140
to possibly do one versus the other?

10
00:27.140 --> 00:30.950
Well, if you have an application, for example, like voice over IP where we're
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:27.140 --> 00:30.950
Well, if you have an application, for example, like voice over IP where we're

11
00:30.950 --> 00:31.540
using UDP

12
00:31.540 --> 00:35.500
It'd probably be good to do UDP jitter because that's the transport protocol

13
00:35.500 --> 00:39.350
It's using to identify problems or degradation before it becomes a serious

14
00:39.350 --> 00:41.480
issue and causes the application not to work

15
00:41.480 --> 00:46.720
Let's also leverage a web server. I have down here 192 once you get 1.100. We

16
00:46.720 --> 00:49.640
'll do an HTTP based IPSLA

17
00:49.640 --> 00:53.260
And also I've got DNS running down here. So let's do a DNS

18
00:54.140 --> 00:58.020
And that's this all do DHCP now for DHCP

19
00:58.020 --> 01:01.720
I don't recall whether I have DHCP running down here
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:58.020 --> 01:01.720
I don't recall whether I have DHCP running down here

20
01:01.720 --> 01:06.380
But what we can do is we can set up R2 as a quick DHCP server for this network

21
01:06.380 --> 01:07.140
segment right here

22
01:07.140 --> 01:08.740
And then once it's a DHCP server

23
01:08.740 --> 01:13.400
We could go ahead and set up R1 with an IPSLA testing and validating that DHCP

24
01:13.400 --> 01:14.580
services are available

25
01:14.580 --> 01:17.880
And then last but not least let me also walk you through an example of how we

26
01:17.880 --> 01:18.900
can do tracking

27
01:18.900 --> 01:23.300
So we can take for example an existing IPSLA and based on the success or

28
01:23.300 --> 01:26.100
failure of what that IPSLA discovers

29
01:26.100 --> 01:29.500
We can cause routes to either be injected into the routing table or removed

30
01:29.500 --> 01:30.620
from the routing table
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

30
01:29.500 --> 01:30.620
from the routing table

31
01:30.620 --> 01:32.620
So I'll give you an example of tracking as well

32
01:32.620 --> 01:35.380
And then again at the tail end we'll go ahead and put you on a hands-on lab

33
01:35.380 --> 01:36.820
So you can practice as well

34
01:36.820 --> 01:40.020
So join me the next video as we take a look at our first step and that's

35
01:40.020 --> 01:41.620
implementing an IPSLA

36
01:41.620 --> 01:46.980
Based on looking at ICMP jitter across the network. So I'll see you there in

37
01:46.980 --> 01:47.740
just a moment