WEBVTT

1
00:00.000 --> 00:02.600
So in this video, let's head over to the vSphere client.

2
00:02.600 --> 00:05.600
Just to verify we have ESXi host to work with.

3
00:05.600 --> 00:07.560
And I currently have some ESXi hosts

4
00:07.560 --> 00:10.440
which are connected over here on this management segment.

5
00:10.440 --> 00:13.000
I also have my vCenter here as well.

6
00:13.000 --> 00:15.920
So my vCenter server is at dot 111.

7
00:15.920 --> 00:21.080
And then I have some ESXi hosts here at dot 101 and dot 102

8
00:21.080 --> 00:21.920
and et cetera.

9
00:21.920 --> 00:24.840
In fact, I have six ESXi hosts that are sitting here

10
00:24.840 --> 00:27.000
on this management network under the control

11
00:27.000 --> 00:28.040
of this vCenter.

12
00:28.040 --> 00:30.120
So they go ahead and redraw this just a little bit
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:28.040 --> 00:30.120
So they go ahead and redraw this just a little bit

13
00:30.120 --> 00:32.400
to represent I have more than just two hosts here.

14
00:32.400 --> 00:34.520
So I'll put a dot ETC

15
00:34.520 --> 00:37.800
and then I'll put the vCenter right there at dot 111.

16
00:37.800 --> 00:41.520
Also as a heads up, I intentionally removed

17
00:41.520 --> 00:43.640
NSX manager from the equation.

18
00:43.640 --> 00:45.080
Just to help reinforce the concept

19
00:45.080 --> 00:47.080
that this infrastructure we're building

20
00:47.080 --> 00:49.080
for the NSX application platform

21
00:49.080 --> 00:50.840
and the Kubernetes that it runs on,

22
00:50.840 --> 00:53.240
this is all implemented on VLANs

23
00:53.240 --> 00:55.460
with traditional routers and switches.

24
00:55.460 --> 00:57.720
And in combination with that, we're using vSphere

25
00:57.720 --> 01:00.480
that is also aware of those vLANs.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
00:57.720 --> 01:00.480
that is also aware of those vLANs.

26
01:00.480 --> 01:03.320
So here's our little topology in the upper right hand corner.

27
01:03.320 --> 01:05.240
And here is the vSphere client.

28
01:05.240 --> 01:07.760
One of the very first things I'd recommend is that

29
01:07.760 --> 01:11.440
if you can, please do a remediation on your clusters

30
01:11.440 --> 01:15.040
just to make sure that everybody is up to snuff.

31
01:15.040 --> 01:16.920
So if we go here to the cluster

32
01:16.920 --> 01:19.500
and then over here we click on updates,

33
01:19.500 --> 01:22.120
we can confirm that we are all updated.

34
01:22.120 --> 01:23.840
In fact, let me put this right down here.

35
01:23.840 --> 01:25.440
So that's likely to get in the way down there.

36
01:25.440 --> 01:29.800
So and for these ESXi hosts, if we go to the networking tab here

37
01:29.800 --> 01:31.280
and we click on the distributed switch
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

37
01:29.800 --> 01:31.280
and we click on the distributed switch

38
01:31.280 --> 01:32.520
and we get a configure.

39
01:32.520 --> 01:35.200
One of my favorite views here is the topology view.

40
01:35.200 --> 01:38.280
Then we get on here to VLAN 11 and just expand that.

41
01:38.280 --> 01:39.800
It's showing us here the IP addresses

42
01:39.800 --> 01:43.720
for each of our six hosts on that management network,

43
01:43.720 --> 01:45.160
which is VLAN 11.

44
01:45.160 --> 01:47.280
And the vCenter server appliance

45
01:47.280 --> 01:49.400
is actually running on a different system,

46
01:49.400 --> 01:52.680
but it's connected logically here to VLAN 11 as well,

47
01:52.680 --> 01:53.520
right there.

48
01:53.520 --> 01:55.080
So back here in the hosting clusters view,

49
01:55.080 --> 01:56.360
let's create a new cluster.

50
01:56.360 --> 01:58.760
So right click and we'll create a new cluster

51
01:58.760 --> 02:00.880
and we'll call this cluster host for nap.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
01:58.760 --> 02:00.880
and we'll call this cluster host for nap.

