WEBVTT

1
00:00.000 --> 00:02.900
In this video, you and I get to chat about VMs

2
00:02.900 --> 00:04.340
and where we're going to place them.

3
00:04.340 --> 00:07.540
So let's start off with some of the VMs we're going to use in our lab

4
00:07.540 --> 00:07.900
environment.

5
00:07.900 --> 00:11.700
We need a VM that we can use for name resolution that we can control.

6
00:11.700 --> 00:13.140
So in my lab environment,

7
00:13.140 --> 00:15.740
I'm using a simple little copy of Windows Server,

8
00:15.740 --> 00:19.540
and that is providing my DNS services in my lab environment.

9
00:19.540 --> 00:22.460
So every time I'm going to deploy an Edge node or

10
00:22.460 --> 00:26.700
transport node or something else in the world of vSphere and or NSX,

11
00:26.700 --> 00:29.860
I'm going to go ahead and create a records for each of them.

12
00:29.860 --> 00:31.420
As far as this Windows Server,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:29.860 --> 00:31.420
As far as this Windows Server,

13
00:31.420 --> 00:35.660
I'm running it as a VM on one of my physical ESXi hosts.

14
00:35.660 --> 00:37.300
So let me show you what that looks like.

15
00:37.300 --> 00:39.500
So here in my vSphere client,

16
00:39.500 --> 00:41.700
if we expand my folder here for Core VMs,

17
00:41.700 --> 00:44.580
there's my Windows Server right there.

18
00:44.580 --> 00:47.460
So we opened up a remote console to that and took a look.

19
00:47.460 --> 00:50.420
While that's coming up, you'll notice here that it's on my management network

20
00:50.420 --> 00:51.540
at .100.

21
00:51.540 --> 00:54.100
So anytime I need to tell one of my VMs,

22
00:54.100 --> 00:57.910
which DNS server to use, I'm going to point to the IP address here of my

23
00:57.910 --> 00:59.300
Windows Server.

24
00:59.300 --> 01:03.340
So here is the remote console for my little Windows Server,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
00:59.300 --> 01:03.340
So here is the remote console for my little Windows Server,

25
01:03.340 --> 01:08.260
and we go to the server manager and go to tools and go to DNS,

26
01:08.260 --> 01:10.380
we can confirm our DNS configuration.

27
01:10.380 --> 01:12.820
So here in the DNS server, if we expand,

28
01:12.820 --> 01:14.380
I've got three different domains,

29
01:14.380 --> 01:16.980
ogat.local and .lab and .com.

30
01:16.980 --> 01:19.580
So whatever you plan on using for names,

31
01:19.580 --> 01:22.940
go ahead and create those zones and then populate them with the A records.

32
01:22.940 --> 01:25.620
So if we expand ogat.lab right here,

33
01:25.620 --> 01:29.940
I've got entries for every possible system I've ever deployed here as part of

34
01:29.940 --> 01:30.500
NSX.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:29.940 --> 01:30.500
NSX.

35
01:30.500 --> 01:32.740
So as a quick dec, we have a little record here for edge one,

36
01:32.740 --> 01:37.420
that'd be edge one .ogat.lab and I should be able to resolve that from my

37
01:37.420 --> 01:38.180
management computer

38
01:38.180 --> 01:41.700
if I'm also pointing to this DNS server for name resolution.

39
01:41.700 --> 01:46.180
So if we bring in a command prompt like that and we do an NS lookup for edge

40
01:46.180 --> 01:48.580
one .ogat.lab

41
01:48.580 --> 01:49.660
and then press enter,

42
01:49.660 --> 01:52.820
they'll confirm that we're using that DNS server here for my management

43
01:52.820 --> 01:53.460
computer.

44
01:53.460 --> 01:56.460
It also confirms that our name resolution is working correctly.

45
01:56.460 --> 02:00.340
So again, this is a critical component for making sure everything works inside
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

45
01:56.460 --> 02:00.340
So again, this is a critical component for making sure everything works inside

46
02:00.340 --> 02:01.420
of an NSX lab.

47
02:01.420 --> 02:05.250
So they move that out of the way and I'll move the Windows Server out of the

48
02:05.250 --> 02:05.660
way.

49
02:05.660 --> 02:07.420
So that's one of the critical VMs for the lab.

50
02:07.420 --> 02:09.540
Another critical VM besides vCenter,

51
02:09.540 --> 02:12.700
which is also running right here on one of my hosts.

52
02:12.700 --> 02:18.020
Another critical VM is a little Vios router that I have is a tiny little image.

53
02:18.020 --> 02:22.100
It doesn't take very long to deploy and I have this configured as a routing and

54
02:22.100 --> 02:22.980
NAT device.

55
02:22.980 --> 02:27.580
So if I want to connect, for example, a tier zero gateway to the external world

