WEBVTT

1
00:00.120 --> 00:01.740
So let's start off with the big picture of

2
00:01.740 --> 00:02.940
what we hope to accomplish.

3
00:02.940 --> 00:05.790
Then we'll put a specific game plan together to get it done.

4
00:05.790 --> 00:09.450
So currently we have these two ESXI hosts A and B,

5
00:09.450 --> 00:12.480
which are acting as Host Transport Nodes.

6
00:12.480 --> 00:14.220
And effectively what that means is they can

7
00:14.220 --> 00:15.870
support NSX segments.

8
00:15.870 --> 00:18.720
They can also build a tunnel between each other

9
00:18.720 --> 00:20.910
to encapsulate and forward the traffic back and forth.

10
00:20.910 --> 00:22.770
Again, that tunnel would be a Geneve tunnel.

11
00:22.770 --> 00:26.190
Now, since the last skill where we deployed the ESXI host,

12
00:26.190 --> 00:27.870
I had a little meltdown in my rack,

13
00:27.870 --> 00:29.550
and so I had to reorganize a few things

14
00:29.550 --> 00:31.500
and I had to rebuild it all from scratch.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

14
00:29.550 --> 00:31.500
and I had to rebuild it all from scratch.

15
00:31.500 --> 00:34.590
So here is my current topology, which is similar to

16
00:34.590 --> 00:36.390
how we left it in the previous skill.

17
00:36.390 --> 00:39.300
So we have ESXI-A and ESXI-B,

18
00:39.300 --> 00:41.010
they currently have tunnel endpoints,

19
00:41.010 --> 00:42.720
which I've statically configured

20
00:42.720 --> 00:45.900
as 11, 11, 11, 11 here on ESXI-A

21
00:45.900 --> 00:48.870
and 22 22, 22, 22 over here

22
00:48.870 --> 00:49.770
on ESXI-B.

23
00:49.770 --> 00:52.410
And I thought to myself "Self, if I was learning this,

24
00:52.410 --> 00:54.570
what would I want to see as tunnel endpoints?"

25
00:54.570 --> 00:58.080
I thought I would want see some very different IP addressing

26
00:58.080 --> 00:59.670
and that way it'd be very clear

27
00:59.670 --> 01:02.115
whenever we see this IP address to remember, it's associated
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
00:59.670 --> 01:02.115
whenever we see this IP address to remember, it's associated

28
01:02.115 --> 01:05.220
as a TEP, tunnel endpoint, with ESXI-A.

29
01:05.220 --> 01:08.760
And this one over here is a tunnel endpoint for ESXI-B.

30
01:08.760 --> 01:10.560
And each of those tunnel endpoints are associated

31
01:10.560 --> 01:12.540
with a VM kernel adapter.

32
01:12.540 --> 01:15.030
And in our implementation here, NSX chose

33
01:15.030 --> 01:17.430
to use VMK10 on both sides

34
01:17.430 --> 01:20.220
for their respective layer three interfaces.

35
01:20.220 --> 01:22.320
And that's where that IP address is assigned.

36
01:22.320 --> 01:25.249
The 11, 11, 11, 11 here on ESXI-A,

37
01:25.249 --> 01:27.320
to the VM kernel adapter 10,

38
01:27.320 --> 01:30.300
and over on ESXI-B, the 22, 22, 22, 22,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:27.320 --> 01:30.300
and over on ESXI-B, the 22, 22, 22, 22,

39
01:30.300 --> 01:32.940
which is the tunnel end point over here on ESXI-B,

40
01:32.940 --> 01:35.790
it's associated with VM kernel 10 over here as well.

41
01:35.790 --> 01:36.900
So what I thought would be valuable

42
01:36.900 --> 01:38.910
to do is let's validate those as we go

43
01:38.910 --> 01:40.710
through this together just to make sure that

44
01:40.710 --> 01:43.260
what we think is in place really is there.

45
01:43.260 --> 01:45.630
So here is the login to the vSphere Client.

46
01:45.630 --> 01:47.370
So I'll go ahead and log in.

47
01:47.370 --> 01:48.990
And then while that's initializing, let's go over

48
01:48.990 --> 01:52.770
to the NSX manager and we'll log in here, as well.

49
01:52.770 --> 01:55.530
So here in the NSX manager, let's go to system

50
01:55.530 --> 01:57.660
by clicking on the system tab up here at the top.

51
01:57.660 --> 01:59.610
Now on the left we have system overview,

52
01:59.610 --> 02:01.860
it's showing us that we have one NSX management node
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
01:59.610 --> 02:01.860
it's showing us that we have one NSX management node

53
02:01.860 --> 02:04.410
and that's the NSX manager 11.