52
02:00.880 --> 02:03.320
We'll go ahead and use DRS on this cluster.

53
02:03.320 --> 02:06.280
So for now let me go ahead and move that little topology

54
02:06.280 --> 02:08.280
out of the way and let me click on next.

55
02:08.280 --> 02:10.360
And we'll be using this latest and greatest version

56
02:10.360 --> 02:13.360
of ESXi as the image and we'll click on next

57
02:13.360 --> 02:14.600
and click on finish.

58
02:14.600 --> 02:17.320
So if we look at recent tasks that is now done,

59
02:17.320 --> 02:19.440
there is our new cluster host for nap.

60
02:19.440 --> 02:21.520
And let's go ahead because these are all maintenance mode.

61
02:21.520 --> 02:24.960
Let's go ahead and put in blue four, five and six.

62
02:24.960 --> 02:27.400
Let's drag them up and put them into that new cluster

63
02:27.400 --> 02:29.600
and click on okay for each one of them.

64
02:29.600 --> 02:34.600
There's four, there's five and here is six and click on okay.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
02:29.600 --> 02:34.600
There's four, there's five and here is six and click on okay.

65
02:34.600 --> 02:37.360
And there they are.

66
02:37.360 --> 02:40.200
And let's also before I bring them out of maintenance mode,

67
02:40.200 --> 02:42.480
I was gonna go ahead and with that cluster selected,

68
02:42.480 --> 02:45.840
we'll click on updates and go ahead and click on check

69
02:45.840 --> 02:46.760
compliance.

70
02:46.760 --> 02:48.880
And then if we need remediation, we'll go ahead

71
02:48.880 --> 02:49.720
and remediate.

72
02:49.720 --> 02:52.080
I just wanna make sure before we get to the point

73
02:52.080 --> 02:55.440
of adding NSX and adding our workloads

74
02:55.440 --> 02:58.680
as part of a Kubernetes cluster that all of our ESXi hosts

75
02:58.680 --> 03:00.560
are starting from a really good starting point.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

75
02:58.680 --> 03:00.560
are starting from a really good starting point.

76
03:00.560 --> 03:04.200
So for the recent tasks, we're currently checking compliance

77
03:04.200 --> 03:05.640
as shown right there.

78
03:05.640 --> 03:08.120
And that is done fantastic and it shows as compliant.

79
03:08.120 --> 03:10.320
So all three of those hosts four, five and six

80
03:10.320 --> 03:12.960
in this host for nap cluster, they're all using

81
03:12.960 --> 03:17.680
the exact same version of ESXi of the hypervisor,

82
03:17.680 --> 03:19.000
which is fantastic.

83
03:19.000 --> 03:21.280
And they also have some shared storage they can all get to.

84
03:21.280 --> 03:24.120
So let me go ahead and take them out of maintenance mode,

85
03:24.120 --> 03:26.840
each one of them like that, right click maintenance mode,

86
03:26.840 --> 03:30.200
exit, right click maintenance mode and exit.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

86
03:26.840 --> 03:30.200
exit, right click maintenance mode and exit.

87
03:30.200 --> 03:32.120
And then this also verifies shared storage.

88
03:32.120 --> 03:34.240
So if we go to the storage tab here,

89
03:34.240 --> 03:36.440
if we take a look at ISCSI one,

90
03:36.440 --> 03:38.320
all six hosts have access to that storage

91
03:38.320 --> 03:41.680
and ISCSI two, all six hosts have access to that storage.

92
03:41.680 --> 03:44.200
And this is a three raid five,

93
03:44.200 --> 03:46.640
all six once again have access to that shared storage.

94
03:46.640 --> 03:47.520
Fantastic.

95
03:47.520 --> 03:49.420
So next, let's take a look at the networking

96
03:49.420 --> 03:52.300
tab, and hopefully bring back our little topology right here.

97
03:52.300 --> 03:54.460
And let's go to the networking tab

98
03:54.460 --> 03:56.080
inside the VCR client,

99
03:56.080 --> 03:58.320
distributed switch called VDS one.

100
03:58.320 --> 03:59.900
And I'm going to once again move that topology

101
03:59.900 --> 04:01.320
right down here out of the way,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

101
03:59.900 --> 04:01.320
right down here out of the way,

102
04:01.320 --> 04:03.060
or hopefully out of the way a little more.