56
02:27.580 --> 02:27.580
,

57
02:27.580 --> 02:32.420
I can use any of the VLANs that this little external router is connected to.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:27.580 --> 02:32.420
I can use any of the VLANs that this little external router is connected to.

58
02:32.420 --> 02:35.860
So for this little router right here, if we scroll down and look at this config

59
02:35.860 --> 02:35.860
,

60
02:35.860 --> 02:38.860
I have poor groups that it's connected to including my prod 192,

61
02:38.860 --> 02:40.260
that's just my management network.

62
02:40.260 --> 02:42.420
I've got one for an ISCSI network.

63
02:42.420 --> 02:47.340
I also have one for VLAN 21, VLAN 23 and VLAN 24.

64
02:47.340 --> 02:50.790
And if we want to just verify that and take a quick peek at that VM, we can do

65
02:50.790 --> 02:51.620
so as well.

66
02:51.620 --> 02:53.540
So here's that little Vios router.

67
02:53.540 --> 02:55.900
Then we do a show configuration and I'll just type in commands.

68
02:55.900 --> 02:57.580
There'll be a little more concise that way.

69
02:57.580 --> 03:00.460
It's going to show us all the configuration commands associated with it.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

69
02:57.580 --> 03:00.460
It's going to show us all the configuration commands associated with it.

70
03:00.460 --> 03:01.860
So here's the command that is just issued,

71
03:01.860 --> 03:03.780
it's showing us the IP addresses that have configured.

72
03:03.780 --> 03:07.900
So in VMware, it plays to each of its interfaces into the correct port group,

73
03:07.900 --> 03:09.580
which leads to the correct VLAN.

74
03:09.580 --> 03:12.660
And in addition to having basic connectivity to each of those networks,

75
03:12.660 --> 03:16.100
this is also configured with address translation.

76
03:16.100 --> 03:22.460
So traffic coming in on the 2312 or 2412 or the 104 or the 1021 networks,

77
03:22.460 --> 03:26.140
all of that can be translated as it goes out towards the internet.

78
03:26.140 --> 03:28.860
It's also running OSPF, which is super handy.

79
03:28.860 --> 03:31.860
It also supports BGP, which is going to be super handy.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

79
03:28.860 --> 03:31.860
It also supports BGP, which is going to be super handy.

80
03:31.860 --> 03:33.940
And it also supports DHPP services,

81
03:33.940 --> 03:35.500
should you need them as well,

82
03:35.500 --> 03:37.500
all of which I have configured right here.

83
03:37.500 --> 03:41.700
And currently I'm connected to this little router on this IP address right here

84
03:41.700 --> 03:41.700
,

85
03:41.700 --> 03:43.620
which is connected to my management network.

86
03:43.620 --> 03:47.100
And again, the footprint for a little BIOS machine is super teeny.

87
03:47.100 --> 03:50.860
So right here it's got one CPU, one gig of RAM.

88
03:50.860 --> 03:54.100
And if we take a look at how much space it's actually using within provisioning

89
03:54.100 --> 03:54.100
,

90
03:54.100 --> 03:57.980
here's that little machine right there, and it's using 1.6 gigs.

91
03:57.980 --> 04:01.340
So once again, a very tiny footprint, lots of functionality,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
03:57.980 --> 04:01.340
So once again, a very tiny footprint, lots of functionality,

92
04:01.340 --> 04:04.020
and lots of great documentation out on the internet,

93
04:04.020 --> 04:05.860
regarding exactly how to configure it.

94
04:05.860 --> 04:08.300
So I've got the Windows server for DNS services.

95
04:08.300 --> 04:11.260
I got my little BIOS machine that we just looked at,

96
04:11.260 --> 04:14.060
which is providing routing and also network services,

97
04:14.060 --> 04:17.260
including network address translation and DHCP.

98
04:17.260 --> 04:20.580
And if you've been with me through these sets of videos as part of this course

99
04:20.580 --> 04:20.580
ware,

100
04:20.580 --> 04:22.700
it's that little BIOS VM right there,

101
04:22.700 --> 04:30.220
that's that default external router at 23.1.2.1, or 24.1.2.1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

101
04:22.700 --> 04:30.220
that's that default external router at 23.1.2.1, or 24.1.2.1.

102
04:30.220 --> 04:34.820
And those are on two respective VLANs of VLAN 23 and VLAN 24.

103
04:34.820 --> 04:38.410
So although we could use a physical router for the purposes of our external

104
04:38.410 --> 04:39.060
gateway,

105
04:39.060 --> 04:41.380
it's a lot easier to use a VM.

106
04:41.380 --> 04:43.020
And that's what I'm using right here in the lab.

