WEBVTT

1
00:00.000 --> 00:03.360
So in this video, let's talk about the infrastructure that we can use for our

2
00:03.360 --> 00:04.560
nested lab environment.

3
00:04.560 --> 00:07.760
Starting off with this top of rack switch. As I mentioned in the other video,

4
00:07.760 --> 00:15.130
I'm using a Cisco Catalyst 3750 switch, which a decade ago, they were thousands

5
00:15.130 --> 00:16.160
and thousands of

6
00:16.160 --> 00:21.270
dollars to get a fully decked out 3750 switch. Now they're 80 bucks, but they

7
00:21.270 --> 00:22.480
still do a fantastic

8
00:22.480 --> 00:26.490
job. So this is going to represent the top of rack switch right here. And again

9
00:26.490 --> 00:27.280
, this is a Cisco

10
00:27.280 --> 00:31.310
Catalyst 3750 that I'm currently using. Now on the top of rack switch, the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:27.280 --> 00:31.310
Catalyst 3750 that I'm currently using. Now on the top of rack switch, the

11
00:31.310 --> 00:32.080
connections that are

12
00:32.080 --> 00:36.480
going to go to your ESXi environment, we simply want them to be trunk ports. So

13
00:36.480 --> 00:36.720
I'm going to

14
00:36.720 --> 00:42.030
label those as trunk ports, meaning they use 802.1 Q tagging and can support

15
00:42.030 --> 00:43.040
the VLANs that are

16
00:43.040 --> 00:46.950
being supported by the switch. So as far as VLANs go, here is a really

17
00:46.950 --> 00:48.880
important part to remember.

18
00:48.880 --> 00:54.930
If you plan on using four or five or six or 10 VLANs, make sure that those VLAN

19
00:54.930 --> 00:55.680
s are supported

20
00:55.680 --> 01:00.490
here at your top of rack switch. So if you're using, for example, VLAN 23 and V
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:55.680 --> 01:00.490
here at your top of rack switch. So if you're using, for example, VLAN 23 and V

21
01:00.490 --> 01:03.120
LAN 24 or VLAN 101

22
01:03.120 --> 01:08.030
or 102, et cetera, et cetera, make sure that those VLANs are supported on the

23
01:08.030 --> 01:08.720
switch and make

24
01:08.720 --> 01:12.560
sure the ports that are connected down to your physical ESXi environment are

25
01:12.560 --> 01:14.080
set up as trunk ports.

26
01:14.080 --> 01:19.520
And those trunk ports can be connected to our physical ESXi hosts. So here I'll

27
01:19.520 --> 01:20.000
make a note,

28
01:20.000 --> 01:26.080
this is our physical ESXi hosts here in pink. And although we may have two or

29
01:26.080 --> 01:27.040
three or more

30
01:27.040 --> 01:31.200
physical hosts as part of our lab environment leveraging DRS behind the scenes,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

30
01:27.040 --> 01:31.200
physical hosts as part of our lab environment leveraging DRS behind the scenes,

31
01:31.200 --> 01:31.600
what I want to

32
01:31.600 --> 01:35.440
do right here is just represent that we want our connectivity from the physical

33
01:35.440 --> 01:36.000
ESXi hosts

34
01:36.000 --> 01:40.330
going up to the trunk ports on the top of rack switch. So let me go ahead and

35
01:40.330 --> 01:41.600
draw a virtual

36
01:41.600 --> 01:46.280
distributed switch right here. I'll just label that VDS on the physical ESXi

37
01:46.280 --> 01:47.280
host. And associate

38
01:47.280 --> 01:53.440
that VDS, we have one or more uplinks, also known as VMNix, that are physically

39
01:53.440 --> 01:54.720
connected up to the

40
01:54.720 --> 01:58.160
trunk ports on the top of rack switch, and that are logged at the associate

41
01:58.160 --> 01:58.640
with our

42
01:58.640 --> 02:02.640
virtual distributed switch here on the ESXi host. And then on this virtual
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
01:58.640 --> 02:02.640
virtual distributed switch here on the ESXi host. And then on this virtual

