WEBVTT

1
00:00.210 --> 00:01.410
So in this video, I'd like to walk

2
00:01.410 --> 00:02.430
through two things, actually.

3
00:02.430 --> 00:05.940
One is I'd like to set up the virtual IP address of .10

4
00:05.940 --> 00:08.370
on my 192.168.1 management network.

5
00:08.370 --> 00:10.680
And that way when we connect to .10,

6
00:10.680 --> 00:13.530
it can associate that with one of our active NSX Managers.

7
00:13.530 --> 00:16.950
So at the moment, we just have NSX Manager .11,

8
00:16.950 --> 00:21.085
but if we had NSX Manager at .12 and another one at .13,

9
00:21.085 --> 00:24.060
you and I could just connect to that virtual IP address

10
00:24.060 --> 00:25.530
and then automatically in the background,

11
00:25.530 --> 00:27.900
that IP address is being managed and responded to

12
00:27.900 --> 00:30.630
by one of our existing NSX Managers.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:27.900 --> 00:30.630
by one of our existing NSX Managers.

13
00:30.630 --> 00:31.890
And then the second thing I'd like to do,

14
00:31.890 --> 00:34.170
after we set up a virtual IP address and verify that,

15
00:34.170 --> 00:35.220
is I'd also like to walk you

16
00:35.220 --> 00:37.380
through setting up anti-affinity rules

17
00:37.380 --> 00:39.660
so that if we have three NSX Managers

18
00:39.660 --> 00:42.240
as part of our cluster, they each are gonna be running

19
00:42.240 --> 00:44.850
on a separate ESXI host to help make sure

20
00:44.850 --> 00:45.990
they have the resources they need.

21
00:45.990 --> 00:47.370
And then more importantly also,

22
00:47.370 --> 00:48.840
to help with fault tolerance

23
00:48.840 --> 00:51.480
in the event that we lose one of our ESXI hosts

24
00:51.480 --> 00:53.250
or have a network connectivity problem

25
00:53.250 --> 00:54.810
with one of our ESXI hosts.

26
00:54.810 --> 00:57.410
So here we are back at the NSX Manager

27
00:57.410 --> 01:00.450
and what we're gonna do is we are gonna go to System
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
00:57.410 --> 01:00.450
and what we're gonna do is we are gonna go to System

28
01:00.450 --> 01:03.750
to specify the virtual IP address for the cluster.

29
01:03.750 --> 01:05.400
So here at System, on the left,

30
01:05.400 --> 01:06.990
we're gonna click down under Configuration

31
01:06.990 --> 01:08.430
and click on Appliances.

32
01:08.430 --> 01:10.950
So as a reminder, if we wanna add additional appliances,

33
01:10.950 --> 01:14.010
we click here, follow the bouncing ball to deploy them.

34
01:14.010 --> 01:15.450
But if we wanna set up a virtual IP address

35
01:15.450 --> 01:16.684
for the cluster as a whole,

36
01:16.684 --> 01:20.100
we simply click right here on SET VIRTUAL IP.

37
01:20.100 --> 01:21.540
So based on our plan,

38
01:21.540 --> 01:25.650
our virtual IP address is gonna be 192.168.1.10,

39
01:25.650 --> 01:27.450
and then we'll go ahead and click on Save.

40
01:27.450 --> 01:29.160
Also, if we're doing IPv6,

41
01:29.160 --> 01:31.740
we'd wanna set up a virtual IPv6 address
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

41
01:29.160 --> 01:31.740
we'd wanna set up a virtual IPv6 address

42
01:31.740 --> 01:33.120
once again for the cluster.

43
01:33.120 --> 01:34.680
But since we're just using IPv4,

44
01:34.680 --> 01:37.410
I'll only specify one virtual IP address for that,

45
01:37.410 --> 01:41.460
and that's the 192.168.1.10, and we'll click on Save.

46
01:41.460 --> 01:43.380
So that's gonna take a few moments

47
01:43.380 --> 01:45.360
to go ahead and crank through that.

48
01:45.360 --> 01:47.130
So we'll give that a moment to complete

49
01:47.130 --> 01:51.030
and then once it's done, we'll reconnect over to .10

50
01:51.030 --> 01:52.650
and verify that we still have connectivity

51
01:52.650 --> 01:54.210
to our NSX Mgmt Cluster.

52
01:54.210 --> 01:58.320
So currently here, still under System, and Appliances,

53
01:58.320 --> 01:59.730
it's showing in Virtual IP now