54
02:04.410 --> 02:05.880
And then we have two transport nodes

55
02:05.880 --> 02:07.380
that we added in a previous set of videos,

56
02:07.380 --> 02:09.360
that's ESXI-A and B.

57
02:09.360 --> 02:11.610
And we have three transport zones.

58
02:11.610 --> 02:14.640
One of those we created on our own and the other two were

59
02:14.640 --> 02:16.050
provided by default.

60
02:16.050 --> 02:18.330
And on the left, if we click here on "appliances",

61
02:18.330 --> 02:20.460
here it's showing us that our cluster is stable.

62
02:20.460 --> 02:23.310
We only have one NSX manager node here,

63
02:23.310 --> 02:24.420
but everything looks green.

64
02:24.420 --> 02:27.480
And if we click here on "view details", we can confirm

65
02:27.480 --> 02:29.460
that all the services are up and ready.

66
02:29.460 --> 02:30.930
So we'll go ahead and close that.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
02:29.460 --> 02:30.930
So we'll go ahead and close that.

67
02:30.930 --> 02:33.630
And then with systems still selected at the top on the left,

68
02:33.630 --> 02:36.810
if we expand fabric, if we now go to hosts,

69
02:36.810 --> 02:39.000
we can verify the details for ESXI hosts

70
02:39.000 --> 02:41.370
that have been enabled as Host Transport Nodes.

71
02:41.370 --> 02:44.520
Let's expand the cluster called Host Transport Nodes.

72
02:44.520 --> 02:47.760
And here we have ESXI-A and ESXI-B.

73
02:47.760 --> 02:49.200
And under IP addresses, if we click

74
02:49.200 --> 02:50.520
where it says "two more",

75
02:50.520 --> 02:52.230
it's showing us we have three addresses.

76
02:52.230 --> 02:56.310
So the 192, 168, 1, 181, that's the management address.

77
02:56.310 --> 02:59.400
The 10, 4, 0, 181 is an IP address associated with a

78
02:59.400 --> 03:02.070
VM kernel adapter that I'm using for access to an
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

78
02:59.400 --> 03:02.070
VM kernel adapter that I'm using for access to an

79
03:02.070 --> 03:03.420
iSCSI data store.

80
03:03.420 --> 03:06.480
And this third one right here is the tunnel endpoint.

81
03:06.480 --> 03:07.527
And if we go down to ESXI-B

82
03:07.527 --> 03:09.360
and we click right here where it says "two more"

83
03:09.360 --> 03:12.720
to see the addresses, there's 22, 22, 22, 22.

84
03:12.720 --> 03:14.520
And to validate that also, we can go over

85
03:14.520 --> 03:16.110
to the vSphere Client.

86
03:16.110 --> 03:18.660
So here on the vSphere Client, if we go over to the host

87
03:18.660 --> 03:21.177
and clusters view and we go to ESXI-A

88
03:21.177 --> 03:23.130
and we go to configure.

89
03:23.130 --> 03:24.630
And then here in the middle pane, if we go down

90
03:24.630 --> 03:27.150
to VMkernel adapters, we can just verify that, as well.

91
03:27.150 --> 03:31.350
So here's VMK10 with the IP address of 11, 11, 11, 11.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
03:27.150 --> 03:31.350
So here's VMK10 with the IP address of 11, 11, 11, 11.

92
03:31.350 --> 03:33.750
Lemme go ahead and make that column a little bit bigger.

93
03:33.750 --> 03:34.860
There we go. That looks a little better.

94
03:34.860 --> 03:37.936
So here for VMK10, click here on "IP settings",

95
03:37.936 --> 03:40.521
there's its IP address with the 24 bit mask

96
03:40.521 --> 03:43.950
and the default gateway is at 11.11.11.1.

97
03:43.950 --> 03:46.290
And if you take a look at ESXI-B

98
03:46.290 --> 03:48.630
and take a look at its VM kernel 10 adapter,

99
03:48.630 --> 03:50.790
it's at 22, 22, 22, 22

100
03:50.790 --> 03:54.540
with a default gateway of 22.22.22.1.

101
03:54.540 --> 03:57.630
So this represents the Geneve tunnel that they can use

102
03:57.630 --> 04:00.150
to encapsulate and de-encapsulate respectively,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

102
03:57.630 --> 04:00.150
to encapsulate and de-encapsulate respectively,

103
04:00.150 --> 04:01.560
as they forward traffic back

104
04:01.560 --> 04:04.620
and forth on behalf of the VMs on the various segments.

105
04:04.620 --> 04:05.880
And when they build that tunnel,

106
04:05.880 --> 04:07.680
they're gonna be using the transport network

