WEBVTT

1
00:00.000 --> 00:06.800
Hello and welcome to performance and redundancy technologies.

2
00:06.800 --> 00:11.680
In this two-part skill, we're going to jump in and look at some technologies

3
00:11.680 --> 00:11.940
that can

4
00:11.940 --> 00:18.410
help us with performance and providing redundancy on our network, particularly

5
00:18.410 --> 00:19.200
for connecting

6
00:19.200 --> 00:20.760
to the cloud.

7
00:20.760 --> 00:25.760
Now keep in mind, these are often very similar functions.

8
00:25.760 --> 00:31.460
redundancy can be used for performance if, for example, we have two redundant
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:25.760 --> 00:31.460
redundancy can be used for performance if, for example, we have two redundant

9
00:31.460 --> 00:31.980
links

10
00:31.980 --> 00:36.880
going to our cloud environment and we're actually using both of them.

11
00:36.880 --> 00:41.370
That's going to give us performance and if one of them fails, we can keep using

12
00:41.370 --> 00:42.720
the other,

13
00:42.720 --> 00:45.420
therefore also providing redundancy.

14
00:45.420 --> 00:48.860
So a lot of these features can be used for both.

15
00:48.860 --> 00:55.480
That said, in this skill, we're going to be talking about timers and BFD.

16
00:55.480 --> 01:00.080
Specifically, modifying our routing protocol timers and implementing bid
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

16
00:55.480 --> 01:00.080
Specifically, modifying our routing protocol timers and implementing bid

17
01:00.080 --> 01:01.560
irectional forwarding

18
01:01.560 --> 01:06.760
detection to help the routers detect a failure quickly.

19
01:06.760 --> 01:09.600
That way, we can converge around that failure.

20
01:09.600 --> 01:15.290
We're also going to monitor these connections with something called IPSLA or

21
01:15.290 --> 01:16.440
service level

22
01:16.440 --> 01:17.960
agreement.

23
01:17.960 --> 01:23.480
This is a way to monitor connections for various things such as packet loss or

24
01:23.480 --> 01:24.440
jitter, too

25
01:24.440 --> 01:27.480
much latency and so on.

26
01:27.480 --> 01:33.690
Then we're going to take a look at using tracked objects along with IPSLA in
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
01:27.480 --> 01:33.690
Then we're going to take a look at using tracked objects along with IPSLA in

27
01:33.690 --> 01:34.760
order to actually

28
01:34.760 --> 01:39.440
do some action based on the quality of that link.

29
01:39.440 --> 01:46.150
Then we're going to take a look at using EEM or embedded event manager to also

30
01:46.150 --> 01:46.560
work with

31
01:46.560 --> 01:53.400
IPSLA and possibly tracked objects to help stabilize the environment.

32
01:53.400 --> 01:58.840
If that doesn't make much sense yet, you'll understand why after we look at IPS

33
01:58.840 --> 01:59.120
LA and

34
01:59.120 --> 02:04.410
tracked objects, we'll see, well, there may not be some stability there and we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:59.120 --> 02:04.410
tracked objects, we'll see, well, there may not be some stability there and we

35
02:04.410 --> 02:04.760
're going

36
02:04.760 --> 02:07.280
to bring in EEM to help with that.

37
02:07.280 --> 02:11.600
Finally, we're going to wrap up by looking at load sharing, which clearly is

38
02:11.600 --> 02:12.160
going to

39
02:12.160 --> 02:15.640
help with both performance and redundancy.

40
02:15.640 --> 02:18.760
And of course, we can do link load sharing.

41
02:18.760 --> 02:21.480
We can do server based load sharing.

42
02:21.480 --> 02:26.680
We're going to be focusing in this skill mostly on link or network load sharing

43
02:26.680 --> 02:26.960
.

44
02:26.960 --> 02:30.120
We'll hit a couple other things as we go.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
02:26.960 --> 02:30.120
We'll hit a couple other things as we go.

45
02:30.120 --> 02:34.800
This being a two part skill, we definitely have a lot to cover.

46
02:34.800 --> 02:36.680
So let's go ahead and jump in.

47
02:36.680 --> 02:38.920
I'll see you in the next video.

48
02:38.920 --> 02:47.900
[BLANK_AUDIO]