WEBVTT

1
00:00.000 --> 00:03.400
In this video, we get to deploy the actual automation VM

2
00:03.400 --> 00:05.920
and based on our plan, we are going to place that little

3
00:05.920 --> 00:08.280
automation VM right here on our management network,

4
00:08.280 --> 00:11.880
which is the 101111 network, which is VLAN 11.

5
00:11.880 --> 00:14.320
And we'll use the IP address of .6.

6
00:14.320 --> 00:17.400
Also, it would be super smart just for a moment

7
00:17.400 --> 00:20.460
to just verify that we currently have our NSX manager,

8
00:20.460 --> 00:23.160
which is reachable and functional.

9
00:23.160 --> 00:25.460
So prior to deploying this auto VM,

10
00:25.460 --> 00:27.840
let's just take a peek at our NSX manager.

11
00:27.840 --> 00:29.980
So here's the web interface for our NSX manager.

12
00:29.980 --> 00:32.640
If we go to system, let's just check a couple things
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:29.980 --> 00:32.640
If we go to system, let's just check a couple things

13
00:32.640 --> 00:34.400
real quick, we'll click on system.

14
00:34.400 --> 00:36.880
And on the left, we'll click right here on appliances,

15
00:36.880 --> 00:40.160
just to make sure the NSX manager is up and ready.

16
00:40.160 --> 00:42.040
So in my lab environment for my cluster,

17
00:42.040 --> 00:45.160
I just have a single NSX manager is right here

18
00:45.160 --> 00:48.080
at 10.11.11.121.

19
00:48.080 --> 00:50.840
And I also want to take a moment and just verify

20
00:50.840 --> 00:53.140
that with our DNS server, that that is

21
00:53.140 --> 00:55.320
resolvable to the name we think it is.

22
00:55.320 --> 00:58.520
So here is our little VM that we looked at earlier.

23
00:58.520 --> 01:01.300
This is the little VM over on the 10.12 network,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:58.520 --> 01:01.300
This is the little VM over on the 10.12 network,

24
01:01.300 --> 01:03.700
which in our topology is our front end network.

25
01:03.700 --> 01:06.620
And let's verify that the name resolution is correct

26
01:06.620 --> 01:08.220
for the NSX manager.

27
01:08.220 --> 01:10.780
So if we didn't want to use NS look up or dig or something

28
01:10.780 --> 01:13.220
like that, we could go ahead and just ping the name

29
01:13.220 --> 01:16.100
and verify it resolves to this IP address.

30
01:16.100 --> 01:25.580
So the name of our NSX manager in DNS is NSX-MGR-VLAN-11.ogit.lab

31
01:25.860 --> 01:29.540
press enter and sure enough that resolved correctly

32
01:29.540 --> 01:32.820
to this IP address 10.11.11.121.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:29.540 --> 01:32.820
to this IP address 10.11.11.121.

33
01:32.820 --> 01:35.500
And I would encourage you as you go through

34
01:35.500 --> 01:37.500
to verify each and every step,

35
01:37.500 --> 01:39.300
including the DNS resolution.

36
01:39.300 --> 01:41.260
And that's going to save you oodles of time

37
01:41.260 --> 01:43.660
regarding troubleshooting because you know you have

38
01:43.660 --> 01:47.100
DNS resolution set up because you're testing it as you go.

39
01:47.100 --> 01:49.740
Also, right here, let's also test the name resolution

40
01:49.740 --> 01:51.140
for our vCenter server.

41
01:51.140 --> 01:56.140
So that's at vcsa-vlan11.ogit.lab.

42
01:56.140 --> 01:59.260
And then it is resolving to the correct IP address there

43
01:59.260 --> 02:02.180
as well for the vCenter on our management network
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

43
01:59.260 --> 02:02.180
as well for the vCenter on our management network

44
02:02.180 --> 02:04.620
at 10.11.11.111.

45
02:04.620 --> 02:05.460
Fantastic.

46
02:05.460 --> 02:06.580
So let me minimize that.

47
02:06.580 --> 02:08.620
So with systems still selected on the left,

48
02:08.620 --> 02:10.300
those go to fabric and under fabric,

49
02:10.300 --> 02:11.940
let's go to compute managers,

50
02:11.940 --> 02:14.900
just to validate that we are currently associated

