WEBVTT

1
00:00.240 --> 00:01.560
So now that we've verified

2
00:01.560 --> 00:02.850
our infrastructure,

3
00:02.850 --> 00:06.570
our next step is to deploy the first NSX manager,

4
00:06.570 --> 00:07.650
which we're gonna do right here

5
00:07.650 --> 00:10.200
with this name NSX-mgr-11.

6
00:10.200 --> 00:12.930
And we'll have it use the IP address of .11.

7
00:12.930 --> 00:16.080
So as a starting point for this, I downloaded the image,

8
00:16.080 --> 00:19.590
the OVA image to my local management computer,

9
00:19.590 --> 00:21.420
and I have a license that we're gonna use a little bit later

10
00:21.420 --> 00:23.250
in the steps here that I got as part

11
00:23.250 --> 00:25.140
of my VM mug Advantage membership.

12
00:25.140 --> 00:27.510
So we're gonna take this VM template here that we got

13
00:27.510 --> 00:31.890
as an OVA file and deploy it right here on ESXi-C.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:27.510 --> 00:31.890
as an OVA file and deploy it right here on ESXi-C.

14
00:31.890 --> 00:33.090
So back here in the vSphere Client,

15
00:33.090 --> 00:35.430
we could either be here in the host and clusters view,

16
00:35.430 --> 00:37.590
or the VM and templates view either way is great.

17
00:37.590 --> 00:40.280
And I wanna put the new VM in the LV-DataCenter.

18
00:40.280 --> 00:41.580
So I'll right click on that.

19
00:41.580 --> 00:44.100
And from the dropdown, we'll choose this bad boy right here,

20
00:44.100 --> 00:46.080
deploy OVF template.

21
00:46.080 --> 00:47.850
And now it's asking us if we wanna reach out

22
00:47.850 --> 00:49.260
over the network and grab this file.

23
00:49.260 --> 00:50.430
Or do you have it locally?

24
00:50.430 --> 00:53.400
So because I already downloaded the OVA CD on my local

25
00:53.400 --> 00:56.280
file system, I'm gonna click right here, local file,

26
00:56.280 --> 00:58.500
and then click right here, upload files to identify

27
00:58.500 --> 01:00.390
where it is on my local file system.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
00:58.500 --> 01:00.390
where it is on my local file system.

28
01:00.390 --> 01:04.680
So here I have a couple of 'em, one is 4.1.0 is 4.1.1

29
01:04.680 --> 01:06.900
that's the latest and greatest as of this recording.

30
01:06.900 --> 01:09.169
So I'll grab this one right here.

31
01:09.169 --> 01:10.590
There's the name of the actual file

32
01:10.590 --> 01:12.360
and I'll click on next to continue.

33
01:12.360 --> 01:16.020
So let's call this nsx-mgr-demo

34
01:16.020 --> 01:17.580
for the demonstration for the install.

35
01:17.580 --> 01:19.860
And the reason I'm doing it as the name demo

36
01:19.860 --> 01:22.920
is because the actual deployment of this VM,

37
01:22.920 --> 01:26.610
it takes like 30 to 40 minutes for the deployment.

38
01:26.610 --> 01:28.670
And then once it's deployed after you power it on,

39
01:28.670 --> 01:31.920
it takes another 20 or 30 minutes to fully initialize.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:28.670 --> 01:31.920
it takes another 20 or 30 minutes to fully initialize.

40
01:31.920 --> 01:36.120
And so in the wings, I've got a VM all ready to go

41
01:36.120 --> 01:39.720
and it's currently called nsx-mgr-11.

42
01:39.720 --> 01:42.090
So I'm gonna walk through this as a demo

43
01:42.090 --> 01:44.370
and then cut over to the one that's currently installed.

44
01:44.370 --> 01:46.950
All right, so we'll call this one nsx-mgr-demo

45
01:46.950 --> 01:48.210
and we'll click on next.

46
01:48.210 --> 01:50.820
As far as the compute resource, where we want this to live,

47
01:50.820 --> 01:52.230
this new VM to be placed,

48
01:52.230 --> 01:54.810
we wanna be in the management cluster

49
01:54.810 --> 01:58.890
and specifically on ESXi-C based on our plan.

50
01:58.890 --> 02:00.540
And then we'll go ahead and select ESXi-C
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

50
01:58.890 --> 02:00.540
And then we'll go ahead and select ESXi-C

51
02:00.540 --> 02:03.270
as the compute resource and click on next.

52
02:03.270 --> 02:06.540
So it's asking me to now verify the template details.

53
02:06.540 --> 02:09.570
It has some certificates that I can't verify, that's okay.