43
02:02.640 --> 02:03.440
distributed switch,

44
02:03.440 --> 02:07.680
we're going to have six port groups that we're going to set up associated with

45
02:07.680 --> 02:08.160
this virtual

46
02:08.160 --> 02:13.080
distributed switch. So for this orange color, I'll label those as PGs for port

47
02:13.080 --> 02:14.160
groups. So when we

48
02:14.160 --> 02:18.420
configure these port groups, we'd want to set them up as trunks to support VLAN

49
02:18.420 --> 02:19.200
zero through

50
02:19.200 --> 02:23.310
four zero nine four, which is a fancy way of saying we're willing to support

51
02:23.310 --> 02:24.560
all VLANs. Also,

52
02:24.560 --> 02:30.060
since we're right here, let's also draw in the nested virtualized ESXi hosts.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
02:24.560 --> 02:30.060
since we're right here, let's also draw in the nested virtualized ESXi hosts.

53
02:30.060 --> 02:30.800
So I'll write that

54
02:30.800 --> 02:35.280
here as nested. And on each of these nested ESXi hosts, we're going to give

55
02:35.280 --> 02:37.440
them each six network

56
02:37.440 --> 02:42.210
cards. And those are going to represent the VM Nix, including VM Nix zero and

57
02:42.210 --> 02:43.440
VM Nix one and two

58
02:43.440 --> 02:48.660
and three and four and five. And as we deploy each of these nested ESXi hosts,

59
02:48.660 --> 02:49.200
we're going to go ahead

60
02:49.200 --> 02:53.630
and associate their network interface cards with the port groups up here on the

61
02:53.630 --> 02:55.120
physical ESXi host.

62
02:55.120 --> 02:58.080
So this is the first network card we'll go to the first port group, and then

63
02:58.080 --> 02:58.560
this one will go to the

64
02:58.560 --> 03:02.960
next port group and so forth and so on until we have all six adapters. So this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
02:58.560 --> 03:02.960
next port group and so forth and so on until we have all six adapters. So this

65
03:02.960 --> 03:04.160
would be VM Nix zero

66
03:04.160 --> 03:07.780
through five, all connected effectively to trunks. And then the VDS that's

67
03:07.780 --> 03:09.200
supporting that is also

68
03:09.200 --> 03:13.510
connected to trunks. And also while we're here, let me also draw in the two VDS

69
03:13.510 --> 03:14.080
s that we're going

70
03:14.080 --> 03:17.020
to create in the virtualized environment. We're going to use one virtual

71
03:17.020 --> 03:18.160
distributed switch. I'll

72
03:18.160 --> 03:21.930
go ahead and label this VDS hosts and a second virtual distributed switch in

73
03:21.930 --> 03:23.280
our nested environment.

74
03:23.280 --> 03:27.100
We'll call that one VDS edge. And then for the uplinks associated, we'll

75
03:27.100 --> 03:28.000
associate these four

76
03:28.000 --> 03:32.090
right here, VM Nix zero, one, two, and three with our virtual distributed
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
03:28.000 --> 03:32.090
right here, VM Nix zero, one, two, and three with our virtual distributed

77
03:32.090 --> 03:34.000
switch called VDS hosts,

78
03:34.000 --> 03:38.140
and we'll associate the other two uplinks with the virtual switch called VDS

79
03:38.140 --> 03:38.720
edge.

80
03:38.720 --> 03:44.160
So for the VLANs that we intend on using this nested ESXi host will believe and

81
03:44.160 --> 03:44.720
feel like it

82
03:44.720 --> 03:49.880
has full access to all the VLANs it needs because it's connected to trunks. And

83
03:49.880 --> 03:50.800
this VDS on the

84
03:50.800 --> 03:55.220
host switch is also connected to one or more trunks. And that leads us back to

85
03:55.220 --> 03:55.840
the top of our

86
03:55.840 --> 04:00.540
X switch. We need to make darn sure that whatever VLAN that we are using, all
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

