WEBVTT

1
00:00.120 --> 00:00.953
So, our last step

2
00:00.953 --> 00:03.180
is now to go ahead to the NSX Manager

3
00:03.180 --> 00:07.290
and specify that we want to take ESXi-A and ESXi-B

4
00:07.290 --> 00:09.660
and configure them for NSX

5
00:09.660 --> 00:12.900
to effectively make them host transport notes.

6
00:12.900 --> 00:16.590
So, let's go to the NSX Manager and let's do that right now.

7
00:16.590 --> 00:18.570
So, back here at the NSX Manager,

8
00:18.570 --> 00:20.310
we're now logged in once again.

9
00:20.310 --> 00:22.110
If we click on the System tab,

10
00:22.110 --> 00:24.390
which is where we need to go to add host currently,

11
00:24.390 --> 00:26.520
we have one NSX management node

12
00:26.520 --> 00:29.910
and no host transport nodes, but that is about to change.

13
00:29.910 --> 00:33.120
So, to add our ESXi host and bring them into the fold,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:29.910 --> 00:33.120
So, to add our ESXi host and bring them into the fold,

14
00:33.120 --> 00:35.700
what we're gonna do is with the System tab selected,

15
00:35.700 --> 00:36.750
on the left-hand side,

16
00:36.750 --> 00:38.940
we'll expand Fabric if it's not already expanded,

17
00:38.940 --> 00:40.740
and then click right here on Hosts.

18
00:40.740 --> 00:43.410
So, this interface is slightly updated

19
00:43.410 --> 00:46.380
and different than it was like with 4.0.

20
00:46.380 --> 00:47.970
So, they move things a little bit around

21
00:47.970 --> 00:49.440
as they've updated the software,

22
00:49.440 --> 00:51.720
but that's where you go currently in the interface.

23
00:51.720 --> 00:53.640
So, System, Hosts.

24
00:53.640 --> 00:55.385
And currently, it's showing us all the clusters

25
00:55.385 --> 00:58.080
that it knows about courtesy of vCenter.

26
00:58.080 --> 01:01.260
So, we integrated a compute manager in an earlier step
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
00:58.080 --> 01:01.260
So, we integrated a compute manager in an earlier step

27
01:01.260 --> 01:03.000
and as a result of vCenter

28
01:03.000 --> 01:05.400
and the integration there between NSX and vCenter,

29
01:05.400 --> 01:07.920
that's why it knows that these hosts exist.

30
01:07.920 --> 01:10.950
So, we wanna configure NSX on these two hosts.

31
01:10.950 --> 01:13.200
So, if we wanted to do them in one fell swoop,

32
01:13.200 --> 01:16.290
what we could do is we could go to Transport Node Profiles,

33
01:16.290 --> 01:18.090
click on add Transport Node Profile,

34
01:18.090 --> 01:20.186
and then put all the details here.

35
01:20.186 --> 01:22.860
And then, simply when we bring the whole cluster in,

36
01:22.860 --> 01:24.660
specify this Transport Node Profile.

37
01:24.660 --> 01:26.040
However, for the demo,

38
01:26.040 --> 01:29.160
what I'd like to do is walk through this one by one.

39
01:29.160 --> 01:31.110
And that way, we can also specify
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:29.160 --> 01:31.110
And that way, we can also specify

40
01:31.110 --> 01:34.050
individual Uplink Profiles, one for ESXi-A

41
01:34.050 --> 01:35.940
and a different one for ESXi-B,

42
01:35.940 --> 01:39.030
which include different subnets and different VLANs.

43
01:39.030 --> 01:39.870
So, that's what we're gonna do here.

44
01:39.870 --> 01:40.703
So, lemme go ahead

45
01:40.703 --> 01:42.780
and minimize this on the left to move it over a little bit.

46
01:42.780 --> 01:43.710
Gives us a little more room.

47
01:43.710 --> 01:46.230
And so, instead of clicking here and saying,

