WEBVTT

1
00:00.000 --> 00:02.720
All right, so for our game plan for the network,

2
00:02.720 --> 00:05.800
let me go ahead and just chat about a few critical components.

3
00:05.800 --> 00:07.360
One is DNS.

4
00:07.360 --> 00:10.160
We need to make sure that we have our internal DNS

5
00:10.160 --> 00:12.160
and that everything is resolvable.

6
00:12.160 --> 00:14.720
We also want to make sure that we have internet access

7
00:14.720 --> 00:17.280
and that would include features like a default gateway

8
00:17.280 --> 00:19.440
for clients to use on a given subnet

9
00:19.440 --> 00:22.120
and also some flavor of NAT or PAT

10
00:22.120 --> 00:24.640
to make sure that we are translating from our private address

11
00:24.640 --> 00:26.720
bases would go out to the public internet.

12
00:26.720 --> 00:29.680
And one other element I'd also coach you strongly about

13
00:29.680 --> 00:33.400
is for the actual infrastructure that we're going to be using
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:29.680 --> 00:33.400
is for the actual infrastructure that we're going to be using

14
00:33.400 --> 00:37.240
for the Kubernetes and then eventually the NSX application

15
00:37.240 --> 00:42.760
platform, I'm going to recommend no SDN, no software

16
00:42.760 --> 00:43.440
find networking.

17
00:43.440 --> 00:47.960
Now I know it is really, really cool and easy to spin up

18
00:47.960 --> 00:51.680
and create T0 gateways and tier one gateways

19
00:51.680 --> 00:54.880
and all the segments, whether they're VLAN based or overlay

20
00:54.880 --> 00:58.040
based and that those can be used to connect to external networks

21
00:58.040 --> 00:59.000
and so forth.

22
00:59.000 --> 01:01.280
However, what I want to put out here from experience
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:59.000 --> 01:01.280
However, what I want to put out here from experience

23
01:01.280 --> 01:04.080
over the last week and a half of doing this more than a dozen

24
01:04.080 --> 01:07.520
times is that if we're going to implement our Kubernetes

25
01:07.520 --> 01:09.640
on top of a software defined network,

26
01:09.640 --> 01:11.880
we are asking for a world of hurt.

27
01:11.880 --> 01:14.840
So although there is the possibility of successfully

28
01:14.840 --> 01:19.320
implementing the NSX application platform on top of a SDN

29
01:19.320 --> 01:22.120
network, it would be better as part of our infrastructure

30
01:22.120 --> 01:25.400
to go ahead and just use traditional VLANs

31
01:25.400 --> 01:28.880
and traditional routers for supporting the infrastructure

32
01:28.880 --> 01:30.120
including the Kubernetes.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:28.880 --> 01:30.120
including the Kubernetes.

33
01:30.120 --> 01:33.240
So although we don't have to avoid SDN and software

34
01:33.240 --> 01:35.840
to find networking for the actual Kubernetes

35
01:35.840 --> 01:38.320
and the NSX application platform itself,

36
01:38.320 --> 01:41.200
I would strongly recommend doing it without it.

37
01:41.200 --> 01:43.680
And that way you have that as part of your infrastructure

38
01:43.680 --> 01:46.200
to support the other routing and switching

39
01:46.200 --> 01:49.280
or implementing with software via NSX.

40
01:49.280 --> 01:50.960
Another key element I would point out

41
01:50.960 --> 01:55.680
is let's avoid using 192, 168, anything.

42
01:55.680 --> 01:58.120
Because there is some IP addressing using that space

43
01:58.120 --> 02:00.320
as part of the NSX application platform
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

43
01:58.120 --> 02:00.320
as part of the NSX application platform

44
02:00.320 --> 02:02.000
and the underlying Kubernetes.

45
02:02.000 --> 02:03.440
So if you're trying to use that as well

46
02:03.440 --> 02:05.520
for network reachability,

47
02:05.520 --> 02:07.520
that can also go ahead and cause grief.

48
02:07.520 --> 02:09.560
So I'm going to go ahead and stay positive here

49
02:09.560 --> 02:11.160
and I'm going to remove these nodes

50
02:11.160 --> 02:14.360
and just focus on the key elements that we want to implement.

