WEBVTT

1
00:00.000 --> 00:02.400
Now logically, one might look at our topology and say,

2
00:02.400 --> 00:06.040
"Well, this DR, if it needs to forward traffic to .1,"

3
00:06.040 --> 00:07.840
it would just go ahead and forward out this interface.

4
00:07.840 --> 00:09.840
But the reason I put additional space here

5
00:09.840 --> 00:12.440
is there as a little stop along the way

6
00:12.440 --> 00:13.440
that's going to be made,

7
00:13.440 --> 00:15.920
and that is our services router function

8
00:15.920 --> 00:17.440
on our tier zero gateway.

9
00:17.440 --> 00:19.680
So I'm going to put that right here.

10
00:19.680 --> 00:20.880
So this is our SR.

11
00:20.880 --> 00:23.920
So all these are distributed router for gateway A,

12
00:23.920 --> 00:25.680
distributed router for gateway zero,

13
00:25.680 --> 00:29.040
and this is the services router for gateway zero.

14
00:29.040 --> 00:30.640
And then we clean that up a little bit
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

14
00:29.040 --> 00:30.640
And then we clean that up a little bit

15
00:30.640 --> 00:32.400
and add gateway zero here.

16
00:32.400 --> 00:33.840
And this services router,

17
00:33.840 --> 00:36.720
let's also document what its UUID is

18
00:36.720 --> 00:38.640
and also the VRF that it's in.

19
00:38.640 --> 00:39.840
So for these services router,

20
00:39.840 --> 00:41.120
this row right here,

21
00:41.120 --> 00:44.720
it is VRF4 and there is the UUID.

22
00:44.720 --> 00:46.480
So we'll add that to our documentation.

23
00:46.480 --> 00:48.320
So it begins with F5,

24
00:48.320 --> 00:49.840
a whole bunch of characters,

25
00:49.840 --> 00:52.000
and it ends with E5.

26
00:52.000 --> 00:56.160
And on the edge one device that is in VRF number four.

27
00:56.160 --> 00:58.880
And then we have some logical connectivity via IP,

28
00:58.880 --> 01:01.200
between the gateway zero,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
00:58.880 --> 01:01.200
between the gateway zero,

29
01:01.200 --> 01:02.720
distributed router function,

30
01:02.720 --> 01:05.280
and the gateway zero services router function,

31
01:05.280 --> 01:07.440
which is actually going to do the actual connection

32
01:07.440 --> 01:08.400
to the physical network.

33
01:08.400 --> 01:09.760
So that's going to go like this.

34
01:09.760 --> 01:11.040
Also, let's go ahead and document

35
01:11.040 --> 01:13.040
the connectivity IP address involved

36
01:13.040 --> 01:15.360
on this leg of our journey right here.

37
01:15.360 --> 01:16.800
And we can look at the information

38
01:16.800 --> 01:20.400
from the perspective of the DR on gateway zero

39
01:20.400 --> 01:22.640
or from the SR on gateway zero.

40
01:22.640 --> 01:25.120
Let's start off with the DR on gateway zero.

41
01:25.120 --> 01:26.640
So that's VRF number one.

42
01:26.640 --> 01:29.040
So we'll type in VRF1 press enter.

43
01:29.040 --> 01:31.120
So now we're looking at the details for VRF1,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

43
01:29.040 --> 01:31.120
So now we're looking at the details for VRF1,

44
01:31.120 --> 01:32.480
let me make that a little bit bigger.

45
01:32.480 --> 01:35.840
Again, that's our distributed router for our tier zero gateway.

46
01:35.840 --> 01:38.640
So in VRF1, if we do a get forwarding,

47
01:38.640 --> 01:40.080
I'll do a space question mark,

48
01:40.080 --> 01:43.760
and let's look for 000/0 press enter.

49
01:43.760 --> 01:45.680
So here's the default route that we just set up

50
01:45.680 --> 01:46.880
a few moments ago.

51
01:46.880 --> 01:50.080
And the next top is 192.168.1.1.