54
02:09.570 --> 02:11.580
I'll click on ignore all for those.

55
02:11.580 --> 02:13.680
So the publisher is VMware.Inc.

56
02:13.680 --> 02:16.560
The product is nsx-unified-appliance.

57
02:16.560 --> 02:18.360
The version is 411.

58
02:18.360 --> 02:20.880
The download size is about 14 gigs.

59
02:20.880 --> 02:22.830
And then the size on the disc, once it's deployed,

60
02:22.830 --> 02:25.650
it's either gonna be seven gig, which is what I'm gonna do

61
02:25.650 --> 02:28.200
within provisioning or 300 gigs.

62
02:28.200 --> 02:29.610
So in my lab environment, I'm gonna go ahead

63
02:29.610 --> 02:32.820
and use a thin provisioned nsx manager appliance.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
02:29.610 --> 02:32.820
and use a thin provisioned nsx manager appliance.

64
02:32.820 --> 02:34.890
And it's showing us all the details here in our advanced

65
02:34.890 --> 02:36.900
configuration about what comes with this template,

66
02:36.900 --> 02:40.470
including the fact that by default it's not allowing you

67
02:40.470 --> 02:42.900
to take snapshots of the VM.

68
02:42.900 --> 02:44.760
And that's a good thing because if you have two

69
02:44.760 --> 02:46.260
or three in the cluster

70
02:46.260 --> 02:48.480
and they're all synchronizing their database,

71
02:48.480 --> 02:49.800
we don't wanna snapshot one

72
02:49.800 --> 02:52.080
and restore it later, that's gonna cause a problem.

73
02:52.080 --> 02:53.970
All right, so we'll click next to continue

74
02:53.970 --> 02:55.320
and then we're gonna choose the size

75
02:55.320 --> 02:57.720
of our deployment based on what we intend to do.

76
02:57.720 --> 02:59.010
So in a lab environment,

77
02:59.010 --> 03:01.230
if you don't have a lot of resources to play with,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

77
02:59.010 --> 03:01.230
if you don't have a lot of resources to play with,

78
03:01.230 --> 03:02.940
you can choose extra small,

79
03:02.940 --> 03:05.280
which is gonna dedicate two virtual CPUs

80
03:05.280 --> 03:06.750
and eight gigs of ram.

81
03:06.750 --> 03:09.690
And then based on how we per the storage up to 300 gigabytes

82
03:09.690 --> 03:10.523
of storage.

83
03:10.523 --> 03:12.150
And even though it says it's only supportive

84
03:12.150 --> 03:14.100
for the nsx-cloud-service-manager role,

85
03:14.100 --> 03:16.200
it'll also work in a lab environment,

86
03:16.200 --> 03:18.270
even if you just managing your own lab gear.

87
03:18.270 --> 03:20.430
Then we have small, which is using more CPU

88
03:20.430 --> 03:22.980
and more RAM medium, more CPU, more RAM,

89
03:22.980 --> 03:24.870
and large more CPU and more RAM.

90
03:24.870 --> 03:28.110
Now one of the considerations also is that when we deploy,

91
03:28.110 --> 03:31.080
for example, a medium here, as we deploy the second
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
03:28.110 --> 03:31.080
for example, a medium here, as we deploy the second

92
03:31.080 --> 03:33.660
and third NSX manager as part of the cluster,

93
03:33.660 --> 03:36.960
we'd want to use the same sizing for those as well.

94
03:36.960 --> 03:39.330
So I'm gonna go ahead and choose the default option here

95
03:39.330 --> 03:42.480
of Medium, which is gonna allocate six virtual CPUs

96
03:42.480 --> 03:45.090
and 24 gigs of RAM and click on Next.

97
03:45.090 --> 03:46.830
Now it's asking me on that server

98
03:46.830 --> 03:48.660
where I'm gonna be hosting this VM,

99
03:48.660 --> 03:51.090
where do I wanna store the VMs files?

100
03:51.090 --> 03:54.270
So I have a local data store on ESXi-C, I've also got one

101
03:54.270 --> 03:56.550
that's network reachable for the demo here,

102
03:56.550 --> 03:59.070
I'm just gonna use the ESXi-C data store.

103
03:59.070 --> 04:01.710
And I'm also gonna say, please do thin provisioning
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
03:59.070 --> 04:01.710
And I'm also gonna say, please do thin provisioning

104
04:01.710 --> 04:04.200
and not tie up 300 gigabytes of space,

105
04:04.200 --> 04:06.240
but only tie up as much as you really need.

106
04:06.240 --> 04:08.040
So having selected thin provisioning,

107
04:08.040 --> 04:09.540
I'll click on next to continue.