54
01:59.730 --> 02:02.070
the virtual IP address of .10.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
01:59.730 --> 02:02.070
the virtual IP address of .10.

55
02:02.070 --> 02:05.070
It's also showing us that the NSX Manager

56
02:05.070 --> 02:07.500
that's currently responsible for that virtual IP address

57
02:07.500 --> 02:12.150
and responding to queries on that address, is 192.168.1.11,

58
02:12.150 --> 02:15.780
which is our one and only NSX Manager at the moment.

59
02:15.780 --> 02:17.626
So let me dismiss the message about backups

60
02:17.626 --> 02:20.310
and let's go ahead and reconnect,

61
02:20.310 --> 02:21.210
but this time we'll connect

62
02:21.210 --> 02:24.720
to the virtual IP address of 192.168.1.10.

63
02:24.720 --> 02:26.670
Alright, so we are connecting initially

64
02:26.670 --> 02:28.770
and we don't yet have certificates all dialed in

65
02:28.770 --> 02:29.910
in our NSX environment.

66
02:29.910 --> 02:32.280
So we can't verify the certificate
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
02:29.910 --> 02:32.280
So we can't verify the certificate

67
02:32.280 --> 02:33.750
and that's why my browser is complaining

68
02:33.750 --> 02:36.180
about a certificate that it can't validate.

69
02:36.180 --> 02:39.810
So this is the IP address we're connected to, 192.168.1.10.

70
02:39.810 --> 02:41.400
That's the virtual IP address.

71
02:41.400 --> 02:42.960
So we're gonna click here in Advanced

72
02:42.960 --> 02:45.720
and Proceed, and away we go.

73
02:45.720 --> 02:47.070
So we'll log back in as admin,

74
02:47.070 --> 02:49.560
we'll put in the password, and click LOG IN.

75
02:49.560 --> 02:50.970
Alright, and here we go.

76
02:50.970 --> 02:53.609
So if we went back to System once again,

77
02:53.609 --> 02:57.300
up here on the top, it's giving us a nice system overview.

78
02:57.300 --> 02:59.610
If we click here on the left on Appliances,

79
02:59.610 --> 03:02.160
here under Appliances, it shows that the cluster is stable.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

79
02:59.610 --> 03:02.160
here under Appliances, it shows that the cluster is stable.

80
03:02.160 --> 03:04.020
And once again, we could look at the details

81
03:04.020 --> 03:06.570
for this specific NSX Manager,

82
03:06.570 --> 03:07.860
which is our only one at the moment,

83
03:07.860 --> 03:10.350
by clicking here on VIEW DETAILS just to confirm

84
03:10.350 --> 03:12.150
that everything looks up and operational.

85
03:12.150 --> 03:15.240
And even though I don't have three NSX Managers

86
03:15.240 --> 03:17.130
as part of this cluster, I just have one,

87
03:17.130 --> 03:18.450
I would like to demonstrate

88
03:18.450 --> 03:20.335
how we could set up affinity rules

89
03:20.335 --> 03:23.070
to make sure that our NSX Managers

90
03:23.070 --> 03:25.680
within a cluster are not run on the same host.

91
03:25.680 --> 03:28.050
So to do that, we're gonna go back to the vSphere client

92
03:28.050 --> 03:31.020
to set up our affinity rules, or more accurately,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

92
03:28.050 --> 03:31.020
to set up our affinity rules, or more accurately,

93
03:31.020 --> 03:33.420
we could call them our anti-affinity rules

94
03:33.420 --> 03:34.890
because we wanna make sure that each

95
03:34.890 --> 03:38.070
of the VMs does not run on the same exact host.

96
03:38.070 --> 03:39.360
So I'm gonna go ahead and create

97
03:39.360 --> 03:42.330
just a couple additional VMs as dummy VMs

98
03:42.330 --> 03:43.830
so I can demonstrate the rules.

99
03:43.830 --> 03:46.740
So I'm gonna take a tiny Linux template here

100
03:46.740 --> 03:48.870
and create a new virtual machine from this template.

101
03:48.870 --> 03:50.700
I'm gonna call this nsx-mgr-12

102
03:50.700 --> 03:52.410
although it's not really an NSX Manager,

103
03:52.410 --> 03:54.030
it'll give us the opportunity to work

104
03:54.030 --> 03:55.380
with the affinity rules,

105
03:55.380 --> 03:58.080
and I'm gonna place that in a folder called NSX Managers.

106
03:58.080 --> 03:59.820
Click on NEXT, and as far as

107
03:59.820 --> 04:01.080
where do you wanna process this,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