51
02:14.360 --> 02:16.280
So for our game plan, for our infrastructure,

52
02:16.280 --> 02:19.160
I'm going to be using a top of rack switch right here.

53
02:19.160 --> 02:21.600
I'll label that T-O-R for top of rack.

54
02:21.600 --> 02:23.160
And it's going to be the core device.

55
02:23.160 --> 02:25.640
It's just so happens that I have this in my network already.

56
02:25.640 --> 02:27.480
I'm going to be using it for the network

57
02:27.480 --> 02:30.320
to support the NSX application platform.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:27.480 --> 02:30.320
to support the NSX application platform.

58
02:30.320 --> 02:33.240
So again, the part about it being Cisco isn't too critical.

59
02:33.240 --> 02:34.680
I just want to let you know what it is.

60
02:34.680 --> 02:37.680
So for our game plan, let's go ahead and use this network

61
02:37.680 --> 02:41.080
right here and let's use in my network, let's use VLAN 10.

62
02:41.080 --> 02:46.920
And that's using the IP address space of 10.10.0 with a/24.

63
02:46.920 --> 02:48.800
And then over here, the top of rack switch,

64
02:48.800 --> 02:51.640
this multi-layer switch, it has the IP address of .1

65
02:51.640 --> 02:53.600
on that 10.10.10 network.

66
02:53.600 --> 02:56.400
So I just want to reinforce that I'm using a physical gateway

67
02:56.400 --> 02:58.240
here connected to this VLAN.

68
02:58.240 --> 03:01.080
And I'm not using a tier 0 or a T1 gateway
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

68
02:58.240 --> 03:01.080
And I'm not using a tier 0 or a T1 gateway

69
03:01.080 --> 03:03.320
as part of the infrastructure that we're setting up here

70
03:03.320 --> 03:05.400
for the NSX application platform.

71
03:05.400 --> 03:07.720
So another network I'd like to go ahead and use

72
03:07.720 --> 03:11.280
as part of the infrastructure here is going to be VLAN 11.

73
03:11.280 --> 03:13.680
So for VLAN 11, the addressing space we're going to use here

74
03:13.680 --> 03:17.800
is 10.11.11.0 with a 24-bit mask.

75
03:17.800 --> 03:19.560
So anytime we see VLAN 11, we'll know

76
03:19.560 --> 03:22.840
as the network, the IP address space of 10.11.

77
03:22.840 --> 03:24.840
And over here, the top of rack switch

78
03:24.840 --> 03:27.480
has the default gateway address of .1.

79
03:27.480 --> 03:29.440
Then next, let's go ahead and use another VLAN.

80
03:29.440 --> 03:31.040
Let's use VLAN 12.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
03:29.440 --> 03:31.040
Let's use VLAN 12.

81
03:31.040 --> 03:32.800
And for the IP address space for VLAN 12,

82
03:32.800 --> 03:37.040
we use 10.12.12.0 with a/24 bit mask.

83
03:37.040 --> 03:39.360
And the default gateway here will be .1.

84
03:39.360 --> 03:41.680
And let's use one more network here as well.

85
03:41.680 --> 03:44.600
And that will be VLAN 13.

86
03:44.600 --> 03:47.240
So that's the layer two broadcast domain, VLAN 13.

87
03:47.240 --> 03:50.080
And for the IP address space for devices in that VLAN,

88
03:50.080 --> 03:52.760
let's use 10.13.13.

89
03:52.760 --> 03:54.240
With a 24-bit mask.

90
03:54.240 --> 03:56.320
In fact, to make this easier to read,

91
03:56.320 --> 03:58.560
we're going to assume that we're using a /24

92
03:58.560 --> 04:01.440
for all the networks as part of this topology.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

92
03:58.560 --> 04:01.440
for all the networks as part of this topology.

93
04:01.440 --> 04:02.840
And the top of rack switch is going

94
04:02.840 --> 04:06.600
to be the default gateway of .1 for that 10.13.13 address

95
04:06.600 --> 04:07.120
space.

96
04:07.120 --> 04:09.520
So for DNS services, I'd like to place my little Windows

97
04:09.520 --> 04:14.520
server here on the 10.10.10 network at .100.

98
04:14.520 --> 04:16.560
So as part of our infrastructure and testing,