108
04:09.540 --> 04:11.820
Now it's asking us for the management interface,

109
04:11.820 --> 04:14.310
the management network interface on this VM.

110
04:14.310 --> 04:16.260
What port group do we wanna associate it with?

111
04:16.260 --> 04:18.630
So currently, because we only have one port group available

112
04:18.630 --> 04:21.030
called management, which we documented earlier,

113
04:21.030 --> 04:22.710
leads to my management network,

114
04:22.710 --> 04:26.130
this is the port group we're gonna choose and click on okay.

115
04:26.130 --> 04:28.480
Then for the IP addressing, do we want IPv4,

116
04:28.480 --> 04:31.830
IPv6, we're gonna choose IPv4 and click on next.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

116
04:28.480 --> 04:31.830
IPv6, we're gonna choose IPv4 and click on next.

117
04:31.830 --> 04:33.330
And then we're gonna put in passwords

118
04:33.330 --> 04:35.040
for the GRUB Root User.

119
04:35.040 --> 04:36.330
We're also gonna specify a timeout.

120
04:36.330 --> 04:37.470
I'll put 10 seconds there.

121
04:37.470 --> 04:38.940
That way if it's booting up,

122
04:38.940 --> 04:40.680
I need to interrupt the boot menu, I can,

123
04:40.680 --> 04:42.210
I'll get 10 seconds to do it.

124
04:42.210 --> 04:44.940
And then I'm gonna supply a System Root User password

125
04:44.940 --> 04:49.410
and an admin user password and an audit user password.

126
04:49.410 --> 04:52.440
And I'll use the default CLI names of admin and audit.

127
04:52.440 --> 04:54.150
So lemme go ahead and scroll back to the top

128
04:54.150 --> 04:55.680
and put those details in.

129
04:55.680 --> 04:58.350
All right, so the password for the GRUB Root User are in.

130
04:58.350 --> 05:01.710
Also this little icon here is for my local password manager.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

130
04:58.350 --> 05:01.710
Also this little icon here is for my local password manager.

131
05:01.710 --> 05:03.240
That's just part of my browser.

132
05:03.240 --> 05:04.320
So I'll scroll down.

133
05:04.320 --> 05:06.540
And for the system root user,

134
05:06.540 --> 05:08.520
I'll put it in a password there as well

135
05:08.520 --> 05:10.320
and confirm that password.

136
05:10.320 --> 05:12.390
So if you ever need to do N-S-X-C-L-I commands

137
05:12.390 --> 05:15.510
or NSX related commands, we'd wanna log in as admin

138
05:15.510 --> 05:17.310
to do that and not as root.

139
05:17.310 --> 05:19.800
So lemme go down and put in the passwords.

140
05:19.800 --> 05:21.870
And now we have a password for the audit user.

141
05:21.870 --> 05:23.970
So I'll supply that and confirm it as well.

142
05:23.970 --> 05:26.460
I'll use the default names, I won't change those.

143
05:26.460 --> 05:27.870
And then for optional parameters,

144
05:27.870 --> 05:29.220
it says for internal use only.

145
05:29.220 --> 05:31.950
So I'll leave those alone, then we'll scroll down
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

145
05:29.220 --> 05:31.950
So I'll leave those alone, then we'll scroll down

146
05:31.950 --> 05:34.050
and that wants a host name for this VM.

147
05:34.050 --> 05:36.570
So I'll call this nsx-mgr-demo.

148
05:36.570 --> 05:39.390
And then for the role, do we want it to be an NSX manager?

149
05:39.390 --> 05:40.620
In our case, we do.

150
05:40.620 --> 05:43.260
Or if we wanted to be a NSX Cloud Service Manager,

151
05:43.260 --> 05:44.190
we could specify that.

152
05:44.190 --> 05:46.200
Or if we're implementing NSX federations,

153
05:46.200 --> 05:48.810
we would choose the NSX global manager role.

154
05:48.810 --> 05:51.120
So in our case, we're gonna use NSX manager

155
05:51.120 --> 05:52.440
and then we're gonna give the IP address

156
05:52.440 --> 05:53.460
that we wanted to use.

157
05:53.460 --> 05:58.380
And based on our plan, that IP address is 192.168.1.11.

158
05:58.380 --> 06:00.660
So next we'd put in the mask. So that's a 24 bit mask.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

158
05:58.380 --> 06:00.660
So next we'd put in the mask. So that's a 24 bit mask.

159
06:00.660 --> 06:04.650
And then the default gateway is 192.1 68.1.1.

160
06:04.650 --> 06:05.850
And then if we're using IPv6

161
06:05.850 --> 06:09.120
we'd put in the IPv6 address and the prefix length here