51
02:14.900 --> 02:18.100
with our vCenter, which based on this name right here

52
02:18.100 --> 02:19.980
is our compute manager, it is.

53
02:19.980 --> 02:21.660
Let me clean up the columns a little bit.

54
02:21.660 --> 02:24.140
So there's the name I gave it when I associated this

55
02:24.140 --> 02:25.940
NSX manager with vCenter,

56
02:25.940 --> 02:28.340
and there is the actual fully qualified domain name

57
02:28.340 --> 02:29.740
that we just verified as well.

58
02:29.740 --> 02:31.860
And that's another confirmation that our DNS
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

58
02:29.740 --> 02:31.860
And that's another confirmation that our DNS

59
02:31.860 --> 02:33.740
is currently working, which is great.

60
02:33.740 --> 02:36.100
Also, what are they I like to share with you before

61
02:36.100 --> 02:38.380
we deploy the automation VM is check this out.

62
02:38.380 --> 02:41.900
If we could care on system in the NSX manager on the left,

63
02:41.900 --> 02:44.700
notice that we have a section called Quick Start

64
02:44.700 --> 02:46.500
and a section called appliances

65
02:46.500 --> 02:48.100
and NSX application platform.

66
02:48.100 --> 02:50.660
But once we deploy the automation VM,

67
02:50.660 --> 02:53.900
and we say we want to integrate with the NSX manager

68
02:53.900 --> 02:56.260
and do the plugin, we're gonna have an additional option

69
02:56.260 --> 02:58.460
right here for the automation component

70
02:58.460 --> 02:59.780
that's gonna magically appear.

71
02:59.780 --> 03:02.620
Actually, it's not magic, is the automation VM
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
02:59.780 --> 03:02.620
Actually, it's not magic, is the automation VM

72
03:02.620 --> 03:05.780
that's adding the plugin here as part of the NSX manager.

73
03:05.780 --> 03:08.220
So on older versions, the actual addition

74
03:08.220 --> 03:10.220
would be somewhere down here,

75
03:10.220 --> 03:12.780
but in the current flavor as of this recording,

76
03:12.780 --> 03:15.100
they're gonna add it right here as far as the plugin.

77
03:15.100 --> 03:16.940
All right, so let's head over to the vSphere client

78
03:16.940 --> 03:19.980
and let's deploy our little auto VM here

79
03:19.980 --> 03:24.980
on the 101111 network using the IP address of .6.

80
03:24.980 --> 03:26.020
So here in the vSphere client,

81
03:26.020 --> 03:28.340
I'm gonna go ahead and place that little auto VM

82
03:28.340 --> 03:29.220
in this cluster right here.

83
03:29.220 --> 03:30.860
In fact, for the remediate cluster,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

83
03:29.220 --> 03:30.860
In fact, for the remediate cluster,

84
03:30.860 --> 03:32.940
I'm gonna take each of these hosts right here

85
03:32.940 --> 03:34.460
and put them in maintenance mode.

86
03:34.460 --> 03:37.420
So I'll go to hosts and select all of them right click

87
03:37.420 --> 03:40.980
and put all of them in maintenance mode and say yes,

88
03:40.980 --> 03:43.780
and then okay and okay.

89
03:43.780 --> 03:46.260
And then we'll be using one, two or three of these

90
03:46.260 --> 03:49.460
as part of our NSX host transport nodes

91
03:49.460 --> 03:51.700
once we start building the NSX network.

92
03:51.700 --> 03:54.580
But also as a reminder, if we go back to our NSX here,

93
03:54.580 --> 03:55.580
here's the NSX manager,

94
03:55.580 --> 03:57.220
we go to networking at the moment.

95
03:57.220 --> 04:00.620
If we go to network topology, I've got absolutely nothing.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

95
03:57.220 --> 04:00.620
If we go to network topology, I've got absolutely nothing.

96
04:00.620 --> 04:02.820
And that's again to reinforce the concept

97
04:02.820 --> 04:06.820
of when we're implementing our NSX application platform,

98
04:06.820 --> 04:11.660
it is best to do it on real switches, real VLANs

99
04:11.660 --> 04:14.060
and not use virtualized infrastructure

100
04:14.060 --> 04:16.900
because if we implement the NSX application platform

101
04:16.900 --> 04:19.460
on a virtualized environment and we change some