48
01:46.230 --> 01:48.690
I want to configure NSX for the entire cluster,

49
01:48.690 --> 01:51.930
I'm gonna go ahead and start with ESXi-A by selecting that.

50
01:51.930 --> 01:54.330
And then, with ESXi-A selected right there,

51
01:54.330 --> 01:56.490
we'll click configure NSX.

52
01:56.490 --> 01:58.260
So, now, it's walking us through the wizard.

53
01:58.260 --> 01:59.339
So, we'll click on next.

54
01:59.339 --> 02:00.450
It's asking us
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
01:59.339 --> 02:00.450
It's asking us

55
02:00.450 --> 02:03.660
about which distributed switch in vSphere we wanna use.

56
02:03.660 --> 02:04.950
So, currently, we have a visual

57
02:04.950 --> 02:06.360
over here on the right. (chuckles)

58
02:06.360 --> 02:08.580
So, we'll click on add host switch,

59
02:08.580 --> 02:09.600
and then from the dropdown,

60
02:09.600 --> 02:12.330
we'll specify the distributed switch we wanna use.

61
02:12.330 --> 02:14.070
So, the VDS for management,

62
02:14.070 --> 02:15.690
we're using that for management only.

63
02:15.690 --> 02:17.220
And the DS for NSX,

64
02:17.220 --> 02:19.410
that's the distributed switch we just created.

65
02:19.410 --> 02:22.440
That's the one we wanna use as part of NSX.

66
02:22.440 --> 02:24.060
And then, for the transport zones,

67
02:24.060 --> 02:25.590
we'll go ahead and click here.

68
02:25.590 --> 02:28.680
And we are gonna use our A-B Overlay transport zone.

69
02:28.680 --> 02:30.360
So, when we configure host B,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

69
02:28.680 --> 02:30.360
So, when we configure host B,

70
02:30.360 --> 02:32.040
we'll also have it included

71
02:32.040 --> 02:33.683
in supporting this transport zone.

72
02:33.683 --> 02:35.940
And we could add multiple transport zones

73
02:35.940 --> 02:38.010
that this ESXi host is gonna support.

74
02:38.010 --> 02:39.450
I'll just use this one for now.

75
02:39.450 --> 02:42.000
And then, for the Uplink Profile, we'll click here.

76
02:42.000 --> 02:43.590
And we'll specify the Uplink Profile

77
02:43.590 --> 02:45.240
we wanna use with E ESXi-A,

78
02:45.240 --> 02:47.730
which is gonna use vmnic 2 as the active uplink

79
02:47.730 --> 02:50.670
and vmnic 3 as the standby.

80
02:50.670 --> 02:53.460
It's also gonna be using VLAN 101 for its transport,

81
02:53.460 --> 02:56.460
and that's all configured as part of the Uplink Profile.

82
02:56.460 --> 02:58.140
So, we'll select that Uplink Profile,

83
02:58.140 --> 02:59.640
and then we'll continue configuring.

84
02:59.640 --> 03:01.410
So, as far as the IP address type,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
02:59.640 --> 03:01.410
So, as far as the IP address type,

85
03:01.410 --> 03:04.560
we want IPv4 or IPv6 for the tunnel endpoint.

86
03:04.560 --> 03:06.240
And we're gonna be using IPv4.

87
03:06.240 --> 03:07.470
And now, it says, okay, great,

88
03:07.470 --> 03:09.240
what kind of IP address do you wanna use?

89
03:09.240 --> 03:11.880
Do you wanna use an IP address from a pool?

90
03:11.880 --> 03:13.140
So, we could pull from our pool,

91
03:13.140 --> 03:16.230
for example, the Pool 10.11.11.11.

92
03:16.230 --> 03:18.060
Or we could say, you know what?

93
03:18.060 --> 03:21.120
I wanna go ahead and use a static IP address,

94
03:21.120 --> 03:22.740
and then just configure it right here.

95
03:22.740 --> 03:24.030
So, initially, I'd like to go ahead

