WEBVTT

1
00:00.000 --> 00:04.440
So to assist us in reinforcing the skills regarding working with stretched gate

2
00:04.440 --> 00:04.940
ways and

3
00:04.940 --> 00:08.930
stretched segments, let's consider this customer scenario where the customer

4
00:08.930 --> 00:10.420
recently implemented

5
00:10.420 --> 00:15.150
a network segment called stretched SEG10, and that is right here in our top

6
00:15.150 --> 00:16.140
ology available

7
00:16.140 --> 00:17.300
at both sites.

8
00:17.300 --> 00:22.330
However, this little VM right here, whose name is Site 1 Blue, is not having

9
00:22.330 --> 00:23.180
any success

10
00:23.180 --> 00:26.020
as they try to communicate out to the internet.

11
00:26.020 --> 00:30.130
And this is based primarily on the topology, much like we left it in the set of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:26.020 --> 00:30.130
And this is based primarily on the topology, much like we left it in the set of

12
00:30.130 --> 00:30.580
skills

13
00:30.580 --> 00:34.580
where we put it all together, except there is a critical flaw somewhere in the

14
00:34.580 --> 00:35.020
mix that

15
00:35.020 --> 00:38.340
is preventing this VM from being able to get up to the internet.

16
00:38.340 --> 00:42.260
So as a quick possibility of what it might be, it could be routing.

17
00:42.260 --> 00:43.340
That's not in place.

18
00:43.340 --> 00:45.540
It could be NAT that's not in place.

19
00:45.540 --> 00:48.540
It could be DHEP services that aren't set up correctly.

20
00:48.540 --> 00:52.300
It could be the external network that the tier zero gateway is connected to

21
00:52.300 --> 00:53.100
going through

22
00:53.100 --> 00:56.950
the service provider that maybe isn't on the right VLAN or has the wrong IP

23
00:56.950 --> 00:57.700
address.

24
00:57.700 --> 01:01.400
And so here's the opportunity, considering all the things that could be wrong,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
00:57.700 --> 01:01.400
And so here's the opportunity, considering all the things that could be wrong,

25
01:01.400 --> 01:01.820
I'd like

26
01:01.820 --> 01:05.510
you to use the screenshots that follow this little video and actually take a

27
01:05.510 --> 01:06.020
look at those

28
01:06.020 --> 01:09.790
screenshots and determine based on that output, what do you think the problem

29
01:09.790 --> 01:10.460
is that's providing

30
01:10.460 --> 01:14.860
this VM right here, which is Site 1 Blue from getting out to the internet.

31
01:14.860 --> 01:17.750
And also what I didn't mention is it also could be a situation where this VM

32
01:17.750 --> 01:18.580
right here

33
01:18.580 --> 01:20.260
is not on the right segment.

34
01:20.260 --> 01:24.490
So if this is the stretch segment right here and this VM is connected to some

35
01:24.490 --> 01:25.340
other segment

36
01:25.340 --> 01:27.500
that also could prevent the connectivity.

37
01:27.500 --> 01:30.630
So take some time right now, take a look at those screenshots, identify what
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

37
01:27.500 --> 01:30.630
So take some time right now, take a look at those screenshots, identify what

38
01:30.630 --> 01:31.060
you think

39
01:31.060 --> 01:35.080
the problem is, and then when you are ready, join me the next video and we'll

40
01:35.080 --> 01:36.140
compare notes,

41
01:36.140 --> 01:39.560
take a look at the interface and determine together and confirm together what's

42
01:39.560 --> 01:40.060
wrong.

43
01:40.060 --> 01:42.870
So I'll see you in that next video when you've had a chance to look at those

44
01:42.870 --> 01:43.540
screenshots

45
01:43.540 --> 01:45.140
and when you're ready to reconvene.

46
01:45.140 --> 01:53.140
[BLANK_AUDIO]