52
01:50.080 --> 01:52.080
However, here on VRF1,

53
01:52.080 --> 01:54.320
which is gateway zero, the DR,

54
01:54.320 --> 01:57.680
if we do a get interfaces and press enter,

55
01:57.680 --> 02:00.880
here are the interfaces associated with VRF1,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
01:57.680 --> 02:00.880
here are the interfaces associated with VRF1,

56
02:00.880 --> 02:03.840
which is again our DR on gateway zero.

57
02:03.840 --> 02:04.720
So if we scroll in here,

58
02:04.720 --> 02:08.320
here's a logical interface between our tier zero DR

59
02:08.320 --> 02:10.640
and down to, looks like gateway A.

60
02:10.640 --> 02:13.360
And this confirms the IP addresses that we documented previously.

61
02:13.360 --> 02:15.680
So on that link down to gateway A,

62
02:15.680 --> 02:18.800
on this side, we're using 160 four zero dot zero

63
02:18.800 --> 02:19.840
with a 31 bit mask.

64
02:19.840 --> 02:20.960
And on the other side,

65
02:20.960 --> 02:23.600
which was gateway A, it's using dot one.

66
02:23.600 --> 02:25.280
And if we can need to scroll down,

67
02:25.280 --> 02:26.400
here's another interface.

68
02:26.400 --> 02:28.720
This is the one that goes down to gateway B

69
02:28.720 --> 02:30.080
based on the name there.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

69
02:28.720 --> 02:30.080
based on the name there.

70
02:30.080 --> 02:33.600
And it's using locally 160 four zero two.

71
02:33.600 --> 02:34.560
And on the other side,

72
02:34.560 --> 02:36.960
gateway B would be using dot three on that common segment.

73
02:36.960 --> 02:38.160
And if we scroll down,

74
02:38.160 --> 02:40.640
here's the interface used for a multicast,

75
02:40.640 --> 02:42.400
as we continue to scroll down.

76
02:42.400 --> 02:44.800
Here is yet another fascinating interface.

77
02:44.800 --> 02:48.080
And its name is BP for backplane DR,

78
02:48.080 --> 02:49.680
distributed router port.

79
02:49.680 --> 02:50.720
And here for the port type,

80
02:50.720 --> 02:52.000
it says backplane.

81
02:52.000 --> 02:56.320
And here it has an IP address of 169 two fifty four zero dot one.

82
02:56.320 --> 02:59.040
So that IP address base of 169 two fifty four

83
02:59.040 --> 03:03.600
is what's being used to communicate between the DR on gateway zero
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

83
02:59.040 --> 03:03.600
is what's being used to communicate between the DR on gateway zero

84
03:03.600 --> 03:05.840
and the SR on gateway zero.

85
03:05.840 --> 03:08.400
So I'm going to add that IP address to our documentation right now.

86
03:08.400 --> 03:11.680
So I'm going to go ahead and label this as BP for backplane.

87
03:11.680 --> 03:14.640
And the network is 169 two fifty four zero

88
03:14.640 --> 03:16.160
with a 24 bit mask.

89
03:16.160 --> 03:17.920
And we just saw here on gateway zero,

90
03:17.920 --> 03:20.080
choosing the address of dot one.

91
03:20.080 --> 03:21.440
And then over here, the services router,

92
03:21.440 --> 03:22.880
it's very likely going to be a dot two.

93
03:22.880 --> 03:24.320
We'll verify that here in a moment.

94
03:24.320 --> 03:25.280
So here in this output,

95
03:25.280 --> 03:28.320
we are currently looking at VRF one,

96
03:28.320 --> 03:31.360
which is our distributed router on tier zero.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
03:28.320 --> 03:31.360
which is our distributed router on tier zero.

97
03:31.360 --> 03:32.960
And as we got near the end of it,

98
03:32.960 --> 03:35.920
this last one here is the backplane interface.

99
03:35.920 --> 03:36.640
But check this out,

100
03:36.640 --> 03:38.400
it's also showing us that same output.

101
03:38.400 --> 03:40.000
This is again for VRF one,