86
03:55.840 --> 04:00.540
X switch. We need to make darn sure that whatever VLAN that we are using, all

87
04:00.540 --> 04:02.320
of those VLANs exist

88
04:02.320 --> 04:06.200
in the top of our X switch, because if down here, we have a situation we're

89
04:06.200 --> 04:07.360
trying to use VLAN

90
04:07.360 --> 04:11.600
one zero one, for example, and the top of X switch doesn't have one zero one,

91
04:11.600 --> 04:12.400
as we start spreading

92
04:12.400 --> 04:15.920
out our work across multiple physical hosts, and they need to communicate with

93
04:15.920 --> 04:16.480
each other,

94
04:16.480 --> 04:20.960
including using a common VLAN like VLAN one zero one. If that VLAN doesn't

95
04:20.960 --> 04:21.680
exist here at the top

96
04:21.680 --> 04:26.020
of our X switch, this top of our X switch for most vendors is going to deny or

97
04:26.020 --> 04:27.280
drop that traffic

98
04:27.280 --> 04:30.680
with a frame that's tagged for a VLAN that is not supporting. All right, a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

98
04:27.280 --> 04:30.680
with a frame that's tagged for a VLAN that is not supporting. All right, a

99
04:30.680 --> 04:31.440
couple other notes

100
04:31.440 --> 04:37.150
about the infrastructure. One is MTU the maximum transmission unit that that to

101
04:37.150 --> 04:38.640
9000 or if you

102
04:38.640 --> 04:42.540
want to say 9k that works too. And that way we can support jumbo frames when

103
04:42.540 --> 04:43.680
needed or if needed

104
04:43.680 --> 04:47.520
across the entire topology. So make sure that on the top of our X switch that

105
04:47.520 --> 04:48.480
we're going to set

106
04:48.480 --> 04:55.600
the MTU to be 9000 to support a layer to 9000 byte frame also often referred to

107
04:55.600 --> 04:56.880
as a jumbo frame.

108
04:56.880 --> 05:00.800
And that also is going to be true here when we create this to switch on our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

108
04:56.880 --> 05:00.800
And that also is going to be true here when we create this to switch on our

109
05:00.800 --> 05:01.760
physical ESXi

110
05:01.760 --> 05:06.320
host that they're going to use, make sure we also set the MTU to 9000. And the

111
05:06.320 --> 05:07.280
same thing here,

112
05:07.280 --> 05:11.590
when we create these distributed switches as well, we also want to set the MTU

113
05:11.590 --> 05:12.800
to 9000.

114
05:12.800 --> 05:16.720
So let me clean that up just a little bit. So the 9000, anytime we're working

115
05:16.720 --> 05:17.360
with a top of

116
05:17.360 --> 05:21.400
X switch or any of our virtual distributed switches, make sure at the switch

117
05:21.400 --> 05:21.760
level,

118
05:21.760 --> 05:25.440
we allow for a 9000 byte frame. Another item that's going to help us when

119
05:25.440 --> 05:26.160
creating our virtual

120
05:26.160 --> 05:31.390
distributed switches is to remember to go ahead and enable Mac learning on the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

120
05:26.160 --> 05:31.390
distributed switches is to remember to go ahead and enable Mac learning on the

121
05:31.390 --> 05:32.320
virtual distributed

122
05:32.320 --> 05:36.950
switches, also allow Mac address changes. And we also want to allow forage

123
05:36.950 --> 05:38.320
transmits. So if we just

124
05:38.320 --> 05:42.450
make that consistent on each of our VDSs, then we won't have to worry later

125
05:42.450 --> 05:43.840
about something breaking

126
05:43.840 --> 05:48.950
or not working because they're not enabled. So as NSX has evolved now, it's in

127
05:48.950 --> 05:50.640
4.1X version as of

128
05:50.640 --> 05:55.710
this recording, instead of NSX creating its own NSX virtual distributed switch,

129
05:55.710 --> 05:57.360
we're now leveraging