107
04:07.680 --> 04:09.120
to carry the actual packets.

108
04:09.120 --> 04:11.820
So if these two ESXI hosts A and B are in different racks,

109
04:11.820 --> 04:12.870
we could do something like this,

110
04:12.870 --> 04:16.707
have the top of rack switches here, where ESXI-A is,

111
04:16.707 --> 04:19.200
and a couple top of rack switches over here

112
04:19.200 --> 04:20.520
where ESXI-B is.

113
04:20.520 --> 04:22.860
And maybe we have the Uplink two go here,

114
04:22.860 --> 04:24.510
And the Uplink three go here.

115
04:24.510 --> 04:26.820
And Uplink two go here, and Uplink three go here

116
04:26.820 --> 04:27.810
for redundancy.

117
04:27.810 --> 04:30.120
So those are our top of rack switches.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
04:27.810 --> 04:30.120
So those are our top of rack switches.

118
04:30.120 --> 04:34.080
I'll call it TORA for rack A. And maybe this is rack B.

119
04:34.080 --> 04:36.960
So I've got a top of rack switches for rack B

120
04:36.960 --> 04:39.030
and we're gonna have some connectivity between those.

121
04:39.030 --> 04:41.562
So let me go ahead and put a router here.

122
04:41.562 --> 04:43.020
So we can have a spine leaf architecture with the top

123
04:43.020 --> 04:44.400
of rack switches being the leaf.

124
04:44.400 --> 04:46.680
And then this device right here

125
04:46.680 --> 04:48.900
that's gluing them all together with routing acting

126
04:48.900 --> 04:51.570
as the spine, or one of our multilayer switches

127
04:51.570 --> 04:53.760
that's participating as part of the spine layer.

128
04:53.760 --> 04:56.190
And that would provide us fall tolerance from this ESXI

129
04:56.190 --> 04:58.557
host going to two different switches here.

130
04:58.557 --> 05:01.170
And the same thing for ESXI-B with two Uplinks going
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

130
04:58.557 --> 05:01.170
And the same thing for ESXI-B with two Uplinks going

131
05:01.170 --> 05:02.520
to two different switches.

132
05:02.520 --> 05:05.760
This could be switch one and switch two in rack A.

133
05:05.760 --> 05:07.380
And this is the top of rack switch one

134
05:07.380 --> 05:09.120
and two over here in rack B.

135
05:09.120 --> 05:11.070
So just to confirm this, in our lab environment here we're

136
05:11.070 --> 05:12.480
regarding the transport network,

137
05:12.480 --> 05:15.060
lemme give you a sneak peek into the world of my top

138
05:15.060 --> 05:17.490
of rack switch, which again is being implemented

139
05:17.490 --> 05:19.440
by a Cisco Catalyst switch.

140
05:19.440 --> 05:22.140
So lemme bring that in. Here it is right here.

141
05:22.140 --> 05:24.030
So if I did a show IP route

142
05:24.030 --> 05:26.460
for 11.11.11.11.

143
05:26.460 --> 05:27.330
Press enter,

144
05:27.330 --> 05:30.480
that's gonna show me from the routing table which route it
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

144
05:27.330 --> 05:30.480
that's gonna show me from the routing table which route it

145
05:30.480 --> 05:31.800
would use to reach that destination address,

146
05:31.800 --> 05:35.010
which is the tunnel endpoint over on ESXI-A.

147
05:35.010 --> 05:37.136
And if we do the same thing

148
05:37.136 --> 05:40.440
for show IP route for 22.22.22.22,

149
05:40.440 --> 05:42.480
we should also have a route for that, as well.

150
05:42.480 --> 05:44.340
In addition, I should also be able to ping those

151
05:44.340 --> 05:45.270
because I have routes for them.

152
05:45.270 --> 05:48.630
So let's do a ping to 11.11.11.11,

153
05:48.630 --> 05:52.020
that's the tunnel endpoint for ESXI-A.

154
05:52.020 --> 05:53.850
And if we do a ping to

155
05:53.850 --> 05:58.560
22.22.22.22, that's the tunnel endpoint for ESXI-B.

156
05:58.560 --> 06:00.720
So if I do a show IP route, I've got routes
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

156
05:58.560 --> 06:00.720
So if I do a show IP route, I've got routes

157
06:00.720 --> 06:04.260
for the 11 11 11 network and also the 22 22 22 network.

158
06:04.260 --> 06:06.690
And in my lab environment, I'm doing the entire routing

159
06:06.690 --> 06:08.580
through one catalyst switch.

160
06:08.580 --> 06:10.980
And then I intentionally used multiple VLANs