102
03:40.000 --> 03:43.920
that we have this associated VRF four and its set of interfaces.

103
03:43.920 --> 03:46.400
And VRF four is our services router.

104
03:46.400 --> 03:47.760
And if we scroll down,

105
03:47.760 --> 03:48.800
our services router,

106
03:48.800 --> 03:50.480
we have a backplane interface.

107
03:50.480 --> 03:54.400
The name is BP SR zero port for services router zero.

108
03:54.400 --> 03:57.920
And its IP address is 169 two fifty four zero dot two,

109
03:57.920 --> 04:00.080
which confirms what we just jotted down in our topology.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

109
03:57.920 --> 04:00.080
which confirms what we just jotted down in our topology.

110
04:00.080 --> 04:04.320
So the logical connectivity between the DR on gateway zero

111
04:04.320 --> 04:08.080
and the SR on gateway zero is this logical subnet,

112
04:08.080 --> 04:12.240
169 two forty four zero with the DR function using dot one

113
04:12.240 --> 04:14.160
and the SR function using dot two.

114
04:14.160 --> 04:16.560
And as we continue looking at VRF four here,

115
04:16.560 --> 04:17.920
which is our services router,

116
04:17.920 --> 04:19.280
we continue to scroll down.

117
04:19.280 --> 04:19.840
Check it out.

118
04:19.840 --> 04:23.920
Look what we have here is a 192 168 1.60 address.

119
04:23.920 --> 04:29.600
And that is the virtual IP address that we assigned to the tier zero gateway.

120
04:29.600 --> 04:32.640
And this IP address is actually owned by the services router.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

120
04:29.600 --> 04:32.640
And this IP address is actually owned by the services router.

121
04:32.640 --> 04:36.400
So for the connectivity to the 192 168 one address,

122
04:36.400 --> 04:38.800
we would be using this logical interface,

123
04:38.800 --> 04:41.600
the services router interface for that connectivity.

124
04:41.600 --> 04:43.360
And so if we finished drawing our topology,

125
04:43.360 --> 04:45.920
it would look like this on this 192 network,

126
04:45.920 --> 04:48.240
we have the dot 60 right here.

127
04:48.240 --> 04:51.730
And then we have the rest of my physical network with the physical router here

128
04:51.730 --> 04:52.560
at dot one.

129
04:52.560 --> 04:57.360
So in a packet from VM one enters host A host A with this distributed router is

130
04:57.360 --> 04:58.080
going to do

131
04:58.080 --> 04:59.680
most of the routing decisions.

132
04:59.680 --> 05:03.040
And then at some point it's going to forward it over to edge one
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

132
04:59.680 --> 05:03.040
And then at some point it's going to forward it over to edge one

133
05:03.040 --> 05:06.460
who's providing the services router function to forward that packet onto the

134
05:06.460 --> 05:07.280
physical network.

135
05:07.280 --> 05:09.680
So I'm going to put in red here edge one.

136
05:09.680 --> 05:13.360
So for the VM that's being hosted by ESXIA for as a packet,

137
05:13.360 --> 05:17.040
the logical routing for gateway A is done by ESXIA.

138
05:17.040 --> 05:22.000
The logical routing for the DR gateway zero is being done by ESXIA.

139
05:22.000 --> 05:23.840
And then based on what we just saw,

140
05:23.840 --> 05:28.560
when the gateway zero DR needs to forward the packet to the next hop of dot two

141
05:28.560 --> 05:28.560
,

142
05:28.560 --> 05:31.600
because gateway zero is logically connected to that segment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

142
05:28.560 --> 05:31.600
because gateway zero is logically connected to that segment.

143
05:31.600 --> 05:34.480
And by the way, we can verify the actual VNI for that segment.

144
05:34.480 --> 05:36.080
Let's do that also right now.

145
05:36.080 --> 05:39.360
So here on edge one, we'll exit a VRF configuration mode.

146
05:39.360 --> 05:41.840
And let's go ahead and do a get segments.