96
03:24.030 --> 03:27.870
and use a static IP address of 10.11.11.11.

97
03:27.870 --> 03:29.430
So, that way, when we see it, we'll know,

98
03:29.430 --> 03:33.360
oh, that is the tunnel endpoint for ESXi-A.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

98
03:29.430 --> 03:33.360
oh, that is the tunnel endpoint for ESXi-A.

99
03:33.360 --> 03:34.267
It'll be very clear,

100
03:34.267 --> 03:36.540
because it'll be the only tunnel endpoint

101
03:36.540 --> 03:39.240
in that subnet of 10.11.11.

102
03:39.240 --> 03:40.530
So, if we hit the Tab key

103
03:40.530 --> 03:44.610
and now wants to know the default gateway, so 10.11.11.1.

104
03:44.610 --> 03:47.220
That's my layer three logical IP address

105
03:47.220 --> 03:50.430
on the multilayer switch that ESXi-A can go ahead and use

106
03:50.430 --> 03:53.070
for routing to reach the other tunnel endpoint,

107
03:53.070 --> 03:55.080
which will be on ESXi-B.

108
03:55.080 --> 03:57.630
And then, for the mask, it's a 24 bit mask that we're using.

109
03:57.630 --> 03:59.520
So, we'll put that in in dotted decimal.

110
03:59.520 --> 04:00.421
And then, we'll scroll down.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

110
03:59.520 --> 04:00.421
And then, we'll scroll down.

111
04:00.421 --> 04:02.130
And now, here is where we're going

112
04:02.130 --> 04:04.470
to associate the two network interface cards.

113
04:04.470 --> 04:07.680
So, these labels right here are the two labels

114
04:07.680 --> 04:10.020
that we used as part of our Uplink Profile.

115
04:10.020 --> 04:12.030
And these here represent the labels

116
04:12.030 --> 04:13.650
that we have on the distributed switch.

117
04:13.650 --> 04:17.850
So, for vmnic 2, I wanna go ahead and use DS vmnic 2.

118
04:17.850 --> 04:20.250
That's the label for the first uplink

119
04:20.250 --> 04:21.420
on the distributed switch.

120
04:21.420 --> 04:25.500
And we're gonna use DS vmnic 3 as the second uplink.

121
04:25.500 --> 04:27.660
So, again, these are the labels here on the left

122
04:27.660 --> 04:29.850
from the actual Uplink Profile,

123
04:29.850 --> 04:31.020
and these are the labels
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

123
04:29.850 --> 04:31.020
and these are the labels

124
04:31.020 --> 04:33.600
of the uplinks in the distributed switch.

125
04:33.600 --> 04:35.190
And so, we're mapping them together.

126
04:35.190 --> 04:37.770
And we'll scroll down, and then we'll click on add.

127
04:37.770 --> 04:40.890
So, that add was for the mapping of the VDS uplinks

128
04:40.890 --> 04:43.947
to the actual uplinks inside of the Uplink Profile in NSX.

129
04:43.947 --> 04:45.510
And then, over here on the right, check it out.

130
04:45.510 --> 04:48.090
It gives us a beautiful diagram of exactly that.

131
04:48.090 --> 04:50.370
So, it's showing us the labels here.

132
04:50.370 --> 04:52.560
And these labels on the bottom are the labels in NSX.

133
04:52.560 --> 04:54.630
And the labels above that are the labels

134
04:54.630 --> 04:56.910
associated with the actual distributed switch itself.

135
04:56.910 --> 05:00.150
All right, so we'll click on finish and it is on its way.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

135
04:56.910 --> 05:00.150
All right, so we'll click on finish and it is on its way.

136
05:00.150 --> 05:01.260
So, for ESXi-A,

137
05:01.260 --> 05:04.140
if we click right here on the NSX Configuration section,

138
05:04.140 --> 05:07.290
it's at 6% and it's gonna go through this entire list

139
05:07.290 --> 05:08.760
as it does the configuration.

140
05:08.760 --> 05:10.741
I say it, as NSX Manager

