WEBVTT

1
00:00.210 --> 00:01.890
Hello and welcome.

2
00:01.890 --> 00:03.690
My name is Keith Barker

3
00:03.690 --> 00:06.930
and in networks it's super common to have different subnets

4
00:06.930 --> 00:08.370
for different types of computers.

5
00:08.370 --> 00:10.770
You may have, for example, some servers in one subnet.

6
00:10.770 --> 00:12.270
You may have some clients in another

7
00:12.270 --> 00:14.970
and some IOT devices in yet another.

8
00:14.970 --> 00:17.712
And in a typical layer two switch network, behind each

9
00:17.712 --> 00:21.090
of those layer three subnets would also be a layer two VLAN

10
00:21.090 --> 00:24.390
associated with that IP addressing space for that subnet.

11
00:24.390 --> 00:25.770
So among some of the reasons

12
00:25.770 --> 00:28.710
for doing subnetting is one is we don't wanna have a single

13
00:28.710 --> 00:31.140
subnet with one giant broadcast domain
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:28.710 --> 00:31.140
subnet with one giant broadcast domain

14
00:31.140 --> 00:32.820
with thousands of devices on it.

15
00:32.820 --> 00:34.200
That's not very efficient.

16
00:34.200 --> 00:35.578
Or we may have multiple tenants

17
00:35.578 --> 00:37.500
that are sharing our address space.

18
00:37.500 --> 00:39.864
We wanna be able to control which devices can talk

19
00:39.864 --> 00:42.150
to each other within that space.

20
00:42.150 --> 00:45.210
For example, customer one over here and a couple subnets

21
00:45.210 --> 00:46.590
and customer two over here

22
00:46.590 --> 00:48.270
and customer three at over here

23
00:48.270 --> 00:49.920
with a couple of different subnets.

24
00:49.920 --> 00:51.270
And then being able to control back

25
00:51.270 --> 00:53.640
and forth which traffic is able to be seen

26
00:53.640 --> 00:54.900
by which other subnets.

27
00:54.900 --> 00:56.640
Now traditionally, and I mean for the last three

28
00:56.640 --> 00:58.200
or four decades, we've been doing that most

29
00:58.200 --> 01:01.380
of the time in the physical infrastructure with VLANs
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

29
00:58.200 --> 01:01.380
of the time in the physical infrastructure with VLANs

30
01:01.380 --> 01:02.520
and either physical

31
01:02.520 --> 01:04.890
or logical layer three routed interfaces to move

32
01:04.890 --> 01:06.210
that traffic back and forth.

33
01:06.210 --> 01:10.290
However, if we have NSX, we can now do that logical routing

34
01:10.290 --> 01:11.730
between multiple subnets.

35
01:11.730 --> 01:14.580
We can do that logically, in the gateway function

36
01:14.580 --> 01:16.140
inside of NSX.

37
01:16.140 --> 01:18.810
So in this skill we get to not only introduce that concept

38
01:18.810 --> 01:20.460
of doing the logical routing in NSX,

39
01:20.460 --> 01:22.500
but we're gonna put a game plan together

40
01:22.500 --> 01:23.820
and then implement it.

41
01:23.820 --> 01:26.376
And we're gonna start off with some of the basics

42
01:26.376 --> 01:28.800
with something called a tier one logical gateway.

43
01:28.800 --> 01:30.240
We'll take a look at before and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

43
01:28.800 --> 01:30.240
We'll take a look at before and

44
01:30.240 --> 01:32.160
after to see what changes happen.

45
01:32.160 --> 01:34.290
And we'll also take a look at the logical routing

46
01:34.290 --> 01:36.840
as a result of that, as a packet is being moved,

47
01:36.840 --> 01:40.260
for example, from VM one over to VM two.

48
01:40.260 --> 01:42.810
And our journey together continues in the next video.

49
01:42.810 --> 01:44.853
And I'll see you there in just a moment.