162
06:09.120 --> 06:10.830
and the IPv6 default gateway.

163
06:10.830 --> 06:12.960
But just be aware that if you're using IPv6

164
06:12.960 --> 06:15.510
we'd also wanna have those quad A records

165
06:15.510 --> 06:19.680
and the pointer records for reverse lookups also set in DNS.

166
06:19.680 --> 06:21.990
So for our deployment, we're not gonna be using IPv6

167
06:21.990 --> 06:23.460
we're just using IPv4.

168
06:23.460 --> 06:24.930
So we'll continue to scroll down.

169
06:24.930 --> 06:27.270
And now it's asking us for the DNS server information,

170
06:27.270 --> 06:30.390
which is 192.168.1.100.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

170
06:27.270 --> 06:30.390
which is 192.168.1.100.

171
06:30.390 --> 06:31.803
And the domain search list is ogit.local.

172
06:31.803 --> 06:34.500
So if the manager's trying to resolve a name

173
06:34.500 --> 06:38.010
and it fails, it'll also tack on ogit.local

174
06:38.010 --> 06:40.350
to the name to try to resolve it again that way.

175
06:40.350 --> 06:41.250
Then we'll scroll down.

176
06:41.250 --> 06:42.450
Here's our NTP setting.

177
06:42.450 --> 06:45.930
So we will specify our same Windows server as an NTP server,

178
06:45.930 --> 06:48.477
192.1.68.1.100.

179
06:48.477 --> 06:49.647
And I'm also gonna enable SSH

180
06:49.647 --> 06:53.310
and I'm also gonna enable Route SSH login as well,

181
06:53.310 --> 06:54.840
even though in a production environment,

182
06:54.840 --> 06:56.640
if you don't need it, don't enable it.

183
06:56.640 --> 06:58.560
But in my lab environment, I'm gonna enable both.

184
06:58.560 --> 07:01.110
And the rest of this says please do not set these
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

184
06:58.560 --> 07:01.110
And the rest of this says please do not set these

185
07:01.110 --> 07:02.520
parameters internal properties.

186
07:02.520 --> 07:05.850
So I won't, and I'll click on next to continue.

187
07:05.850 --> 07:07.890
All right, so here we are at the step nine,

188
07:07.890 --> 07:09.180
the ready to complete.

189
07:09.180 --> 07:11.160
So if we confirm our settings here,

190
07:11.160 --> 07:13.170
there's the management IP address we're gonna use.

191
07:13.170 --> 07:15.450
There's the mask below it, the default gateway,

192
07:15.450 --> 07:20.160
no IPv6 DNS server at 100 NTP server at 100,

193
07:20.160 --> 07:21.387
enabling SSH.

194
07:21.387 --> 07:24.060
And then if this is all correct, we'd click on finish

195
07:24.060 --> 07:26.310
to deploy this to the ESXi-C host

196
07:26.310 --> 07:29.590
that we specified should be the compute resource for this VM
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

197
07:31.125 --> 07:32.221
for this NSX manager.

198
07:32.221 --> 07:33.600
Now, as I mentioned earlier, I already have deployed this

199
07:33.600 --> 07:34.770
and the reason I did it earlier was

200
07:34.770 --> 07:36.840
because this process here takes 30

201
07:36.840 --> 07:38.700
to 45 minutes for the deployment.

202
07:38.700 --> 07:41.790
And then once it's deployed, you then turn on that machine,

203
07:41.790 --> 07:43.680
you power it up, and that takes another 30

204
07:43.680 --> 07:45.630
or 40 minutes to fully initialize.

205
07:45.630 --> 07:47.010
And that's why in the background,

206
07:47.010 --> 07:51.330
I already have an nsx manager that I deployed earlier today

207
07:51.330 --> 07:53.490
where I gave it plenty of time to fully deploy

208
07:53.490 --> 07:55.620
and then I hit the power button powered on.

209
07:55.620 --> 07:58.890
But I have not done anything else besides that.

210
07:58.890 --> 08:01.170
So I'm gonna click on cancel here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

210
07:58.890 --> 08:01.170
So I'm gonna click on cancel here.

211
08:01.170 --> 08:03.870
Let's take a peek over here at NSX managers

212
08:03.870 --> 08:06.180
and there is NSX manager right there.

213
08:06.180 --> 08:08.100
And again, I've done nothing to this.

214
08:08.100 --> 08:10.620
I haven't even logged on, I just deployed it

215
08:10.620 --> 08:12.300
with the steps we just looked at.

216
08:12.300 --> 08:15.180
I went to that VM and hit the power button to turn it on.

217
08:15.180 --> 08:17.043
And that's all I did.