141
05:10.741 --> 05:15.390
implements this configuration over on ESXi-A.

142
05:15.390 --> 05:17.700
So, I'm gonna repeat the process for ESXi-B,

143
05:17.700 --> 05:20.310
except we're gonna simply use a different Uplink Profile,

144
05:20.310 --> 05:23.160
but we'll use the one that we created just for ESXi-B.

145
05:23.160 --> 05:24.657
So, we'll select ESXi-B,

146
05:24.657 --> 05:27.330
we'll click here on configure NSX,

147
05:27.330 --> 05:29.520
and then we'll go through the menu here as well.

148
05:29.520 --> 05:31.200
We can do this one a little bit faster.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

148
05:29.520 --> 05:31.200
We can do this one a little bit faster.

149
05:31.200 --> 05:33.420
So, we'll specify the host switch.

150
05:33.420 --> 05:35.057
We wanna use the DS for NSX.

151
05:35.057 --> 05:38.160
We wanna go ahead and support this transport zone.

152
05:38.160 --> 05:41.610
We wanna use this Uplink Profile called ESXi-B.

153
05:41.610 --> 05:44.580
And for the IP dressing, we wanna use a static address.

154
05:44.580 --> 05:47.340
And then, for the IP address for ESXi-B,

155
05:47.340 --> 05:50.310
we're gonna use 10.22.22.22.

156
05:50.310 --> 05:53.960
And then, the default gateway is gonna be 10.22.22.1.

157
05:54.900 --> 05:57.240
And the subnet mask is a 24 bit mask,

158
05:57.240 --> 05:58.650
so we'll put that in as well.

159
05:58.650 --> 06:00.960
Then, we'll scroll down and then we'll do the mappings here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

159
05:58.650 --> 06:00.960
Then, we'll scroll down and then we'll do the mappings here.

160
06:00.960 --> 06:04.488
So, on the Uplink Profile for ESXi-B,

161
06:04.488 --> 06:07.500
I call the two uplink labels dos and tres.

162
06:07.500 --> 06:09.750
And now, here, we'll specify the actual uplinks

163
06:09.750 --> 06:10.860
on the distributed switch

164
06:10.860 --> 06:12.810
that we wanna map to those uplinks.

165
06:12.810 --> 06:17.220
So, I'm gonna use vmnic 2 and vmnic 3 and click on add.

166
06:17.220 --> 06:18.750
And then, it gives us the graphic over here on the right.

167
06:18.750 --> 06:21.120
Fantastic. And we'll click on finish.

168
06:21.120 --> 06:22.650
All right, so it is on its way.

169
06:22.650 --> 06:24.270
So, it is at this step

170
06:24.270 --> 06:25.770
and it'll be going through all these steps as well.

171
06:25.770 --> 06:27.390
Now, once it's done,

172
06:27.390 --> 06:31.050
it's gonna create new VMkernel adapters on our ESXi host
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

172
06:27.390 --> 06:31.050
it's gonna create new VMkernel adapters on our ESXi host

173
06:31.050 --> 06:34.050
that will act as the logical layer three endpoint

174
06:34.050 --> 06:36.150
for the tunnels with the IP addresses

175
06:36.150 --> 06:38.280
that we specified as part of the configurations.

176
06:38.280 --> 06:40.440
So, if we popped over to the vSphere client

177
06:40.440 --> 06:43.239
and we went to our host, let's go to ESXi-A

178
06:43.239 --> 06:45.060
and let's go to Configure.

179
06:45.060 --> 06:47.010
And let's take a look at VMkernel adapters.

180
06:47.010 --> 06:49.380
Currently, it has two VMkernel adapters.

181
06:49.380 --> 06:51.060
One I'm using for management,

182
06:51.060 --> 06:53.670
one I'm using for access to an iSCSI data store.

183
06:53.670 --> 06:56.250
And if we look at ESXi-B, very similar,

184
06:56.250 --> 06:58.350
it's got one VMkernel adapter zero

