WEBVTT

1
00:00.180 --> 00:01.560
So based on our game plan,

2
00:01.560 --> 00:04.890
we are going to create this logical router right there.

3
00:04.890 --> 00:07.800
And there are some additional options when we set this up.

4
00:07.800 --> 00:09.870
We could say, you know what? I want some fault tolerance

5
00:09.870 --> 00:11.610
with active active or active standby,

6
00:11.610 --> 00:14.340
which is gonna call upon and using a lot of the services

7
00:14.340 --> 00:15.480
provided by the edge node.

8
00:15.480 --> 00:16.809
So for this demonstration,

9
00:16.809 --> 00:20.421
I'd like to focus on a simple distributed router only

10
00:20.421 --> 00:23.580
without using any additional fault tolerant features.

11
00:23.580 --> 00:25.800
And that way we're not getting the edges directly involved.

12
00:25.800 --> 00:28.431
So what we'll end up is we'll have this logical router

13
00:28.431 --> 00:30.300
and this logical router.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:28.431 --> 00:30.300
and this logical router.

14
00:30.300 --> 00:34.800
This distributed router function will live on ESXi-A,

15
00:34.800 --> 00:36.240
that host transport node.

16
00:36.240 --> 00:38.100
It'll also live here.

17
00:38.100 --> 00:40.109
And that's because both of these transport nodes

18
00:40.109 --> 00:42.734
have VMs connected to the respective segments

19
00:42.734 --> 00:45.090
involved with this default gateway.

20
00:45.090 --> 00:46.110
I also took a moment

21
00:46.110 --> 00:49.410
and I renamed these VMs as VM one, two, three and four.

22
00:49.410 --> 00:51.930
So it's easier to call out exactly where they are.

23
00:51.930 --> 00:53.370
So here's where they are

24
00:53.370 --> 00:54.853
as far as which host they reside on.

25
00:54.853 --> 00:56.670
And I've also color coded them

26
00:56.670 --> 00:57.932
and put their IP dresses here

27
00:57.932 --> 01:00.600
to represent which IP addresses they currently have.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
00:57.932 --> 01:00.600
to represent which IP addresses they currently have.

28
01:00.600 --> 01:02.310
So for this logical distributed router,

29
01:02.310 --> 01:05.096
we wanna use a dot one here on the 10 10 zero network

30
01:05.096 --> 01:07.770
and a dot one here on the 10 20 zero network.

31
01:07.770 --> 01:09.420
And that's what the clients will then use

32
01:09.420 --> 01:10.830
as a default gateway

33
01:10.830 --> 01:13.590
if they ever need to route traffic off their local subnet.

34
01:13.590 --> 01:14.820
So the first thing we're gonna do

35
01:14.820 --> 01:17.862
is create this logical layer three router,

36
01:17.862 --> 01:21.160
also known and loved as a gateway in the world of NSX.

37
01:21.160 --> 01:22.752
So let's go to the NSX manager

38
01:22.752 --> 01:24.810
and let's create it right now.

39
01:24.810 --> 01:27.300
So here on the NSX manager on the homepage, it's showing us

40
01:27.300 --> 01:30.120
that we don't have any gateways configured whatsoever yet.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
01:27.300 --> 01:30.120
that we don't have any gateways configured whatsoever yet.

41
01:30.120 --> 01:33.210
If we click on networking, it can also confirm that

42
01:33.210 --> 01:35.520
by showing us right here that we don't have any tier zero

43
01:35.520 --> 01:37.080
or tier one gateways.

44
01:37.080 --> 01:38.606
And if we click on the network topology,

45
01:38.606 --> 01:41.910
it's gonna show us the topology with the 10 segment

46
01:41.910 --> 01:43.050
and the 20 segment

47
01:43.050 --> 01:45.240
and with the VMs that are attached to each of those.

48
01:45.240 --> 01:46.980
But again, there's no routing currently

49
01:46.980 --> 01:48.000
between those segments.

50
01:48.000 --> 01:49.050
So let's fix that

51
01:49.050 --> 01:51.693
by setting up an east west routing function.

52
01:52.644 --> 01:54.120
And that is a tier one gateway.

53
01:54.120 --> 01:55.653
So we'll click here on tier one gateways,

54
01:55.653 --> 01:58.200
we'll click on add, and then we'll give it a name.

55
01:58.200 --> 02:01.950
Let's go ahead and call this Our Tier-1 GW dash A,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
01:58.200 --> 02:01.950
Let's go ahead and call this Our Tier-1 GW dash A,

56
02:01.950 --> 02:03.986
and that way if we have another tier one router as well,

57
02:03.986 --> 02:06.930
we can call it tier one gateway B, et cetera.