102
04:19.460 --> 04:21.020
of that virtualized environment later,

103
04:21.020 --> 04:23.140
either accidentally or we didn't remember

104
04:23.140 --> 04:25.260
what it was being used for, that could destroy

105
04:25.260 --> 04:29.260
or interrupt the functionality of our NSX application platform.

106
04:29.260 --> 04:33.140
So once again, using physical gear and real VLANs
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

106
04:29.260 --> 04:33.140
So once again, using physical gear and real VLANs

107
04:33.140 --> 04:36.700
and real routers to support the NSX application platform

108
04:36.700 --> 04:38.020
is a great idea.

109
04:38.020 --> 04:40.220
So for the automation VM, let's go ahead

110
04:40.220 --> 04:42.780
and use this host for nap cluster.

111
04:42.780 --> 04:46.820
And I currently have DRS, which is enabled on that cluster.

112
04:46.820 --> 04:48.820
So we can right click on this cluster

113
04:48.820 --> 04:51.420
and say we wanna deploy an OVF template

114
04:51.420 --> 04:53.220
and then grab a local file.

115
04:53.220 --> 04:54.580
So I've just selected that file,

116
04:54.580 --> 04:58.980
it's called nap-automation.ovA and we'll click on next.

117
04:58.980 --> 05:01.620
Then I'm gonna go ahead and simply let it keep that name,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
04:58.980 --> 05:01.620
Then I'm gonna go ahead and simply let it keep that name,

118
05:01.620 --> 05:04.300
nap automation, which is showing us the version

119
05:04.300 --> 05:07.580
of the virtual machine that's gonna use for the automation.

120
05:07.580 --> 05:09.740
And as far as where we wanna keep this logically,

121
05:09.740 --> 05:12.740
let's put it in a folder called NSX VMs.

122
05:12.740 --> 05:14.420
And then as far as the compute resource,

123
05:14.420 --> 05:18.020
we wanna go ahead and use the cluster called host for naps.

124
05:18.020 --> 05:20.420
We'll select that cluster, click on next.

125
05:20.420 --> 05:21.420
And it's giving us some warnings,

126
05:21.420 --> 05:23.820
we're getting certificates, so I'll ignore those.

127
05:23.820 --> 05:26.180
And here's a summary of the details,

128
05:26.180 --> 05:27.940
including the size on disk,

129
05:27.940 --> 05:29.660
if it's thin provisioned or thick provisioned.

130
05:29.660 --> 05:30.860
So we'll click on next,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

130
05:29.660 --> 05:30.860
So we'll click on next,

131
05:30.860 --> 05:32.900
and then we'll accept the license agreement

132
05:32.900 --> 05:34.380
and click on next.

133
05:34.380 --> 05:36.820
Next it's asking us about where we wanna store the files

134
05:36.820 --> 05:37.660
for this VM.

135
05:37.660 --> 05:39.940
And let's put this on iSCSI2,

136
05:39.940 --> 05:42.660
which is reachable by all of our ESXi host

137
05:42.660 --> 05:44.540
and just to save a little space in my lab,

138
05:44.540 --> 05:47.340
I'm gonna say thin provisioned and click on next.

139
05:47.340 --> 05:49.620
Next is asking us about which network

140
05:49.620 --> 05:50.780
we wanna put this VM on.

141
05:50.780 --> 05:52.420
And so because we did the pre-work

142
05:52.420 --> 05:54.580
and we already have our networks all set up,

143
05:54.580 --> 05:57.180
we wanna place this little VM on our management network.

144
05:57.180 --> 06:00.140
So there's a port group that reflects VLAN 11.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

144
05:57.180 --> 06:00.140
So there's a port group that reflects VLAN 11.

145
06:00.140 --> 06:01.620
So we'll put the little VM connected

146
06:01.620 --> 06:04.340
to that logical port group and click on, okay.

147
06:04.340 --> 06:05.740
Then we'll click on next,

148
06:05.740 --> 06:08.580
and now it's gonna ask us some questions about that little VM.

149
06:08.580 --> 06:11.820
So for the name, I'm gonna put here a nap automation.

150
06:11.820 --> 06:14.780
Then we'll specify and confirm the initial root password.

151
06:14.780 --> 06:17.260
And this little icon here is for my password manager

152
06:17.260 --> 06:19.300
that's not part of the native interface.