107
04:43.020 --> 04:46.860
So the little BIOS VM is also running on one of my physical ESXi hosts,

108
04:46.860 --> 04:50.820
along with the Windows server, and also my vCenter server appliance

109
04:50.820 --> 04:53.300
is also running on one of my physical hosts.

110
04:53.300 --> 04:57.100
And in my lab environment, I'm using .111 on my management network for that.

111
04:57.100 --> 04:59.980
My Windows server, as we looked at earlier, is at .100.

112
04:59.980 --> 05:03.420
And that reminds me of another important step is besides just setting up DNS
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

112
04:59.980 --> 05:03.420
And that reminds me of another important step is besides just setting up DNS

113
05:03.420 --> 05:03.780
entries

114
05:03.780 --> 05:07.280
for what needs DNS, we'd also want to make sure that we have a good plan in

115
05:07.280 --> 05:07.460
place

116
05:07.460 --> 05:11.570
and good documentation of exactly which devices and which VMs are going to get

117
05:11.570 --> 05:12.860
which IP addresses.

118
05:12.860 --> 05:17.150
We're going to have three ESXi VMs that are also running here in the physical

119
05:17.150 --> 05:17.740
environment.

120
05:17.740 --> 05:25.300
So we call them ESXi, A and ESXi, B and ESXi management.

121
05:25.300 --> 05:29.340
So these first two are going to be acting as host transport nodes.

122
05:29.340 --> 05:31.220
And on this third one right here,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

122
05:29.340 --> 05:31.220
And on this third one right here,

123
05:31.220 --> 05:35.190
this we can put the nested vCenter server and also our edge nodes when we

124
05:35.190 --> 05:35.940
deploy them.

125
05:35.940 --> 05:41.300
So those will be nested VMs inside of this VM, the ESXi management VM.

126
05:41.300 --> 05:45.100
And these three VMs are going to be running in the physical hosts.

127
05:45.100 --> 05:49.140
And when we deploy those VMs, we also want to go into the details under CPU

128
05:49.140 --> 05:52.440
and enable the little checkbox that says we want to be able to do virtual

129
05:52.440 --> 05:53.020
ization

130
05:53.020 --> 05:54.580
inside of those VMs.

131
05:54.580 --> 05:58.500
So let me show you these three ESXi hosts running as VMs.

132
05:58.500 --> 06:02.780
So here in the vSphere client, and this domain is OGIT.prod,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

132
05:58.500 --> 06:02.780
So here in the vSphere client, and this domain is OGIT.prod,

133
06:02.780 --> 06:04.500
that's my single sign on domain.

134
06:04.500 --> 06:11.060
I have a folder called nested NSX Blue and there is ESXi, A running as a VM.

135
06:11.060 --> 06:14.620
And I gave that 48 gigs of RAM and eight CPUs.

136
06:14.620 --> 06:18.740
There's ESXi, B, which I also gave 48 gigs of RAM and eight CPUs.

137
06:18.740 --> 06:21.460
And there's my third VM ESXi management,

138
06:21.460 --> 06:24.660
which I gave more CPUs and more memory to.

139
06:24.660 --> 06:28.270
So in my vSphere environment, with the vCenter for this managing my physical

140
06:28.270 --> 06:28.700
hosts,

141
06:28.700 --> 06:32.500
I'm also using DRS so it can move VMs around as needed
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

141
06:28.700 --> 06:32.500
I'm also using DRS so it can move VMs around as needed

142
06:32.500 --> 06:35.140
between any of my available ESXi hosts.

143
06:35.140 --> 06:38.980
Also, while we're here, let me also chat with you about the NSX manager.

144
06:38.980 --> 06:44.340
Notice here that I'm running the NSX manager as a VM on the physical hosts.

145
06:44.340 --> 06:46.660
I'm not running the NSX manager nested.

146
06:46.660 --> 06:48.980
Now it is possible and I did it for a while.

147
06:48.980 --> 06:54.900
We can run if we want to the actual NSX manager on one of our virtualized ESXi

148
06:54.900 --> 06:55.220
hosts.

149
06:55.220 --> 06:58.020
However, as I took a look at a few different versions,

150
06:58.020 --> 07:02.900
it wasn't always completely reliable if it was running as a nested VM.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

150
06:58.020 --> 07:02.900
it wasn't always completely reliable if it was running as a nested VM.

151
07:02.900 --> 07:08.120
So in addition to these three ESXi hosts that I'm running in my VMware

152
07:08.120 --> 07:09.620
environment with vSphere,

153
07:09.620 --> 07:13.860
I'm also when we deploy the NSX manager, I'm also going to deploy that

154
07:13.860 --> 07:18.420
on a physical host and not nested inside of one of the other ESXi hosts.

155
07:18.420 --> 07:21.780
Also regarding these ESXi hosts, if we look at one of them and right click on