58
02:06.930 --> 02:09.990
And then as far as the HA mode, this is where for the demo,

59
02:09.990 --> 02:12.630
I'm gonna go ahead and just choose distributed only.

60
02:12.630 --> 02:15.550
And then later on what we'll do is we'll integrate this

61
02:16.406 --> 02:17.340
with a tier zero router

62
02:17.340 --> 02:19.560
and we'll also integrate it with edge nodes

63
02:19.560 --> 02:21.300
for the benefit of some high availability.

64
02:21.300 --> 02:23.670
But for now, I just wanna create a simple distributed

65
02:23.670 --> 02:27.009
logical router that can exist on ESXi-A

66
02:27.009 --> 02:29.790
and ESXi-B as host transport nodes.

67
02:29.790 --> 02:31.530
So here's the name of our tier one gateway.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
02:29.790 --> 02:31.530
So here's the name of our tier one gateway.

68
02:31.530 --> 02:33.144
I don't have any tier zero gateways to link it to yet.

69
02:33.144 --> 02:34.920
We'll do that in another skill.

70
02:34.920 --> 02:37.620
And so we've created it, we'll click on save.

71
02:37.620 --> 02:39.570
And this situation right here reminds me

72
02:39.570 --> 02:41.490
of when I first got into networking,

73
02:41.490 --> 02:42.750
'cause I bought a modular router

74
02:42.750 --> 02:44.130
and I failed to buy interfaces.

75
02:44.130 --> 02:47.850
So what good is a router if it doesn't have any interfaces?

76
02:47.850 --> 02:49.410
So if we go back to our network topology,

77
02:49.410 --> 02:51.270
here's our little router right here.

78
02:51.270 --> 02:52.470
As far as the service goes,

79
02:52.470 --> 02:55.290
it has a built-in gateway firewall rule

80
02:55.290 --> 02:57.240
that's permitting all traffic by default,

81
02:57.240 --> 03:00.630
but it's not connected. So we need to connect this gateway
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

81
02:57.240 --> 03:00.630
but it's not connected. So we need to connect this gateway

82
03:00.630 --> 03:02.490
to our two network segments.

83
03:02.490 --> 03:04.920
So to do that, instead of going to the router

84
03:04.920 --> 03:06.720
and saying, hey, connect to segment 10

85
03:06.720 --> 03:08.160
or connect to segment 20,

86
03:08.160 --> 03:09.990
we actually do it from the actual segments.

87
03:09.990 --> 03:11.760
So we'll go to the configuration for segment 10

88
03:11.760 --> 03:13.920
and say, you know what, please associate yourself

89
03:13.920 --> 03:15.180
with this gateway.

90
03:15.180 --> 03:17.100
And we'll do the same thing for segment 20.

91
03:17.100 --> 03:19.309
So over the left, we'll go over to segments.

92
03:19.309 --> 03:21.480
So here, let's start with segment 10.

93
03:21.480 --> 03:23.010
So we'll click on the three dots

94
03:23.010 --> 03:25.036
and then from that menu, we'll click on edit.

95
03:25.036 --> 03:26.670
And what we're gonna do is we're gonna somebody say,

96
03:26.670 --> 03:29.032
dear Mr. Segment 10, we want you to be associated

97
03:29.032 --> 03:31.650
with this gateway from the dropdown.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

97
03:29.032 --> 03:31.650
with this gateway from the dropdown.

98
03:31.650 --> 03:32.970
And that's it. Let's how you connect 'em.

99
03:32.970 --> 03:36.410
And then as far as what IP address this gateway should use

100
03:36.410 --> 03:39.000
as it connects to this segment, we put it in right here.

101
03:39.000 --> 03:40.260
So over here under subnets,

102
03:40.260 --> 03:42.180
we'll put in the IP address we wanna use,

103
03:42.180 --> 03:46.020
which is 10.10.0.1 with a 24 bit mask.

104
03:46.020 --> 03:48.304
So we'll put that in, and that will be the IP address

105
03:48.304 --> 03:51.600
that this logical interface is gonna use on the gateway

106
03:51.600 --> 03:53.610
as it connects to this segment right there.

107
03:53.610 --> 03:55.369
And then we'll scroll down and click on save.

108
03:55.369 --> 03:57.090
And then before we continue,

109
03:57.090 --> 03:58.740
let's go ahead and take a look at our network topology.

110
03:58.740 --> 04:02.100
So now we have our gateway that's connected
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

110
03:58.740 --> 04:02.100
So now we have our gateway that's connected

111
04:02.100 --> 04:03.600
to the yellow segment.

112
04:03.600 --> 04:05.692
It's IP address is 10 10 0 1 as shown right there.

113
04:05.692 --> 04:09.017
And then on that segment, currently I have two VMs,