153
06:19.300 --> 06:21.900
So we'll scroll down and admin password

154
06:21.900 --> 06:23.340
and confirm it as well.

155
06:23.340 --> 06:26.940
And as we scroll down, it's asking us about a NTP server.

156
06:26.940 --> 06:29.060
So we're gonna use our lab NTP server.

157
06:29.060 --> 06:30.740
Let's confirm where that is.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

157
06:29.060 --> 06:30.740
Let's confirm where that is.

158
06:30.740 --> 06:34.540
So here in our topology, that's right here at 10.10.10.100.

159
06:34.540 --> 06:38.820
So we'll specify our DINA server is at 10.10.10.100.

160
06:38.820 --> 06:41.340
And we'll specify that for the lab environment,

161
06:41.340 --> 06:44.380
I don't wanna join the customer experience improvement programs.

162
06:44.380 --> 06:45.580
We'll leave that unchecked.

163
06:45.580 --> 06:46.820
And the next is asking us about,

164
06:46.820 --> 06:51.260
do we want to enable the plugin with our NSX manager?

165
06:51.260 --> 06:52.820
In that way, if we do enable the plugin,

166
06:52.820 --> 06:54.660
we can actually use the automation directly

167
06:54.660 --> 06:56.740
from the NSX manager instead of going

168
06:56.740 --> 06:59.940
to the separate interface for the automation VM.

169
06:59.940 --> 07:01.180
So they will both work,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

169
06:59.940 --> 07:01.180
So they will both work,

170
07:01.180 --> 07:03.060
but if we wanna do it all from the interface

171
07:03.060 --> 07:05.780
at the NSX manager, we want to enable the plugin.

172
07:05.780 --> 07:07.020
So we'll say yes to that.

173
07:07.020 --> 07:10.740
And now it's asking us about where is that NSX manager?

174
07:10.740 --> 07:14.620
So if we had a virtual IP address for NSX manager cluster,

175
07:14.620 --> 07:16.380
we'd wanna specify that virtual IP address

176
07:16.380 --> 07:18.300
or in the event that you don't have a virtual IP address,

177
07:18.300 --> 07:21.300
you only have one NSX manager like I do in my lab,

178
07:21.300 --> 07:23.060
we can still be specifying the IP address

179
07:23.060 --> 07:26.740
or even better yet the name of that NSX manager right here.

180
07:26.740 --> 07:28.580
So I'm gonna go ahead and use the DNS name

181
07:28.580 --> 07:31.260
'cause that's also gonna help us verify with the prechecks
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

181
07:28.580 --> 07:31.260
'cause that's also gonna help us verify with the prechecks

182
07:31.260 --> 07:33.940
that everything is resolvable and reachable.

183
07:33.940 --> 07:36.460
So it's better to find out earlier than later

184
07:36.460 --> 07:37.940
if you have a problem with DNS.

185
07:37.940 --> 07:40.940
So I'm gonna go ahead and use the fully qualified domain name here.

186
07:40.940 --> 07:43.100
And then we'd wanna specify the passwords

187
07:43.100 --> 07:44.900
that we're gonna be using in conjunction

188
07:44.900 --> 07:46.380
with our NSX manager.

189
07:46.380 --> 07:49.060
So there's an API password and also the root password

190
07:49.060 --> 07:50.740
and I'm gonna plug those in right now.

191
07:50.740 --> 07:52.940
So whatever passwords you use when you configured

192
07:52.940 --> 07:54.580
and deployed the NSX manager,

193
07:54.580 --> 07:56.700
you'd wanna use the same passwords here

194
07:56.700 --> 07:58.060
and then we'll scroll down.

195
07:58.060 --> 08:00.580
Now it's asking us about what IP address we wanna use
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

195
07:58.060 --> 08:00.580
Now it's asking us about what IP address we wanna use

196
08:00.580 --> 08:02.900
for the actual automation appliance itself.

197
08:02.900 --> 08:07.880
So based on our plan, we wanna use the IP address of 10.11.11.7.

198
08:08.640 --> 08:10.040
So we'll supply that here.

199
08:10.040 --> 08:12.360
There's a 24-bit mask associated with that IP address.

200
08:12.360 --> 08:13.360
Fantastic.

201
08:13.360 --> 08:15.800
And because we are doing a static address,