103
04:03.060 --> 04:05.560
So for this distributed switch, if we click on hosts,

104
04:05.560 --> 04:07.740
here it shows us that all six hosts

105
04:07.740 --> 04:10.700
have been configured to use that distributed switch.

106
04:10.700 --> 04:12.900
And also I've got some port groups that are being used

107
04:12.900 --> 04:16.820
specifically for ISCSI access and for provisioning

108
04:16.820 --> 04:20.340
and for V motion, and they have respective VM kernel adapters

109
04:20.340 --> 04:21.660
to support that as well.

110
04:21.660 --> 04:23.580
So here is the management network

111
04:23.580 --> 04:25.640
and that is this green one right here

112
04:25.640 --> 04:27.060
that they are connected to.

113
04:27.060 --> 04:28.780
However, what we don't yet have

114
04:28.780 --> 04:32.900
is we don't have the port groups associated with the VLAN 12
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

114
04:28.780 --> 04:32.900
is we don't have the port groups associated with the VLAN 12

115
04:32.900 --> 04:34.020
or VLAN 13 yet.

116
04:34.020 --> 04:35.780
So let's go ahead and create those.

117
04:35.780 --> 04:37.820
So we'll right click on the distributed switch

118
04:37.820 --> 04:40.180
and we'll simply click on distributed port group

119
04:40.180 --> 04:42.180
and then we'll click on new distributed port group.

120
04:42.180 --> 04:44.500
And this first of all, create one for VLAN 12.

121
04:44.500 --> 04:46.220
So I'm going to call this VDS one

122
04:46.220 --> 04:48.180
so that when we see it, we'll know exactly where it is

123
04:48.180 --> 04:50.420
as part of that parent switch.

124
04:50.420 --> 04:53.420
And for this, we'll just go ahead and call it VLAN 12

125
04:53.420 --> 04:55.020
and I'll call it front end as well

126
04:55.020 --> 04:56.740
because we're going to be using it for the front end

127
04:56.740 --> 04:58.780
as part of our Kubernetes cluster

128
04:58.780 --> 05:01.140
with the NSX application platform.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

128
04:58.780 --> 05:01.140
with the NSX application platform.

129
05:01.140 --> 05:02.980
So I'll move this to topology up to the top

130
05:02.980 --> 05:04.660
so I can go ahead and click on next.

131
05:04.660 --> 05:06.740
And then for the details of this new port group,

132
05:06.740 --> 05:09.700
I want it to be supporting VLAN number 12.

133
05:09.700 --> 05:11.300
So we'll go ahead and put that in as 12

134
05:11.300 --> 05:12.220
and then I'll scroll down.

135
05:12.220 --> 05:14.180
I want to go ahead and look at all the other properties

136
05:14.180 --> 05:15.020
as well.

137
05:15.020 --> 05:17.660
And then I'm going to go ahead and allow MAC address changes

138
05:17.660 --> 05:20.620
and force transmits and also enable MAC learning

139
05:20.620 --> 05:21.780
and click on next.

140
05:21.780 --> 05:24.020
Then I'm going to leave the traffic shaping alone.

141
05:24.020 --> 05:26.620
And then currently I have four uplinks

142
05:26.620 --> 05:28.140
associated with that distributed switch.

143
05:28.140 --> 05:29.820
And just for the lab, I'm going to say,

144
05:29.820 --> 05:31.500
let's just use VMNIC zero.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

144
05:29.820 --> 05:31.500
let's just use VMNIC zero.

145
05:31.500 --> 05:32.620
So I'm going to take all the rest

146
05:32.620 --> 05:34.980
and put them in the unused category.

147
05:34.980 --> 05:37.220
So the port group for VLAN 12 is the fact

148
05:37.220 --> 05:38.900
that we're just going to use that one uplink,

149
05:38.900 --> 05:40.700
which is going to be fine and we'll click on next.

150
05:40.700 --> 05:44.180
Then we'll click on next and next and finish.

151
05:44.180 --> 05:47.060
Boom, we now have our port group right here

152
05:47.060 --> 05:48.980
to support the front end.

153
05:48.980 --> 05:51.060
So let's go ahead and create one more port group

154
05:51.060 --> 05:52.420
for VLAN 13.

155
05:52.420 --> 05:54.300
So we'll go back to the virtual distributed switch,

