WEBVTT

1
00:00.000 --> 00:03.280
So, to help reinforce the concepts that we've covered in this skill and in

2
00:03.280 --> 00:04.280
these videos,

3
00:04.280 --> 00:07.390
here is the customer challenge I'd like you to take on as part of the

4
00:07.390 --> 00:08.360
validation of what

5
00:08.360 --> 00:09.360
we've learned.

6
00:09.360 --> 00:10.360
So, here's the scenario.

7
00:10.360 --> 00:15.730
The customer has this tier 0 gateway, gateway 5, connected to this external

8
00:15.730 --> 00:16.760
segment, and

9
00:16.760 --> 00:20.160
they also have verified basic connectivity to the IP address of the external

10
00:20.160 --> 00:20.940
router at

11
00:20.940 --> 00:22.320
1090 0.1.

12
00:22.320 --> 00:24.840
So, no problem with that connectivity there.

13
00:24.840 --> 00:28.860
They also configured a default route that looks something like this for IPv4

14
00:28.860 --> 00:29.560
that's using

15
00:29.560 --> 00:32.040
that IP address as the next top.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

15
00:29.560 --> 00:32.040
that IP address as the next top.

16
00:32.040 --> 00:35.660
However, what's not going well for them is that when they go down to their VMs

17
00:35.660 --> 00:36.600
like VM1

18
00:36.600 --> 00:42.580
here or VM2, when they try to ping that IP address at 1090 0.1, that ping is

19
00:42.580 --> 00:43.800
unsuccessful,

20
00:43.800 --> 00:47.160
meaning there's no response back here at the client, so they don't know exactly

21
00:47.160 --> 00:47.440
what

22
00:47.440 --> 00:48.440
went wrong.

23
00:48.440 --> 00:49.920
And that's where you and I come into play.

24
00:49.920 --> 00:54.080
They've asked us to come and help them identify what is the problem.

25
00:54.080 --> 00:55.480
So, here's what I'd like you to do.

26
00:55.480 --> 00:59.420
I'd like you to take a moment and think about what could be the issues

27
00:59.420 --> 01:01.000
preventing a successful
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
00:59.420 --> 01:01.000
preventing a successful

28
01:01.000 --> 01:05.520
ping, for example, from VM1 to that IP address on that external router.

29
01:05.520 --> 01:08.780
And then after you've taken a moment to list several things that could be

30
01:08.780 --> 01:09.600
possibly wrong,

31
01:09.600 --> 01:13.040
I'd then like you to offer what could we do to fix those problems.

32
01:13.040 --> 01:16.900
So, if it's an issue with a default gateway, for example, on a VM, the solution

33
01:16.900 --> 01:17.880
would be

34
01:17.880 --> 01:20.320
train the VMs to go ahead and have a correct default gateway.

35
01:20.320 --> 01:24.520
So, I'd like you to take some time and maybe identify three or four potential

36
01:24.520 --> 01:25.320
problems,

37
01:25.320 --> 01:28.740
and then the three or four potential solutions based on those problems you've

38
01:28.740 --> 01:29.440
predicted.

39
01:29.440 --> 01:32.080
So, have some fun with this exercise.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:29.440 --> 01:32.080
So, have some fun with this exercise.

40
01:32.080 --> 01:35.240
If you need to refer back to any of the previous videos, feel free to do that.

41
01:35.240 --> 01:38.980
And then when you've taken a moment or two to work through this exercise, join

42
01:38.980 --> 01:39.320
me in

43
01:39.320 --> 01:41.280
the next video and we'll compare notes.