99
04:16.560 --> 04:18.760
we want to verify this little Windows servers here

100
04:18.760 --> 04:20.680
at 10.10.10.100.

101
04:20.680 --> 04:23.640
And we're going to be using that server for DNS for name

102
04:23.640 --> 04:26.440
resolution, as well as network time protocol.

103
04:26.440 --> 04:27.800
So before we're completely done,

104
04:27.800 --> 04:29.600
we'll want to verify that all that is working.

105
04:29.600 --> 04:34.120
And then here on VLAN 11 on the 10.11.11 address space,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

105
04:29.600 --> 04:34.120
And then here on VLAN 11 on the 10.11.11 address space,

106
04:34.120 --> 04:35.360
this can be my management network,

107
04:35.360 --> 04:39.240
not just for the management of my ESXi host and for vCenter,

108
04:39.240 --> 04:40.760
which is also true for that.

109
04:40.760 --> 04:42.520
But it's also going to be the management network

110
04:42.520 --> 04:44.600
for the Kubernetes cluster.

111
04:44.600 --> 04:46.160
And then as part of Kubernetes, it's

112
04:46.160 --> 04:48.520
also going to ask us for a front-end network.

113
04:48.520 --> 04:50.320
So we're going to use VLAN 12 for that.

114
04:50.320 --> 04:52.520
And it's also going to want a workload network.

115
04:52.520 --> 04:55.320
So we'll need to make sure that we have these VLANs in place,

116
04:55.320 --> 04:57.240
that my switching environment supports it.

117
04:57.240 --> 05:00.400
And also that vSphere knows about it.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
04:57.240 --> 05:00.400
And also that vSphere knows about it.

118
05:00.400 --> 05:02.960
For example, having port groups for the management network

119
05:02.960 --> 05:05.080
and port group for the front-end network

120
05:05.080 --> 05:06.880
and a port group for the workload network

121
05:06.880 --> 05:08.360
from a distributed switch.

122
05:08.360 --> 05:10.880
We also want to make sure we're providing internet access.

123
05:10.880 --> 05:12.200
So in my lab environment here, I've

124
05:12.200 --> 05:13.920
got this top-of-rack switch, which I mentioned

125
05:13.920 --> 05:15.920
is a Cisco multilayer switch.

126
05:15.920 --> 05:18.840
And then I have another router right here,

127
05:18.840 --> 05:20.800
which happens to be a 40-gate router.

128
05:20.800 --> 05:22.880
And that is then connected to the internet.

129
05:22.880 --> 05:24.960
So as far as the vendors are concerned,

130
05:24.960 --> 05:26.000
it really doesn't matter.

131
05:26.000 --> 05:27.800
You can use whichever vendor you want,

132
05:27.800 --> 05:29.400
as long as you have the functionality.

133
05:29.400 --> 05:32.320
So they've got a little common network segment here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

133
05:29.400 --> 05:32.320
So they've got a little common network segment here.

134
05:32.320 --> 05:35.760
So the top-of-rack switch has a default route going this way.

135
05:35.760 --> 05:37.960
And then at this router, I'm implementing NAT,

136
05:37.960 --> 05:40.920
or more specifically, PAT, port address translation.

137
05:40.920 --> 05:43.400
So if device is here, trying to reach a remote network,

138
05:43.400 --> 05:45.200
they'll use their default gateway.

139
05:45.200 --> 05:47.120
The top-of-rack switch, that routing environment,

140
05:47.120 --> 05:49.680
will forward that traffic based on its routing tables

141
05:49.680 --> 05:52.280
to my external router here, who will then

142
05:52.280 --> 05:54.600
provide the network address translation services

143
05:54.600 --> 05:56.520
before saying that traffic out to the internet.

144
05:56.520 --> 05:59.240
So we want to verify that DNS is working.

145
05:59.240 --> 06:01.960
We want to verify that internet access is working,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

145
05:59.240 --> 06:01.960
We want to verify that internet access is working,

146
06:01.960 --> 06:03.760
including the use of a default gateway here

147
06:03.760 --> 06:05.040
at my top-of-rack switch.

148
06:05.040 --> 06:06.480
And if we do access the internet,

149
06:06.480 --> 06:07.760
we'll also be able at that point

150
06:07.760 --> 06:10.720
to verify that NAT/ PAT is working as well.