130
05:57.360 --> 06:01.440
our existing virtual distributed switches that are in the vSphere environment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

130
05:57.360 --> 06:01.440
our existing virtual distributed switches that are in the vSphere environment.

131
06:01.440 --> 06:02.080
And as part of that

132
06:02.080 --> 06:05.880
to make everything work, if we have these three settings enabled for all of our

133
06:05.880 --> 06:06.800
virtual distributed

134
06:06.800 --> 06:11.650
switches, including the 9000 byte MTU, we're going to avoid a lot of headaches

135
06:11.650 --> 06:12.640
along the way.

136
06:12.640 --> 06:16.560
So let's take a look at the top of rack switch, which again, I have a 3750 that

137
06:16.560 --> 06:17.040
I'm using from

138
06:17.040 --> 06:21.200
Cisco systems. And let's verify that I have ports set up for trunking and also

139
06:21.200 --> 06:21.840
that I have all the

140
06:21.840 --> 06:26.660
VLANs that I need for my topology. Also, while we're there, we can also confirm

141
06:26.660 --> 06:27.280
that we have

142
06:27.280 --> 06:31.520
routing in place, which will also be performed by the top of rack switch. Oh,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

142
06:27.280 --> 06:31.520
routing in place, which will also be performed by the top of rack switch. Oh,

143
06:31.520 --> 06:32.000
and you know what,

144
06:32.000 --> 06:35.690
there's one other connection. I want to go ahead and add this topology here as

145
06:35.690 --> 06:36.400
well. And that's

146
06:36.400 --> 06:40.100
with one of these ports. It's connected out to my management network. So here's

147
06:40.100 --> 06:40.720
my management

148
06:40.720 --> 06:46.920
network in my home office here. It's the 192 168 one network address space. And

149
06:46.920 --> 06:47.680
on that network,

150
06:47.680 --> 06:53.290
I've got my management PC right here, which is at dot 151. I've also got my

151
06:53.290 --> 06:54.800
logical vCenter

152
06:54.800 --> 06:59.920
on that same address base of 192 168 one as well. So I'll call this VCS a prod.

153
06:59.920 --> 07:00.800
And this is the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

153
06:59.920 --> 07:00.800
And this is the

154
07:00.800 --> 07:04.660
vCenter server right here that's managing all the physical hosts. And then once

155
07:04.660 --> 07:05.520
we start deploying

156
07:05.520 --> 07:10.240
our nested environment here, we're going to deploy yet another vCenter on one

157
07:10.240 --> 07:12.320
of our nested ES6i hosts.

158
07:12.320 --> 07:16.600
And I'll explain the benefit of why that's important to do as we proceed. Also

159
07:16.600 --> 07:17.680
off of this network,

160
07:17.680 --> 07:22.800
I have a router and that routers at dot one that router has internet access and

161
07:22.800 --> 07:23.280
is performing

162
07:23.280 --> 07:27.120
network address translation as well for traffic going out towards the internet.

163
07:27.120 --> 07:27.680
If it's coming in

164
07:27.680 --> 07:31.780
from the 192 168 one address space. So with that in mind, let's take a look at
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

164
07:27.680 --> 07:31.780
from the 192 168 one address space. So with that in mind, let's take a look at

165
07:31.780 --> 07:32.880
the top of rack switch

166
07:32.880 --> 07:38.290
just to confirm that I have the MTU support for jumbo frames of at least 9000

167
07:38.290 --> 07:39.360
bytes. Also that

168
07:39.360 --> 07:42.840
I have all the VLANs that I need. And also for any ports that are connected to

169
07:42.840 --> 07:44.560
my physical ES6i host

170
07:44.560 --> 07:49.290
that they are set up for trunking. All right, so here is my top of rack switch.

171
07:49.290 --> 07:49.600
With the show

172
07:49.600 --> 07:54.610
version command showing it's a Cisco 3750E. And as far as the software is

173
07:54.610 --> 07:55.600
currently running