161
06:10.980 --> 06:14.040
and different subnets just to help reflect the concept

162
06:14.040 --> 06:16.470
that these two ESXI hosts don't have

163
06:16.470 --> 06:18.030
to be on the same subnet.

164
06:18.030 --> 06:20.250
AKA, they don't have to be on the same layer two

165
06:20.250 --> 06:23.370
broadcast domain for tunnel traffic to go back and forth

166
06:23.370 --> 06:24.203
between them.

167
06:24.203 --> 06:26.790
And let's also talk about and confirm the Uplinks

168
06:26.790 --> 06:30.060
that our ESXI hosts are gonna use if they're gonna access
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

168
06:26.790 --> 06:30.060
that our ESXI hosts are gonna use if they're gonna access

169
06:30.060 --> 06:32.430
the transport network to build these tunnels,

170
06:32.430 --> 06:35.100
or in this case the single tunnel between ESXI-A

171
06:35.100 --> 06:37.680
and ESXI-B with one TEP each.

172
06:37.680 --> 06:40.680
In NSX we specify which Uplinks to use

173
06:40.680 --> 06:43.620
and which VLANs to use in combination with those Uplinks

174
06:43.620 --> 06:46.380
by creating and then using an Uplink profile.

175
06:46.380 --> 06:49.530
And that Uplink profile is gonna specify for the ESXI host,

176
06:49.530 --> 06:52.410
which Uplink or Uplinks we're gonna be using.

177
06:52.410 --> 06:53.640
And we're also gonna specify as part

178
06:53.640 --> 06:55.950
of the Uplink profile, which VLAN to use.

179
06:55.950 --> 06:57.930
So my switched environment for all the connections

180
06:57.930 --> 06:59.760
that are coming up to the ESXI host,

181
06:59.760 --> 07:01.500
they're all set up as trunks.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

181
06:59.760 --> 07:01.500
they're all set up as trunks.

182
07:01.500 --> 07:04.620
So that way if we wanna support any VLANs on the physical

183
07:04.620 --> 07:06.810
network, we can use those right here.

184
07:06.810 --> 07:07.710
So let's measure on the switch.

185
07:07.710 --> 07:11.370
We have everything from one to 200 as far as VLANs go.

186
07:11.370 --> 07:13.200
And we're trunking on all ports.

187
07:13.200 --> 07:14.760
So if we have connections that go

188
07:14.760 --> 07:16.890
to our trunked infrastructure right here,

189
07:16.890 --> 07:19.530
that means we could choose to use any individual VLANs

190
07:19.530 --> 07:22.290
we want to with 8020.1 Q trunking.

191
07:22.290 --> 07:24.060
So for example, in our Uplink profile,

192
07:24.060 --> 07:26.425
if we said we wanna use Uplink2

193
07:26.425 --> 07:31.140
and we wanna use VLAN 101, we would specify that as part
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

193
07:26.425 --> 07:31.140
and we wanna use VLAN 101, we would specify that as part

194
07:31.140 --> 07:33.840
of the Uplink profile, including the fact we use this name

195
07:33.840 --> 07:36.420
called Uplink2 and we wanna use VLAN 1.

196
07:36.420 --> 07:39.540
And then when we configure ESXI-A or reconfigure

197
07:39.540 --> 07:41.070
for that matter, ESXI-A,

198
07:41.070 --> 07:42.882
we can simply specify that Uplink profile

199
07:42.882 --> 07:45.585
and as a result, it'll use the specified Uplink that we map

200
07:45.585 --> 07:47.820
to off of the physical host.

201
07:47.820 --> 07:50.490
It'll also go ahead and use the VLAN that we specify

202
07:50.490 --> 07:52.020
as part of the Uplink profile.

203
07:52.020 --> 07:53.850
So if we specify it in the Uplink profile

204
07:53.850 --> 07:56.590
that we wanna use VLAN 101 and Uplink2,

205
07:56.590 --> 07:59.151
this ESXI Host Transport Node,

206
07:59.151 --> 08:01.530
as it communicates on the transport network,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

206
07:59.151 --> 08:01.530
as it communicates on the transport network,

207
08:01.530 --> 08:04.620
is gonna be tagging all the frames that go out the Uplink

208
08:04.620 --> 08:07.440
with a 8020.1 Q tag of 101.

209
08:07.440 --> 08:09.750
And that way the receiving switch on the physical network

210
08:09.750 --> 08:11.460
can associate that with the correct layer two

211
08:11.460 --> 08:14.670
broadcast domain and then perform the routing, for example,

212
08:14.670 --> 08:17.130
to get from the 11, 11, 11s address base

213
08:17.130 --> 08:19.413
to the 22, 22, 22 address base.