107
03:59.820 --> 04:01.080
where do you wanna process this,

108
04:01.080 --> 04:03.180
I'm gonna put this in the Mgmt Cluster,

109
04:03.180 --> 04:04.980
but I'm gonna put it on host d.

110
04:04.980 --> 04:08.280
So our original NSX Manager is on host c.

111
04:08.280 --> 04:11.070
I'm gonna put this second NSX Manager on host d

112
04:11.070 --> 04:13.680
and then click on NEXT, specify the data store.

113
04:13.680 --> 04:16.350
I'll go ahead and use the same format as source,

114
04:16.350 --> 04:18.180
click on NEXT, then I wanna customize

115
04:18.180 --> 04:19.530
that VM and power it on.

116
04:19.530 --> 04:21.120
Click on NEXT, and it's currently

117
04:21.120 --> 04:22.740
on the MGMT port group, fantastic.

118
04:22.740 --> 04:24.339
We'll click on NEXT and FINISH.

119
04:24.339 --> 04:25.530
Alright, there it goes.

120
04:25.530 --> 04:28.260
There's our little placeholder for nsx-mgr-12,

121
04:28.260 --> 04:29.970
and we'll right click and create

122
04:29.970 --> 04:31.860
another virtual machine from this template,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

122
04:29.970 --> 04:31.860
another virtual machine from this template,

123
04:31.860 --> 04:34.462
and we'll call this nsx-mgr-13,

124
04:34.462 --> 04:36.540
again, just as a placeholder for a VM

125
04:36.540 --> 04:38.400
so we can demonstrate the affinity rules,

126
04:38.400 --> 04:41.700
and we'll put that in NSX Managers as well, NEXT.

127
04:41.700 --> 04:45.450
So currently, I've got the real NSX Manager on esxi-c.

128
04:45.450 --> 04:47.040
We just put the second one on d.

129
04:47.040 --> 04:48.660
And because I don't have a third host,

130
04:48.660 --> 04:51.270
let me just use a third host out of a different cluster.

131
04:51.270 --> 04:54.030
Let me pick esxi-b, and click on NEXT.

132
04:54.030 --> 04:56.040
Again, just for the demo of having each

133
04:56.040 --> 04:59.490
of the NSX Managers on different ESXi hosts.

134
04:59.490 --> 05:02.550
So we'll go ahead and start off with them on different hosts
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

134
04:59.490 --> 05:02.550
So we'll go ahead and start off with them on different hosts

135
05:02.550 --> 05:06.180
and we'll click on NEXT, and Customize and Power on, NEXT.

136
05:06.180 --> 05:08.220
And it's also in the MGMT network port group.

137
05:08.220 --> 05:10.050
Click on NEXT and FINISH.

138
05:10.050 --> 05:12.227
So now if we look at this folder called NSX Managers

139
05:12.227 --> 05:14.310
and we click on the VMs tab,

140
05:14.310 --> 05:18.240
we currently have these three VMs, 11, 12, and 13,

141
05:18.240 --> 05:20.130
running on three different hosts.

142
05:20.130 --> 05:22.200
And to keep it that way, we go to our cluster

143
05:22.200 --> 05:24.090
and I just realized those are in two different clusters.

144
05:24.090 --> 05:26.520
So let me just choose the Mgmt Cluster as an example.

145
05:26.520 --> 05:30.120
So we'd choose our Mgmt Cluster here and go to Configure,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

145
05:26.520 --> 05:30.120
So we'd choose our Mgmt Cluster here and go to Configure,

146
05:30.120 --> 05:31.350
and in the middle column, we're gonna go down

147
05:31.350 --> 05:34.170
to our VM/Host Rules, and then just create a new rule.

148
05:34.170 --> 05:35.400
So we'll click on ADD,

149
05:35.400 --> 05:39.690
and let's call it NO NSX VMs Together.

150
05:39.690 --> 05:41.010
And for the type, we're gonna go ahead

151
05:41.010 --> 05:43.170
and say Separate Virtual Machines

152
05:43.170 --> 05:44.910
and then we'll specify the virtual machines

153
05:44.910 --> 05:46.560
that we want to have run on separate hosts.

154
05:46.560 --> 05:47.610
So we'll click on ADD.

155
05:47.610 --> 05:50.040
nsx-mgr-13, because it's in a different cluster,

156
05:50.040 --> 05:50.970
isn't even showing up here.

157
05:50.970 --> 05:52.860
So I only have two hosts in this cluster.