202
08:15.800 --> 08:17.240
we'll also specify the default gateway

203
08:17.240 --> 08:19.120
that this automation VM should use,

204
08:19.120 --> 08:22.120
which is 10.11.11.1.

205
08:22.120 --> 08:23.840
And just to confirm where that is,

206
08:23.840 --> 08:26.520
this is the .1 address on this multilayer switch

207
08:26.520 --> 08:29.960
or top of rack switch that we tested and verified earlier.

208
08:29.960 --> 08:32.640
So our little automation VM is gonna be deployed right here
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

208
08:29.960 --> 08:32.640
So our little automation VM is gonna be deployed right here

209
08:32.640 --> 08:35.760
at .6 on the 10.11.11 network.

210
08:35.760 --> 08:38.200
And it's gonna have a default gateway of .1

211
08:38.200 --> 08:39.880
if it needs to reach any other devices,

212
08:39.880 --> 08:42.560
including DNS and other subnets

213
08:42.560 --> 08:44.680
that are not local to that out of VM.

214
08:44.680 --> 08:47.000
And for the domain name, I'll specify it's ogit.lab

215
08:47.000 --> 08:48.920
and for additional search domains,

216
08:48.920 --> 08:50.960
I'm gonna still use just ogit.lab

217
08:50.960 --> 08:54.080
'cause everything in my topology is within that domain.

218
08:54.080 --> 08:57.880
And then for the DNS server, it's gonna be 10.10.10.100,

219
08:57.880 --> 09:00.480
which again, we already verified that we have reachability two
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

219
08:57.880 --> 09:00.480
which again, we already verified that we have reachability two

220
09:00.480 --> 09:03.760
and also we verified that that DNS server is functional.

221
09:03.760 --> 09:05.880
So with that in place, we'll click on next.

222
09:05.880 --> 09:07.280
So it's giving us a quick summary

223
09:07.280 --> 09:09.880
and I would recommend that when you're deploying this,

224
09:09.880 --> 09:12.520
you take a moment and read the summary.

225
09:12.520 --> 09:15.640
So the NTP server as well as the DNS server

226
09:15.640 --> 09:18.200
is at 10.10.10.100, fantastic.

227
09:18.200 --> 09:20.840
The IP address that we want this little automation VM to use

228
09:20.840 --> 09:24.000
is .6 on the 10.11.11 network,

229
09:24.000 --> 09:26.000
the default gateway is at .1.

230
09:26.000 --> 09:29.400
And here's the DNS resolvable name for the NSX manager,

231
09:29.400 --> 09:31.200
which this little automation VM is gonna need
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

231
09:29.400 --> 09:31.200
which this little automation VM is gonna need

232
09:31.200 --> 09:33.840
because it's gonna reach out to that NSX manager

233
09:33.840 --> 09:36.480
and add the plugin for the automation.

234
09:36.480 --> 09:38.960
So we'll go ahead and click right here on Finish.

235
09:38.960 --> 09:40.060
And here are recent tasks.

236
09:40.060 --> 09:41.960
It shows us that that little VM is currently

237
09:41.960 --> 09:44.160
in the process of being deployed.

238
09:44.160 --> 09:45.880
And after that VM is deployed,

239
09:45.880 --> 09:48.520
what we'd expect here in the NSX manager

240
09:48.520 --> 09:51.760
is that if we go to the system tab over here on the left,

241
09:51.760 --> 09:54.360
once that little auto VM is completely deployed,

242
09:54.360 --> 09:56.320
we'll have an additional option right here

243
09:56.320 --> 09:59.200
for the automation, for the implementation

244
09:59.200 --> 10:01.480
of the NSX application platform.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

244
09:59.200 --> 10:01.480
of the NSX application platform.

245
10:01.480 --> 10:03.840
So I'm gonna give the deployment here about 30 minutes

246
10:03.840 --> 10:05.080
for it to complete.

247
10:05.080 --> 10:06.400
And then in the next video, we'll come back

248
10:06.400 --> 10:08.600
and we'll verify that both the VM deployed

249
10:08.600 --> 10:10.800
and also the here in the NSX manager,

250
10:10.800 --> 10:12.760
we have the additional plugin available

251
10:12.760 --> 10:14.500
for the NSX automation.

252
10:14.500 --> 10:17.000
So I'll see you in the next video for that follow up.