174
07:55.600 --> 08:00.940
is 15 dot X. And if we did a show system MTU on the Cisco switch here, it's
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

174
07:55.600 --> 08:00.940
is 15 dot X. And if we did a show system MTU on the Cisco switch here, it's

175
08:00.940 --> 08:01.760
showing us that we're

176
08:01.760 --> 08:06.050
supporting our jumbo MTUs. And all I really need is 9000. But if your switch

177
08:06.050 --> 08:07.040
supports a little more

178
08:07.040 --> 08:11.290
than 9000, that'll work as well. I still want to have a bottleneck or a problem

179
08:11.290 --> 08:12.240
at the top of rack

180
08:12.240 --> 08:15.240
switch. In the event a jumbo frame is sent, I want to make sure the switch is

181
08:15.240 --> 08:16.400
going to go ahead and

182
08:16.400 --> 08:20.070
forward it. So now that we've confirmed we can support a larger than normal

183
08:20.070 --> 08:21.120
frame size. Next,

184
08:21.120 --> 08:24.240
let's take a look at the routing table to show IP route on the Cisco router

185
08:24.240 --> 08:25.360
will press enter

186
08:25.360 --> 08:28.550
at space bar a few times. There's quite a few routes, but I just want to

187
08:28.550 --> 08:29.840
confirm and demonstrate

188
08:29.840 --> 08:33.840
that this top of rack switch has not only the ability to layer two switching,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

188
08:29.840 --> 08:33.840
that this top of rack switch has not only the ability to layer two switching,

189
08:33.840 --> 08:34.800
but it also

190
08:34.800 --> 08:39.280
has logical layer three interfaces. So if we scroll over here, I've got a local

191
08:39.280 --> 08:40.640
interface of 11 11

192
08:40.640 --> 08:44.380
11 dot one, which happens to be the default gateway for one of my transport

193
08:44.380 --> 08:45.200
nodes. And that's

194
08:45.200 --> 08:49.670
associated with VLAN 101. And then I also have a logical layer three address

195
08:49.670 --> 08:50.640
associated with

196
08:50.640 --> 08:54.600
VLAN 102, which is being used by another transport node. And then one with an

197
08:54.600 --> 08:56.960
IP address of 3333.1,

198
08:56.960 --> 09:01.600
that's being used in combination with VLAN 103. So this helps confirm that we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

198
08:56.960 --> 09:01.600
that's being used in combination with VLAN 103. So this helps confirm that we

199
09:01.600 --> 09:02.160
are supporting

200
09:02.160 --> 09:07.100
routing on this device. And if we did a show VLAN brief here on the Cisco

201
09:07.100 --> 09:08.160
switch, and I call

202
09:08.160 --> 09:11.720
a switch, but it's really a multi layer switch that does routing and switching

203
09:11.720 --> 09:12.480
here, it's confirming

204
09:12.480 --> 09:17.610
a list of all the VLANs that it currently has. So if we're using VLAN 23, we'd

205
09:17.610 --> 09:18.240
want to make sure

206
09:18.240 --> 09:22.090
VLAN 23 exists. If we're using VLAN 24, we'd want to make sure VLAN 24 exists

207
09:22.090 --> 09:23.600
and so forth and so on.

208
09:23.600 --> 09:29.320
So I have every single VLAN and more that we'll be using as part of my lab

209
09:29.320 --> 09:30.160
environment,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

209
09:29.320 --> 09:30.160
environment,

210
09:30.160 --> 09:33.750
including all these VLANs, which I'm using as part of my transport network. I

211
09:33.750 --> 09:34.320
've also got a

212
09:34.320 --> 09:38.520
port on this switch that goes out to my physical network and that's off of its

213
09:38.520 --> 09:39.920
interface VLAN 1.

214
09:39.920 --> 09:44.550
So if we did a show IP interface for VLAN 1, press dinner, there's its IP

215
09:44.550 --> 09:46.080
address right there,

216
09:46.080 --> 09:50.030
and its default gateway from its routing table is at .1. So if we tried to ping