147
05:41.840 --> 05:44.640
Or if you want to use the older command of get logical switches,

148
05:44.640 --> 05:45.840
that works too.

149
05:45.840 --> 05:48.400
So here's the segment for segment 20.

150
05:48.400 --> 05:50.560
Here's the segment for segment 10.

151
05:50.560 --> 05:54.240
And we have our transit links that go between our tier one gateways and our

152
05:54.240 --> 05:54.800
tier zero.

153
05:54.800 --> 05:58.320
So this one is and this one is we have one for multicast.

154
05:58.320 --> 06:00.640
And then we have this beautiful one right here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

154
05:58.320 --> 06:00.640
And then we have this beautiful one right here.

155
06:00.640 --> 06:04.080
So that is VNI 67584.

156
06:04.080 --> 06:06.240
So let's document that on our topology.

157
06:06.240 --> 06:11.760
So for this segment 67584, that's the VNI number.

158
06:11.760 --> 06:17.360
So ESXIA is logically connected to this segment 67584.

159
06:17.360 --> 06:21.360
And now it needs to forward to the layer two address on that same segment.

160
06:21.360 --> 06:23.040
Now that all the routing decisions are done,

161
06:23.040 --> 06:27.520
needs to forward to the layer two address associated with this IP address 169,

162
06:27.520 --> 06:30.320
254, zero dot two on this segment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

162
06:27.520 --> 06:30.320
254, zero dot two on this segment.

163
06:30.320 --> 06:33.520
And the control plane for NSX is going to let ESXIA know that,

164
06:33.520 --> 06:37.810
hey, that MAC address associated with this is going to be reachable off of the

165
06:37.810 --> 06:39.200
edge one VM

166
06:39.200 --> 06:41.600
that's supporting that services router.

167
06:41.600 --> 06:46.320
So from a tunnel perspective, ESXIA is going to forward traffic over the tunnel

168
06:46.320 --> 06:48.960
over to the tunnel endpoint for edge one.

169
06:48.960 --> 06:52.560
So ESXIA is 11, 11, 11, 11, 11.

170
06:52.560 --> 06:57.280
And edge one is at 33 dot 33 dot 33 dot 33.

171
06:57.280 --> 06:59.280
And then edge one would pick up on the work.

172
06:59.280 --> 07:01.360
So edge one would receive that.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

172
06:59.280 --> 07:01.360
So edge one would receive that.

173
07:01.360 --> 07:03.760
It would do the logical routing for the traffic.

174
07:03.760 --> 07:08.320
So let's assume the client PC was originally trying to go to 192.1 state one

175
07:08.320 --> 07:09.200
dot one.

176
07:09.200 --> 07:13.090
So edge one would do that logical route lookup and then forward it to that

177
07:13.090 --> 07:13.680
segment,

178
07:13.680 --> 07:18.720
which in our case is that VLAN back segment for where my 192.168.1 network is.

179
07:18.720 --> 07:22.880
So if we capture the traffic right here, we would see traffic from 11, 11,

180
07:22.880 --> 07:26.720
etc. to 33, 33, and inside the genieve header,

181
07:26.720 --> 07:30.240
it would indicate is for VNI 6, 7, 5, 8, 4.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

181
07:26.720 --> 07:30.240
it would indicate is for VNI 6, 7, 5, 8, 4.

182
07:30.240 --> 07:34.800
And it would also identify the layer two address that we're trying to reach

183
07:34.800 --> 07:37.200
for that next top address on the services router.

184
07:37.200 --> 07:40.560
And again, then the services router would take a look at the IP header,

185
07:40.560 --> 07:41.680
see what the destination is.

186
07:41.680 --> 07:46.640
For example, 192.168.1 dot one, and then forward it appropriately based on its

187
07:46.640 --> 07:47.360
routing table.

188
07:47.360 --> 07:51.260
Now currently on this device, I set up a static route on this physical

189
07:51.260 --> 07:52.160
appliance to say,

190
07:52.160 --> 07:55.600
hey, if you ever need to reach the 1010 zero address space,