158
05:52.860 --> 05:54.930
So this will still work for the demonstration.

159
05:54.930 --> 05:56.910
If we wanna influence DRS and have it

160
05:56.910 --> 05:59.670
not place these two VMs on the same exact host,

161
05:59.670 --> 06:03.390
we select those two VMs, click on OK, and click on OK.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

161
05:59.670 --> 06:03.390
we select those two VMs, click on OK, and click on OK.

162
06:03.390 --> 06:06.629
So now with this rule in place for the Mgmt Cluster,

163
06:06.629 --> 06:08.730
when DRS, Distributed Resource Scheduler,

164
06:08.730 --> 06:11.280
is deciding where those VMs should be put,

165
06:11.280 --> 06:12.420
or in the case of migration,

166
06:12.420 --> 06:13.980
where they should be migrated to,

167
06:13.980 --> 06:16.260
it's going to avoid placing those two VMs

168
06:16.260 --> 06:17.970
on the exact same host.

169
06:17.970 --> 06:19.260
And that's how we can help make sure

170
06:19.260 --> 06:23.131
that we don't accidentally have two or more NSX Managers

171
06:23.131 --> 06:26.280
that are both running on the same computing resource,

172
06:26.280 --> 06:28.920
effectively meaning the same ESXi host.

173
06:28.920 --> 06:30.300
All right, and because I'm not really
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

173
06:28.920 --> 06:30.300
All right, and because I'm not really

174
06:30.300 --> 06:32.460
using nsx-mgr-12 or 13,

175
06:32.460 --> 06:34.530
let me go ahead and delete that rule.

176
06:34.530 --> 06:36.630
I'll say yes to that, and also, let me go

177
06:36.630 --> 06:39.600
to the DataCenter level, go to VMs,

178
06:39.600 --> 06:41.730
and let me select nsx-mgr-12 and 13,

179
06:41.730 --> 06:44.310
those are the bogus ones that are not really NSX Managers.

180
06:44.310 --> 06:46.710
They're just little temporary VMs that I put in place.

181
06:46.710 --> 06:49.440
I'll right click on those, and let me go to Power,

182
06:49.440 --> 06:51.000
and they are running VMware tools.

183
06:51.000 --> 06:53.370
So I'll go ahead and shut down the guest operating system

184
06:53.370 --> 06:54.600
and say yes to that.

185
06:54.600 --> 06:56.220
So in recent tasks, that looks great.

186
06:56.220 --> 06:57.630
Now those two VMs are shut down.

187
06:57.630 --> 06:59.162
I'm also gonna right click for those two VMs

188
06:59.162 --> 07:02.550
and say, please Delete From Disk, click on YES,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

188
06:59.162 --> 07:02.550
and say, please Delete From Disk, click on YES,

189
07:02.550 --> 07:03.900
and that will remove them permanently

190
07:03.900 --> 07:05.070
from our infrastructure.

191
07:05.070 --> 07:07.896
So when we leave this, we now have a single NSX Manager

192
07:07.896 --> 07:10.980
in my lab environment that is currently running

193
07:10.980 --> 07:14.430
on esxi-c, as shown right here.

194
07:14.430 --> 07:15.712
And if you go back to the interface,

195
07:15.712 --> 07:19.110
if we look at the cluster by going to System > Appliances,

196
07:19.110 --> 07:22.290
here is the representation of that NSX Manager.

197
07:22.290 --> 07:23.730
And if we click on VIEW DETAILS,

198
07:23.730 --> 07:24.810
we can confirm that it looks

199
07:24.810 --> 07:26.700
like it's ready to rock and roll.

200
07:26.700 --> 07:29.910
So now that we have an NSX Manager in place,

201
07:29.910 --> 07:31.950
we've verified that it's functional,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

201
07:29.910 --> 07:31.950
we've verified that it's functional,

202
07:31.950 --> 07:34.590
we also linked it with a vCenter server

203
07:34.590 --> 07:36.360
so it could work with that vCenter,

204
07:36.360 --> 07:37.710
what's our next logical step?

205
07:37.710 --> 07:39.390
Well, the next logical step is give it

206
07:39.390 --> 07:41.610
some transport nodes that it can work with.

207
07:41.610 --> 07:43.140
and that's exactly what you and I get

208
07:43.140 --> 07:45.810
to do in the very next skill.

209
07:45.810 --> 07:48.330
So I'll see you over there when you're ready.

210
07:48.330 --> 07:50.820
Until then, I hope this has been informative

211
07:50.820 --> 07:53.313
and I'd like to thank you for viewing.