217
09:50.030 --> 09:53.520
for example 192.168.1.1,

218
09:53.520 --> 09:56.880
which is my default gateway going out towards the internet, we can reach that.

219
09:56.880 --> 09:57.360
And if we tried

220
09:57.360 --> 10:02.020
to ping for example out to 8 at 8 to 8 that's also going to work because the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

220
09:57.360 --> 10:02.020
to ping for example out to 8 at 8 to 8 that's also going to work because the

221
10:02.020 --> 10:03.200
router at this IP

222
10:03.200 --> 10:06.430
address on my local network here is also supporting network address translation

223
10:06.430 --> 10:07.360
services for me.

224
10:07.360 --> 10:10.780
The last thing I want to verify as well is my trunking. So here on the Cisco K

225
10:10.780 --> 10:11.200
elle switch,

226
10:11.200 --> 10:16.480
we'll do a show interface trunk press enter. And I currently have one trunk and

227
10:16.480 --> 10:17.040
it's this one right

228
10:17.040 --> 10:21.120
here. This is the 10 gig port and it's supporting all of these VLANs. So truth

229
10:21.120 --> 10:22.080
be told behind the

230
10:22.080 --> 10:27.050
scenes, I actually have a switch here and then I have another switch here. So

231
10:27.050 --> 10:28.720
this is my Cisco 3750

232
10:28.720 --> 10:32.020
and up here I think it's a trend net. And so this connection right here, this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

232
10:28.720 --> 10:32.020
and up here I think it's a trend net. And so this connection right here, this

233
10:32.020 --> 10:34.480
trunk is from my 3750

234
10:34.480 --> 10:38.360
going up to my trend net and then the trend here have the trunk ports that go

235
10:38.360 --> 10:39.280
out to the physical

236
10:39.280 --> 10:42.700
ESXI hosts. And because this connection right here is a trunk port between

237
10:42.700 --> 10:44.000
these two physical

238
10:44.000 --> 10:48.680
switches, these VLANs, which are really just layer two broadcast domains exist

239
10:48.680 --> 10:49.520
across both

240
10:49.520 --> 10:53.660
those switches. So in my topology as well, because I have two switches involved

241
10:53.660 --> 10:54.640
here, I need to make

242
10:54.640 --> 11:00.240
sure that any VLANs I plan on using exist not only here, but also on here. So
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

242
10:54.640 --> 11:00.240
sure that any VLANs I plan on using exist not only here, but also on here. So

243
11:00.240 --> 11:01.360
we can kind of think

244
11:01.360 --> 11:05.570
of this logically as my top of rack switching environment. And once again, we

245
11:05.570 --> 11:06.320
want to make

246
11:06.320 --> 11:10.280
sure that any VLANs that we plan on using, make sure they're supported by your

247
11:10.280 --> 11:11.520
top of rack switches.

248
11:11.520 --> 11:15.050
All right. So now that we've taken a look at the top of rack switches, we

249
11:15.050 --> 11:16.240
verified jumbo frame

250
11:16.240 --> 11:20.020
support. We verified they have the right VLANs that are needed for our lab top

251
11:20.020 --> 11:21.040
ology. We also

252
11:21.040 --> 11:25.670
verified we have connectivity to my external network, the 192.1 state one

253
11:25.670 --> 11:27.200
network with a router out

254
11:27.200 --> 11:30.680
there that can lead us off towards the internet if we need to. Our next logical
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

254
11:27.200 --> 11:30.680
there that can lead us off towards the internet if we need to. Our next logical

255
11:30.680 --> 11:31.440
step then is to

256
11:31.440 --> 11:35.900
take a look at the actual VMs that we're going to be using inside of our lab

257
11:35.900 --> 11:37.600
environment, including

258
11:37.600 --> 11:42.000
our nested ESXi host. So we'll continue this journey taking a closer look at

259
11:42.000 --> 11:42.880
the VMs and the

260
11:42.880 --> 11:46.800
nested VMs in the next video. I'll see you there in just a moment.