185
06:58.350 --> 07:00.330
associated with its management IP address,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

185
06:58.350 --> 07:00.330
associated with its management IP address,

186
07:00.330 --> 07:03.690
another vmk1 that's associated with the iSCS network

187
07:03.690 --> 07:05.880
for access to the iSCS data store.

188
07:05.880 --> 07:07.830
However, when NSX is done

189
07:07.830 --> 07:09.900
with the configuration on these two hosts,

190
07:09.900 --> 07:11.853
effectively making them host transport nodes,

191
07:11.853 --> 07:14.256
it's gonna have additional VMkernel adapters

192
07:14.256 --> 07:17.220
on each one of them, including a VMkernel adapter.

193
07:17.220 --> 07:18.960
I think it starts with vmk10.

194
07:18.960 --> 07:21.120
It's gonna have a VMkernel adapter of 10

195
07:21.120 --> 07:22.860
with the address that we signed for the tap.

196
07:22.860 --> 07:23.880
So, for ESXi-A,

197
07:23.880 --> 07:27.210
it's gonna be a new VMkernel adapter with 10.11.11.11.

198
07:27.210 --> 07:30.480
And for ESXi-B, it's gonna be a new VMkernel adapter
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

198
07:27.210 --> 07:30.480
And for ESXi-B, it's gonna be a new VMkernel adapter

199
07:30.480 --> 07:34.200
with the IP address of 10.22.22.22.

200
07:34.200 --> 07:35.843
So, whenever those ESXi hosts need to send traffic

201
07:35.843 --> 07:37.410
to send through their tunnel,

202
07:37.410 --> 07:39.120
they'll be using the layer three interfaces

203
07:39.120 --> 07:41.190
associated with the tunnel endpoints

204
07:41.190 --> 07:43.620
or the tunneling of the traffic between the two hosts.

205
07:43.620 --> 07:46.410
So, if we hop back to the NSX Manager,

206
07:46.410 --> 07:48.210
let me expand the left-hand column real quick.

207
07:48.210 --> 07:49.980
Just to remind us where we would configure this,

208
07:49.980 --> 07:53.640
we go to System, on the left under Fabric, go to Hosts,

209
07:53.640 --> 07:56.070
and then click on the ESXi host you wanna configure,

210
07:56.070 --> 07:58.740
and then click on configure NSX and you're off to the races.

211
07:58.740 --> 08:00.810
Now, in the event that you do wanna do a whole cluster
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

211
07:58.740 --> 08:00.810
Now, in the event that you do wanna do a whole cluster

212
08:00.810 --> 08:03.030
at the same time, you can simply put a check mark

213
08:03.030 --> 08:05.940
next to the cluster, click on configure NSX.

214
08:05.940 --> 08:08.730
It'll ask us what Transport Node Profiles we wanna use.

215
08:08.730 --> 08:10.500
We could actually create one right here

216
08:10.500 --> 08:11.880
by clicking on Create New,

217
08:11.880 --> 08:13.830
or we could use one that we already created.

218
08:13.830 --> 08:15.690
And effectively, the Transport Node Profile

219
08:15.690 --> 08:19.560
has all the details such as the Uplink Profile to use,

220
08:19.560 --> 08:21.210
which distributed switch to use,

221
08:21.210 --> 08:25.256
the mappings between the distributed switch, uplink ports,

222
08:25.256 --> 08:27.568
and the uplinks as part of the Uplink Profile.

223
08:27.568 --> 08:30.300
So, we could pre-configure all of that right here,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

223
08:27.568 --> 08:30.300
So, we could pre-configure all of that right here,

224
08:30.300 --> 08:33.120
and then use that when we're configuring a cluster.

225
08:33.120 --> 08:35.580
In fact, while we're waiting for the deployment to finish,

226
08:35.580 --> 08:37.530
let's just create a transport node profile,

227
08:37.530 --> 08:38.610
so you can see what it looks like.