156
05:54.300 --> 05:57.260
right click on distributed port group from the menu,

157
05:57.260 --> 05:58.940
click on new distributed port group.

158
05:58.940 --> 06:01.780
And we'll call this one VDS-1, VLAN 13.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

158
05:58.940 --> 06:01.780
And we'll call this one VDS-1, VLAN 13.

159
06:01.780 --> 06:03.940
And I'm also going to put the word workload in there as well.

160
06:03.940 --> 06:05.820
That way when we see it, it'll remind us

161
06:05.820 --> 06:07.980
of what it's being used for, what it will be used for,

162
06:07.980 --> 06:09.260
and we'll click on next.

163
06:09.260 --> 06:12.100
And then this is going to be supporting VLAN 13.

164
06:12.100 --> 06:13.260
So we'll put that in.

165
06:13.260 --> 06:15.100
And then we'll click on the check box

166
06:15.100 --> 06:17.940
for customized default policy config next.

167
06:17.940 --> 06:20.460
And I'm going to say accept to the port's transmits

168
06:20.460 --> 06:23.940
and Mac address changes, enable Mac learning, click on next,

169
06:23.940 --> 06:26.540
leave traffic shaping up this default, click on next.

170
06:26.540 --> 06:28.340
And then for the uplink, so I'm going to use a single uplink.

171
06:28.340 --> 06:30.180
So I'll take the others as part of the distributed switch
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

171
06:28.340 --> 06:30.180
So I'll take the others as part of the distributed switch

172
06:30.180 --> 06:31.380
and put them out of the picture,

173
06:31.380 --> 06:34.900
click on next and next and next and finish.

174
06:34.900 --> 06:35.900
Now in a production environment,

175
06:35.900 --> 06:38.260
you may want to have like a primary uplink

176
06:38.260 --> 06:39.780
then a backup and so forth.

177
06:39.780 --> 06:41.460
However, in a lab environment,

178
06:41.460 --> 06:44.860
I would recommend just using one to make it nice and clean

179
06:44.860 --> 06:47.220
so you know exactly where your traffic is flowing.

180
06:47.220 --> 06:50.300
So now we have our port groups for VLAN 11,

181
06:50.300 --> 06:53.700
a port group for VLAN 12, and a port group for VLAN 13.

182
06:53.700 --> 06:55.020
Now in this vSphere environment,

183
06:55.020 --> 06:59.100
if we were to also deploy the DNS server upon VLAN 10,

184
06:59.100 --> 07:01.340
we'd also want to make sure we have a port group for VLAN 10.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

184
06:59.100 --> 07:01.340
we'd also want to make sure we have a port group for VLAN 10.

185
07:01.340 --> 07:03.780
However, in my topology, I've got that Windows server

186
07:03.780 --> 07:08.060
at dot 100 on the 10, 10, 10 network hosted on a different server.

187
07:08.060 --> 07:11.060
So before we're all done, we'll verify that DNS

188
07:11.060 --> 07:14.020
and NTP services are working in conjunction

189
07:14.020 --> 07:16.460
with that server up on the Blue network on VLAN 10.

190
07:16.460 --> 07:17.700
So let's check our work.

191
07:17.700 --> 07:19.500
So we have these three hosts,

192
07:19.500 --> 07:23.740
Blue four, five and six that we can use as compute resources.

193
07:23.740 --> 07:26.340
We have port groups associated with the management network,

194
07:26.340 --> 07:28.860
VLAN 11, the front end network, VLAN 12,

195
07:28.860 --> 07:31.020
and the workload network, which is VLAN 13.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

195
07:28.860 --> 07:31.020
and the workload network, which is VLAN 13.

196
07:31.020 --> 07:34.700
So now that VMWare and vSphere are aware of those VLANs,

197
07:34.700 --> 07:37.140
we need to make sure in the physical topology

198
07:37.140 --> 07:39.380
that those VLANs actually exist,

199
07:39.380 --> 07:42.500
including the default gateway on the top of Rec Switch

200
07:42.500 --> 07:43.620
that we want to use.

201
07:43.620 --> 07:46.340
So we're going to shift over to the physical side of the house

202
07:46.340 --> 07:48.700
in the very next video and verify those components.

203
07:48.700 --> 07:50.660
So we'll see you there in just a moment.