191
07:55.600 --> 08:00.160
go ahead and forward it back to the next top of 192.168.1 dot 60.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

191
07:55.600 --> 08:00.160
go ahead and forward it back to the next top of 192.168.1 dot 60.

192
08:00.160 --> 08:04.160
So that routing from the external network, that part's already in place.

193
08:04.160 --> 08:06.880
So what I like to do is let's just verify from this VM

194
08:06.880 --> 08:10.960
that we really can indeed reach the 192.168.1 network

195
08:10.960 --> 08:13.040
and specifically the dot one address here.

196
08:13.040 --> 08:15.120
And then once we verify we have the connectivity,

197
08:15.120 --> 08:17.280
let's go to trace flow. We'll verify it there.

198
08:17.280 --> 08:20.560
We can also capture the trace flow and see what it looks like

199
08:20.560 --> 08:22.960
as that traffic is going over the transport network.

200
08:22.960 --> 08:26.480
So let me bring in a little console for this little VM right here.

201
08:26.480 --> 08:29.440
And let's confirm its IP address with an IF config.

202
08:29.440 --> 08:31.840
And that looks good as 1010 zero 10.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

202
08:29.440 --> 08:31.840
And that looks good as 1010 zero 10.

203
08:31.840 --> 08:34.800
And let's also do a route, verify its route.

204
08:34.800 --> 08:37.040
So its default gateway is 1010 zero one,

205
08:37.040 --> 08:39.760
which is our logical DR for gateway A.

206
08:39.760 --> 08:42.880
And then the next top is the DR for gateway zero.

207
08:42.880 --> 08:46.240
And let's just confirm from the perspective of ESXIA that gateway zero,

208
08:46.240 --> 08:48.800
the DR believes that for its default route,

209
08:48.800 --> 08:52.800
the next top is going to be 169.250.2.

210
08:52.800 --> 08:58.080
So here at the NSX CLI for ESXIA host A, let's do a gate gateways.

211
08:58.080 --> 09:00.560
And then for the DR gateway zero,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

211
08:58.080 --> 09:00.560
And then for the DR gateway zero,

212
09:00.560 --> 09:03.280
based on our documentation is the one that ends in bed.

213
09:03.280 --> 09:05.840
That's this one right here. So I'll go ahead and copy that.

214
09:05.840 --> 09:08.240
We'll do a get gateway space.

215
09:08.240 --> 09:11.920
We'll plug in that UUID space and then we'll do a question mark.

216
09:11.920 --> 09:13.520
And let's just look at the IPV4 else.

217
09:13.520 --> 09:15.600
We'll specify IPV4 press enter.

218
09:15.600 --> 09:21.440
It says that it's default route has a next top of 169.250.2,

219
09:21.440 --> 09:26.080
which is the logical interface on the services router at tier zero.

220
09:26.080 --> 09:29.360
It also indicates here from the routing table that is directly connected.

221
09:29.360 --> 09:34.880
And this is the gateway zero DR being directly connected to the 169.2.4 network
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

221
09:29.360 --> 09:34.880
And this is the gateway zero DR being directly connected to the 169.2.4 network

222
09:34.880 --> 09:34.880
.

223
09:34.880 --> 09:39.600
And so ESXIA, as it needs to forward the traffic to that layer two address of

224
09:39.600 --> 09:40.800
the next top there,

225
09:40.800 --> 09:45.130
is going to leverage the NSX control plane to identify where that layer two

226
09:45.130 --> 09:45.920
address lives.

227
09:45.920 --> 09:50.560
So for ESXIA to forward on that segment to the layer two address associated

228
09:50.560 --> 09:53.360
with 169.2.2,

229
09:53.360 --> 09:56.000
which is the next top for the routing,

230
09:56.000 --> 09:58.240
it would encapsulate the traffic forward over to edge one,

231
09:58.240 --> 10:01.600
who had de-encapsulated, then continued the logical routing process.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

231
09:58.240 --> 10:01.600
who had de-encapsulated, then continued the logical routing process.