114
04:09.017 --> 04:10.770
VM one and VM three.

115
04:10.770 --> 04:13.140
So our next step is go to segment 20 to do the same thing.

116
04:13.140 --> 04:15.480
Go to segment 20, say, Hey, segment 20, we want you

117
04:15.480 --> 04:16.803
to be associated with this gateway.

118
04:16.803 --> 04:20.010
And then at that moment we'll also specify the IP address

119
04:20.010 --> 04:21.240
that we wanna use on this gateway

120
04:21.240 --> 04:22.590
as it connects to that segment.

121
04:22.590 --> 04:24.876
So on the left, we'll go back over to segments,

122
04:24.876 --> 04:28.050
we'll click on the three dots next to segment 20

123
04:28.050 --> 04:29.640
from the menu, we'll click on edit,

124
04:29.640 --> 04:30.473
and then we'll specify
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

124
04:29.640 --> 04:30.473
and then we'll specify

125
04:30.473 --> 04:32.876
that we want this segment also be connected to our gateway.

126
04:32.876 --> 04:34.376
So we'll select it from the dropdown

127
04:34.376 --> 04:36.510
and then we'll get the IP address we wanted to use,

128
04:36.510 --> 04:38.340
which is 10.20.0.1

129
04:38.340 --> 04:40.200
with a 24 bit mask based on our plan.

130
04:40.200 --> 04:42.810
And then we'll scroll down and click on save.

131
04:42.810 --> 04:43.650
And in the background,

132
04:43.650 --> 04:45.193
I've already trained all of the clients

133
04:45.193 --> 04:49.230
to use those respective IP dresses of 10 10 zero one

134
04:49.230 --> 04:51.570
or 10 20 zero one based on the segment they're on

135
04:51.570 --> 04:53.010
as their default gateway.

136
04:53.010 --> 04:54.150
So before we go too much further,

137
04:54.150 --> 04:56.550
let's just do a quick spot check on these four VMs

138
04:56.550 --> 04:58.680
to make sure that they really do have these IP addresses

139
04:58.680 --> 05:01.680
and also that they have the dot one
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

139
04:58.680 --> 05:01.680
and also that they have the dot one

140
05:01.680 --> 05:04.320
on their respective subnets as their default gateway.

141
05:04.320 --> 05:07.680
So here is VM one at 10.10.0 11.

142
05:07.680 --> 05:11.850
There's its IP address and there's its default gateway.

143
05:11.850 --> 05:14.700
That looks good. Let's take a peek at VM number two.

144
05:14.700 --> 05:18.660
So here at VM number two, it should be at 10 20 zero dot 20,

145
05:18.660 --> 05:21.390
and it is, it's default gateway is 10 20 zero one

146
05:21.390 --> 05:22.530
and two more to go.

147
05:22.530 --> 05:26.910
So here it is, VM three, which should be at 10.10.0.10,

148
05:26.910 --> 05:28.878
which it is and there's its default gateway.

149
05:28.878 --> 05:31.740
And let's also take a peek at VM four.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

149
05:28.878 --> 05:31.740
And let's also take a peek at VM four.

150
05:31.740 --> 05:33.750
And here is VM four,

151
05:33.750 --> 05:37.110
which is at 10.20.0.21,

152
05:37.110 --> 05:40.200
and it has a default gateway of 10 20 zero dot one.

153
05:40.200 --> 05:41.580
Alright, all that looks good.

154
05:41.580 --> 05:43.320
And let's go back to VM one for a moment

155
05:43.320 --> 05:44.760
and let's do some pings.

156
05:44.760 --> 05:48.510
So let's do a ping over to 10.10.0.10.

157
05:48.510 --> 05:52.500
And that works. And that's VM three that we just pinged.

158
05:52.500 --> 05:56.940
It's also ping 10.20.0.20, and that's working.

159
05:56.940 --> 06:01.140
And let's also do a ping of 10.20.0.21.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

159
05:56.940 --> 06:01.140
And let's also do a ping of 10.20.0.21.

160
06:01.140 --> 06:02.370
And that works.

161
06:02.370 --> 06:05.130
So we just verified full connectivity between these VMs

162
06:05.130 --> 06:06.210
and what's really happening

163
06:06.210 --> 06:09.725
is this logical distributed router that we just created

164
06:09.725 --> 06:11.040
and then we assigned it

165
06:11.040 --> 06:12.539
and connected it to the two segments.

166
06:12.539 --> 06:14.512
That little logical router function

167
06:14.512 --> 06:17.550
that exists here on ESXi-A.

168
06:17.550 --> 06:19.830
It also exists here on ESXi-B

169
06:19.830 --> 06:21.873
as a distributed router function.