151
06:10.720 --> 06:13.400
Now as we continue in the subsequent sets of videos

152
06:13.400 --> 06:15.880
and subsequent skills, we'll be using this topology

153
06:15.880 --> 06:17.800
that we've now implemented and verified

154
06:17.800 --> 06:20.080
as the place where we can then deploy

155
06:20.080 --> 06:21.680
the Kubernetes cluster.

156
06:21.680 --> 06:24.720
And then after that, the NSX application platform

157
06:24.720 --> 06:26.800
that's using the Kubernetes cluster.

158
06:26.800 --> 06:29.080
So I can't stress how important it is

159
06:29.080 --> 06:32.160
to have this infrastructure in place and tested,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

159
06:29.080 --> 06:32.160
to have this infrastructure in place and tested,

160
06:32.160 --> 06:35.120
because just one tiny little element

161
06:35.120 --> 06:37.160
out of the many prerequisites that have to be in place

162
06:37.160 --> 06:39.160
if just one of them isn't correct,

163
06:39.160 --> 06:41.760
it's gonna cause us a failure as we get to the point

164
06:41.760 --> 06:44.680
of deploying the NSX application platform.

165
06:44.680 --> 06:47.040
Now, one question might be, well, if we implement this,

166
06:47.040 --> 06:49.720
for example, we have all these VLANs created,

167
06:49.720 --> 06:51.240
we have our top-of-rack switch setup,

168
06:51.240 --> 06:53.200
we have all the routing and that setup as well,

169
06:53.200 --> 06:55.440
how do we test it prior to implementing

170
06:55.440 --> 06:57.880
and deploying the NSX application platform?

171
06:57.880 --> 07:01.200
The answer is we should probably place VMs, little VMs,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

171
06:57.880 --> 07:01.200
The answer is we should probably place VMs, little VMs,

172
07:01.200 --> 07:03.440
tiny ones that are very quick to deploy

173
07:03.440 --> 07:06.320
on each of these segments, just to verify

174
07:06.320 --> 07:09.100
that they can use this DNS server,

175
07:09.100 --> 07:11.400
just to verify that NTP is working,

176
07:11.400 --> 07:14.040
and also verify that they can get access out to the internet,

177
07:14.040 --> 07:16.600
because it's a lot better to identify a problem

178
07:16.600 --> 07:19.000
with our topology here, rather than waiting

179
07:19.000 --> 07:21.800
for the deployment of the NSX application platform,

180
07:21.800 --> 07:24.600
and then having some weird or abstract error come up

181
07:24.600 --> 07:26.080
that we're not sure what it is,

182
07:26.080 --> 07:27.840
when it was all based on our infrastructure

183
07:27.840 --> 07:28.800
not working correctly.

184
07:28.800 --> 07:31.320
So as part of getting this all up and working
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

184
07:28.800 --> 07:31.320
So as part of getting this all up and working

185
07:31.320 --> 07:33.640
and functioning, we have a couple of tasks.

186
07:33.640 --> 07:34.920
Number one is we need to make sure

187
07:34.920 --> 07:37.240
that the physical environment has these VLANs

188
07:37.240 --> 07:40.520
and that they exist, and also from a vSphere environment,

189
07:40.520 --> 07:42.600
we also wanna make sure we have poor groups

190
07:42.600 --> 07:44.380
that reflect this as well.

191
07:44.380 --> 07:45.560
So here's what I propose we do.

192
07:45.560 --> 07:47.920
Let's head over to vSphere first,

193
07:47.920 --> 07:51.040
and just take a look at the hosts that we plan on using,

194
07:51.040 --> 07:52.960
also give some tips on starting points

195
07:52.960 --> 07:54.880
to help avoid problems later,

196
07:54.880 --> 07:57.620
and we'll make sure that we have connectivity

197
07:57.620 --> 07:59.960
to these VLANs via port groups.

198
07:59.960 --> 08:01.160
So I'll see you in the next video
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

198
07:59.960 --> 08:01.160
So I'll see you in the next video

199
08:01.160 --> 08:03.200
as we take a look at this topology

200
08:03.200 --> 08:05.160
from the perspective of vSphere.

201
08:05.160 --> 08:07.120
So I'll see you there in just a moment.