156
07:21.780 --> 07:26.100
the VM and say edit settings, here with the virtual hardware tab selected,

157
07:26.100 --> 07:30.900
we want to expand the CPU section here and make sure that we're allowing the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

157
07:26.100 --> 07:30.900
we want to expand the CPU section here and make sure that we're allowing the

158
07:30.900 --> 07:31.540
hardware

159
07:31.540 --> 07:36.660
virtualization. So I deployed these VMs, these ESXi hosts as VMs.

160
07:36.660 --> 07:41.710
I made sure to check that checkbox so that we could further run VMs inside of

161
07:41.710 --> 07:42.420
those VMs.

162
07:42.420 --> 07:46.020
So that's one more thing we'd want to do on those ESXi hosts that are running

163
07:46.020 --> 07:46.820
as VMs.

164
07:46.820 --> 07:49.140
All right, let me go ahead and close that.

165
07:49.140 --> 07:53.860
So now that we've identified these three ESXi VMs that we're running inside of

166
07:53.860 --> 07:54.820
our parent

167
07:54.820 --> 07:58.180
environment here, let me also give you a peek into what's running on these VMs.

168
07:58.180 --> 08:03.300
Now in my virtualized environment, I also deployed vCenter, which is separate
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

168
07:58.180 --> 08:03.300
Now in my virtualized environment, I also deployed vCenter, which is separate

169
08:03.300 --> 08:03.780
from my

170
08:03.780 --> 08:08.800
ogit.prod. I wanted a separate instance of vCenter just for my nested

171
08:08.800 --> 08:09.460
environment.

172
08:09.460 --> 08:13.940
That way when I snapshot things, I have to roll things back, I can bring it all

173
08:13.940 --> 08:14.500
back,

174
08:14.500 --> 08:18.740
including vCenter and not leave any trails of previous configurations.

175
08:18.740 --> 08:23.140
So let me swap over with light mode into the vSphere environment that these

176
08:23.140 --> 08:24.580
three ESXi hosts

177
08:24.580 --> 08:28.980
are currently part of. So here in the vSphere client in my nested environment,

178
08:28.980 --> 08:33.860
notice that the single sign-on domain is changed as ogit.lab.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

178
08:28.980 --> 08:33.860
notice that the single sign-on domain is changed as ogit.lab.

179
08:33.860 --> 08:37.540
And here in host and clusters view with the VM tab selected, notice that we

180
08:37.540 --> 08:38.580
have the vCenter

181
08:38.580 --> 08:43.180
server for my nested environment and the two edge nodes courtesy of the NSX

182
08:43.180 --> 08:43.940
manager who deployed

183
08:43.940 --> 08:51.300
those all running on this host. So ESXi-management.ogit.lab, that's my nested

184
08:51.300 --> 08:52.020
VM

185
08:52.020 --> 08:56.010
called ESXi-management. So if you go back to the parent environment here in

186
08:56.010 --> 08:56.660
dark mode,

187
08:56.660 --> 09:01.300
that's this VM right there that is currently running those three VMs.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

187
08:56.660 --> 09:01.300
that's this VM right there that is currently running those three VMs.

188
09:01.300 --> 09:05.910
Again, the two edge nodes and the vCenter that I have set up just for my nested

189
09:05.910 --> 09:06.740
environment.

190
09:06.740 --> 09:10.750
Another thing I chose to do was to create a couple different clusters, one for

191
09:10.750 --> 09:12.260
ESXi-a and b,

192
09:12.260 --> 09:17.060
and then one just for my management ESXi host. I also chose to go ahead and use

193
09:17.060 --> 09:17.780
the life cycle

194
09:17.780 --> 09:22.260
manager to update the versions of the ESXi host to the latest and greatest.

195
09:22.260 --> 09:27.530
I also took the option of upgrading vCenter. So everything is super current

196
09:27.530 --> 09:28.740
before I started

197
09:28.740 --> 09:33.380
deploying NSX on top of this virtualized nested lab environment. So again,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

197
09:28.740 --> 09:33.380
deploying NSX on top of this virtualized nested lab environment. So again,

198
09:33.380 --> 09:34.180
going forward for the

199
09:34.180 --> 09:38.470
demonstration here in dark mode, that's my production environment or my parent

200
09:38.470 --> 09:39.700
physical environment

201
09:39.700 --> 09:45.060
called ogit.prod. And here in light mode is my nested environment. And the next

202
09:45.060 --> 09:45.620
thing I'd love to

203
09:45.620 --> 09:49.400
think a closer look at you with is the networking inside of my nested

204
09:49.400 --> 09:50.900
environment, which we'll do

205
09:50.900 --> 09:53.940
in the next video. So I'll see you there in just a moment.