228
08:38.610 --> 08:42.780
So, we'll call this a TP for transport profile for cluster.

229
08:42.780 --> 08:45.026
And then, regarding the host switch we're gonna use,

230
08:45.026 --> 08:47.400
we'll go ahead and click on add to add one.

231
08:47.400 --> 08:49.980
We'll specify that we're gonna use our vCenter.

232
08:49.980 --> 08:51.930
Then, we'll specify the DS for NSX,

233
08:51.930 --> 08:53.850
same exact type of information

234
08:53.850 --> 08:56.370
we supplied individually for each of our ESXi hosts.

235
08:56.370 --> 08:58.770
But now, we're doing it in a profile that we could use,

236
08:58.770 --> 08:59.910
sort of like a template

237
08:59.910 --> 09:01.680
to do a whole bunch of hosts at the same time.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

237
08:59.910 --> 09:01.680
to do a whole bunch of hosts at the same time.

238
09:01.680 --> 09:04.200
Then, for the transport zones, we could say we want,

239
09:04.200 --> 09:05.730
based on this template, if it's used,

240
09:05.730 --> 09:08.028
to use that transport zone or support that transport zone.

241
09:08.028 --> 09:10.170
We could then select the Uplink Profile.

242
09:10.170 --> 09:12.540
So, we choose the Uplink Profile we want them to use.

243
09:12.540 --> 09:14.036
And then, based on that Uplink Profile,

244
09:14.036 --> 09:16.950
we could go ahead and specify the uplinks we wanna use.

245
09:16.950 --> 09:21.030
So, there's DS vmnic 2 and DS vmnic 3.

246
09:21.030 --> 09:23.670
For the labels on the Uplink Profile of 2 and 3.

247
09:23.670 --> 09:25.050
And because in this Uplink Profile,

248
09:25.050 --> 09:27.930
we have two active uplinks, if we use this,

249
09:27.930 --> 09:30.570
it would have two tunnel endpoint addresses
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

249
09:27.930 --> 09:30.570
it would have two tunnel endpoint addresses

250
09:30.570 --> 09:32.940
for each of the hosts that we apply this to.

251
09:32.940 --> 09:34.800
And then, for IPv4 address assignment,

252
09:34.800 --> 09:36.630
because as a template, we don't have the option

253
09:36.630 --> 09:38.220
of a static address assignment,

254
09:38.220 --> 09:39.480
because we're gonna be applying this

255
09:39.480 --> 09:40.770
to a whole bunch at the same time.

256
09:40.770 --> 09:43.260
So, we can say, please use the IPv4 pool.

257
09:43.260 --> 09:44.940
And then if we use that option,

258
09:44.940 --> 09:46.860
choose the pool we wanna pull from.

259
09:46.860 --> 09:48.630
And then, we did the mappings right here.

260
09:48.630 --> 09:50.520
And then, we'll go ahead and click on add,

261
09:50.520 --> 09:53.370
and then click on apply and click on save.

262
09:53.370 --> 09:55.440
So, now, we have this transport profile set up

263
09:55.440 --> 09:56.850
with a lot of those questions answered.

264
09:56.850 --> 09:59.081
So, if we went back to our clusters in the future,

265
09:59.081 --> 10:01.928
if we wanna configure a cluster, for example,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

265
09:59.081 --> 10:01.928
if we wanna configure a cluster, for example,

266
10:01.928 --> 10:03.210
let's say we wanna configure

267
10:03.210 --> 10:05.010
all the devices in this management cluster.

268
10:05.010 --> 10:07.388
We put a checkbox here for the management cluster,

269
10:07.388 --> 10:09.194
click on configure NSX.

270
10:09.194 --> 10:12.390
It's gonna ask us which Transport Node Profile we wanna use.

271
10:12.390 --> 10:14.700
We'll select that one. Then, we click on save.

272
10:14.700 --> 10:16.837
And then, it would apply those settings

273
10:16.837 --> 10:18.970
that we have in that transport profile

274
10:18.970 --> 10:21.660
to all of the hosts in that cluster.

275
10:21.660 --> 10:23.190
So, for our demo, I don't wanna configure

276
10:23.190 --> 10:24.480
any of the two ESXi hosts

277
10:24.480 --> 10:26.520
in our management cluster with NSX,

278
10:26.520 --> 10:28.890
because we're gonna save that just for the two

279
10:28.890 --> 10:31.380
that are in the host transport nodes cluster.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

279
10:28.890 --> 10:31.380
that are in the host transport nodes cluster.

280
10:31.380 --> 10:32.550
So, we'll let that completely finish.

281
10:32.550 --> 10:34.680
Looks like ESXi-A is mostly done.

282
10:34.680 --> 10:36.870
Now, currently, the status here shows as Unknowns.

283
10:36.870 --> 10:37.920
We'll click on refresh.

284
10:37.920 --> 10:39.540
And what we're looking for

285
10:39.540 --> 10:41.250
is we want green across the board here

286
10:41.250 --> 10:44.100
for the NSX configuration and also for the status.

287
10:44.100 --> 10:45.930
So, it may take 15 to 20 minutes

288
10:45.930 --> 10:48.420
to fully initialize and be ready to go.

289
10:48.420 --> 10:50.416
We could also scroll to the right,

290
10:50.416 --> 10:53.130
and there's an option here for View Details.

291
10:53.130 --> 10:55.380
So, if we click on that, it's looking pretty positive.

292
10:55.380 --> 10:56.430
It's getting closer and closer.

293
10:56.430 --> 10:59.070
So, here's the name and the IP addresses involved.

294
10:59.070 --> 11:02.700
So, this address right here, the 10.11.11.11,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

294
10:59.070 --> 11:02.700
So, this address right here, the 10.11.11.11,

295
11:02.700 --> 11:04.530
that's the tunnel endpoint address.

296
11:04.530 --> 11:06.900
This can be used for the GENEVE tunnel.

297
11:06.900 --> 11:08.310
And then, over here, we have a nice visual.

298
11:08.310 --> 11:09.990
So, if we scroll to the right a little bit,

299
11:09.990 --> 11:11.850
it's gonna show us the switch we're using,

300
11:11.850 --> 11:12.780
the vSphere switch,

301
11:12.780 --> 11:15.810
the distributed switch we're using as part of NSX.

302
11:15.810 --> 11:17.670
It's also showing us the uplinks.

303
11:17.670 --> 11:19.470
So, here we have the two labels

304
11:19.470 --> 11:22.320
for Use-vmnic-2 and Standby-3.

305
11:22.320 --> 11:24.540
And specifically, they're being mapped to the uplinks

306
11:24.540 --> 11:29.094
that lead to vmnic 2 and vmnic 3 on ESXi-A.

307
11:29.094 --> 11:30.030
And then, if we click on Monitor,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

307
11:29.094 --> 11:30.030
And then, if we click on Monitor,

308
11:30.030 --> 11:32.880
it shows us details about that ESXi host,

309
11:32.880 --> 11:34.110
including system memory

310
11:34.110 --> 11:36.990
and connectivity to the NSX controller.

311
11:36.990 --> 11:37.823
And that's all great.

312
11:37.823 --> 11:40.140
Now, also because it is mostly configured,

313
11:40.140 --> 11:42.750
oh, look at that, says Down, let's click on refresh here.

314
11:42.750 --> 11:44.730
So, what we're looking for is Success and Up.

315
11:44.730 --> 11:48.720
So, looks like it's completely done for both ESXi hosts.

316
11:48.720 --> 11:50.670
So for it's IP dresses, if we click here,

317
11:50.670 --> 11:52.410
it's gonna show us the IP addresses in use.

318
11:52.410 --> 11:53.243
So, that's an IP address

319
11:53.243 --> 11:55.740
it has on its management interface on vmk0.

320
11:55.740 --> 11:56.610
This is an IP address

321
11:56.610 --> 11:59.820
that I have associated with vmk1 for iSCSI access.

322
11:59.820 --> 12:01.410
And this is the IP address
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

322
11:59.820 --> 12:01.410
And this is the IP address

323
12:01.410 --> 12:03.570
that it has on the new VMkernel adapter

324
12:03.570 --> 12:06.600
that NSX deployed on this ESXi host.

325
12:06.600 --> 12:08.670
So, if we're gonna do the same thing for ESXi-B

326
12:08.670 --> 12:11.400
and click here on 1 more, it should have that IP address

327
12:11.400 --> 12:14.490
for its tunnel endpoint at 10.22.22.22.

328
12:14.490 --> 12:16.410
And if we go over to the vSphere client for a moment

329
12:16.410 --> 12:17.790
and take a look at those two hosts,

330
12:17.790 --> 12:20.910
if we click on ESXi-A and click on Configure

331
12:20.910 --> 12:22.230
and VMkernel adapters,

332
12:22.230 --> 12:26.220
there we have vmk10 with the IP address, 10.11.11.11.

333
12:26.220 --> 12:27.424
And if we go to ESXi-B,

334
12:27.424 --> 12:31.050
there's its IP address of 10.22.22.22.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

334
12:27.424 --> 12:31.050
there's its IP address of 10.22.22.22.

335
12:31.050 --> 12:32.728
So, if we go back to the NSX Manager,

336
12:32.728 --> 12:34.110
and now under System,

337
12:34.110 --> 12:36.480
if we clicked on System Overview here on the left,

338
12:36.480 --> 12:39.720
we now have still one NSX management node,

339
12:39.720 --> 12:42.540
and now we have two host transport nodes,

340
12:42.540 --> 12:47.540
and that's ESXi-A and ESXi-B, which are ready to rock.

341
12:47.550 --> 12:49.800
Now, the challenge is with these hosts,

342
12:49.800 --> 12:52.740
if we click on host here on the left-hand side under fabric,

343
12:52.740 --> 12:55.740
and we expand the host transport nodes cluster,

344
12:55.740 --> 12:57.510
even though they have their tunnel endpoints,

345
12:57.510 --> 12:58.530
check this out.

346
12:58.530 --> 13:01.320
Under Tunnels, it says tunnels Not Available.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

346
12:58.530 --> 13:01.320
Under Tunnels, it says tunnels Not Available.

347
13:01.320 --> 13:02.250
Now, one of the reasons

348
13:02.250 --> 13:03.750
there may not be any tunnels in place

349
13:03.750 --> 13:06.240
is because we don't need any tunnels at the moment.

350
13:06.240 --> 13:08.820
We don't have any NSX overlay segments.

351
13:08.820 --> 13:11.160
We don't have any VMs connected to those segments.

352
13:11.160 --> 13:12.450
So, the ESXi hosts are saying,

353
13:12.450 --> 13:14.210
well, you know, we have the tunnel endpoints.

354
13:14.210 --> 13:15.660
We could build the tunnels,

355
13:15.660 --> 13:17.280
but we really don't need to at this point,

356
13:17.280 --> 13:20.850
until we have a NSX overlay segment to support.

357
13:20.850 --> 13:23.130
And have no fear, because in the next skill,

358
13:23.130 --> 13:24.430
we'll walk through the process

359
13:24.430 --> 13:27.510
of creating a segment, an overlay segment,

360
13:27.510 --> 13:29.730
putting some VMs on that segment,

361
13:29.730 --> 13:31.620
and take a look at that tunnel take off.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

361
13:29.730 --> 13:31.620
and take a look at that tunnel take off.

362
13:31.620 --> 13:33.180
We'll also have a better opportunity

363
13:33.180 --> 13:36.240
once we create a segment to analyze the traffic flow

364
13:36.240 --> 13:38.190
as traffic is being sent back and forth

365
13:38.190 --> 13:41.130
between two ESXi transport nodes

366
13:41.130 --> 13:44.073
in an NSX environment using a GENEVE tunnel.