WEBVTT

1
00:00.240 --> 00:01.380
And as a quick reminder,

2
00:01.380 --> 00:02.850
here's what we did in the previous skill.

3
00:02.850 --> 00:05.363
We deployed this single Tier-1

4
00:05.363 --> 00:07.740
virtualized routing function in NSX.

5
00:07.740 --> 00:09.120
We refer to it as a gateway.

6
00:09.120 --> 00:10.950
And that gateway as a distributed router

7
00:10.950 --> 00:13.680
lives here on ESXi-A.

8
00:13.680 --> 00:15.930
That distributed router lives here on ESXi-B

9
00:15.930 --> 00:18.450
both as transport nodes, so that either one of them

10
00:18.450 --> 00:20.663
has all the information regarding in the interfaces

11
00:20.663 --> 00:22.260
and the logical routing

12
00:22.260 --> 00:24.120
that this Tier-1 Gateway can provide.

13
00:24.120 --> 00:25.440
And that way if, for example,

14
00:25.440 --> 00:28.414
this VM here wants to communicate with this VM here,

15
00:28.414 --> 00:30.598
this local ESXi host can provide
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

15
00:28.414 --> 00:30.598
this local ESXi host can provide

16
00:30.598 --> 00:32.700
all that logical routing service

17
00:32.700 --> 00:35.490
between those two VMs on those two different segments,

18
00:35.490 --> 00:37.620
which again are on two different subnets.

19
00:37.620 --> 00:39.450
Or in the case of this VM here,

20
00:39.450 --> 00:42.810
communicating with this VM over here, VM-1 to VM-4,

21
00:42.810 --> 00:45.752
the local ESXi host having a copy of that distributed router

22
00:45.752 --> 00:48.060
can go ahead and make the routing decision first

23
00:48.060 --> 00:49.470
and then forward the traffic

24
00:49.470 --> 00:52.380
over the GENEVE tunnel over to ESXi-B.

25
00:52.380 --> 00:54.600
And that way, ESXi-B can forward that traffic over

26
00:54.600 --> 00:57.630
to the final destination, in this case, VM-4.

27
00:57.630 --> 01:01.410
And that's all with a single Tier-1 distributed router
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
00:57.630 --> 01:01.410
And that's all with a single Tier-1 distributed router

28
01:01.410 --> 01:05.100
doing East-West traffic routing inside of our topology.

29
01:05.100 --> 01:06.886
So with that in mind, from our previous skill,

30
01:06.886 --> 01:09.750
let's build upon that and let's put a plan together

31
01:09.750 --> 01:12.780
to add some additional distributed routers.

32
01:12.780 --> 01:14.400
And here is what I propose we do.

33
01:14.400 --> 01:16.034
Instead of just having one Tier-1 router

34
01:16.034 --> 01:17.820
for our East to West routing,

35
01:17.820 --> 01:19.110
let's go ahead and add another one.

36
01:19.110 --> 01:21.120
So, we currently have our first gateway in place.

37
01:21.120 --> 01:23.550
It was doing the routing between Segment 10 and Segment 20.

38
01:23.550 --> 01:26.700
But what I'd like to do is add a second Tier-1 Gateway.

39
01:26.700 --> 01:28.440
So this one's called Gateway-A.

40
01:28.440 --> 01:30.090
We'll call this one Gateway-B.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
01:28.440 --> 01:30.090
We'll call this one Gateway-B.

41
01:30.090 --> 01:31.650
And then to connect it altogether,

42
01:31.650 --> 01:35.040
let's go ahead and also add a Tier-0 Gateway,

43
01:35.040 --> 01:36.510
and that's this guy right here.

44
01:36.510 --> 01:38.850
we'll call it Tier-0 Gateway-0.

45
01:38.850 --> 01:40.447
And that way whenever we hear zero, we'll know,

46
01:40.447 --> 01:43.260
"Oh, we're talking about this Tier-0 Gateway here."

47
01:43.260 --> 01:46.110
Whether I call it the Tier-0 Gateway or the Gateway-0,

48
01:46.110 --> 01:49.350
we're talking about this guy right here as a Tier-0 Gateway.

49
01:49.350 --> 01:52.230
So, the big picture is once we create this infrastructure,

50
01:52.230 --> 01:54.090
we create the additional gateway here

51
01:54.090 --> 01:55.950
and the other one here, and we link them together,

52
01:55.950 --> 01:58.230
those three virtual routers will live here

53
01:58.230 --> 02:00.360
on this transport node ESXi-A
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
01:58.230 --> 02:00.360
on this transport node ESXi-A

54
02:00.360 --> 02:02.100
and they'll also live in the mind

55
02:02.100 --> 02:04.380
and brains of ESXi-B as well.

56
02:04.380 --> 02:06.000
So, if I drew the little green one here,

57
02:06.000 --> 02:09.270
that'll be our Tier-0 router, our distributed router.

58
02:09.270 --> 02:11.848
And we'd also have our Tier-1 Gateway-A.

59
02:11.848 --> 02:14.551
I'll put a little A there, and A over here as well,

60
02:14.551 --> 02:16.290
'cause it's also got a copy.

61
02:16.290 --> 02:18.240
And also our Tier-1 Gateway-B as well.

62
02:18.240 --> 02:21.330
So as far as the instances of the distributed router,

63
02:21.330 --> 02:23.160
we're gonna have sets of those here

64
02:23.160 --> 02:27.420
for each of these three gateways on ESXi-A and on ESXi-B.

65
02:27.420 --> 02:30.960
And they will also be here on our edge nodes as well,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

65
02:27.420 --> 02:30.960
And they will also be here on our edge nodes as well,

66
02:30.960 --> 02:32.850
including Edge-1 and Edge-2.

67
02:32.850 --> 02:34.050
So, we also draw them up here.

68
02:34.050 --> 02:36.602
So, Edge-1 will have a copy or an instance

69
02:36.602 --> 02:39.780
of the distributed router representing Tier-0.

70
02:39.780 --> 02:40.845
So will Edge-2.

71
02:40.845 --> 02:42.540
Edge-1 will have an instance

72
02:42.540 --> 02:45.870
for this Tier-1 Gateway-A as a distributed router.

73
02:45.870 --> 02:47.490
So, put that here with an A.

74
02:47.490 --> 02:49.530
Also, Edge-2 same thing.

75
02:49.530 --> 02:50.790
And for the Tier-1 Gateway-B,

76
02:50.790 --> 02:52.470
they'll both have a copy of that as well.

77
02:52.470 --> 02:54.780
So, I'll put that here just as reference.

78
02:54.780 --> 02:56.543
And up to this point, I'm being very specific

79
02:56.543 --> 03:00.300
about focusing on just the distributed routing function
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

79
02:56.543 --> 03:00.300
about focusing on just the distributed routing function

80
03:00.300 --> 03:02.500
inside of NSX because in addition

81
03:02.500 --> 03:04.710
to having a distributed router

82
03:04.710 --> 03:07.110
that's running on multiple nodes here,

83
03:07.110 --> 03:09.420
we also, as we add additional functionality

84
03:09.420 --> 03:10.620
for network services,

85
03:10.620 --> 03:13.740
we are also going to be introducing a services router.

86
03:13.740 --> 03:16.860
For example, when we deployed our Tier-1 Gateway-A,

87
03:16.860 --> 03:18.300
if we had said, "Hey, you know what?

88
03:18.300 --> 03:20.310
Instead of just running as a distributed router,

89
03:20.310 --> 03:23.430
let's go ahead and use Active Standby or Active Active."

90
03:23.430 --> 03:25.980
That additional function for fault tolerance

91
03:25.980 --> 03:28.110
and high availability on our edge nodes,

92
03:28.110 --> 03:30.030
they would also then have included
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

92
03:28.110 --> 03:30.030
they would also then have included

93
03:30.030 --> 03:32.550
the services router component as well

94
03:32.550 --> 03:34.230
as we start to add our network services.

95
03:34.230 --> 03:37.560
So, anytime we're implementing network address translation

96
03:37.560 --> 03:42.270
or VPN or connectivity, for example, from a Tier-0 Gateway

97
03:42.270 --> 03:44.850
out to the physical world to the physical network,

98
03:44.850 --> 03:46.800
so I'll put external connectivity.

99
03:46.800 --> 03:49.200
Any of those options are gonna automatically require

100
03:49.200 --> 03:52.950
the addition of a services router on the nodes that need it.

101
03:52.950 --> 03:54.210
So, I wanna give you a heads up

102
03:54.210 --> 03:57.090
that I'm intentionally to this point designing

103
03:57.090 --> 04:00.240
and putting network together with just the DR function
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
03:57.090 --> 04:00.240
and putting network together with just the DR function

104
04:00.240 --> 04:02.580
and not the services router function.

105
04:02.580 --> 04:03.820
And that way we can get comfortable

106
04:03.820 --> 04:05.910
with where that distributed router shows up.

107
04:05.910 --> 04:07.410
And then, as we start to connect

108
04:07.410 --> 04:09.390
to the outside world in a separate skill,

109
04:09.390 --> 04:12.870
we'll automatically see based on our existing infrastructure

110
04:12.870 --> 04:14.220
that we're automatically adding

111
04:14.220 --> 04:15.690
that services router component.

112
04:15.690 --> 04:18.030
Or I should say, NSX is gonna be adding

113
04:18.030 --> 04:20.520
that services router component behind the scenes

114
04:20.520 --> 04:22.260
to the transport nodes that need it.

115
04:22.260 --> 04:24.030
So for our game plan, let's do this.

116
04:24.030 --> 04:26.250
We currently have one Tier-1 Gateway-A

117
04:26.250 --> 04:29.010
that's connected to Segment 10 and Segment 20.

118
04:29.010 --> 04:32.040
But what I'd like to do is I'd like to recreate or modify
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

118
04:29.010 --> 04:32.040
But what I'd like to do is I'd like to recreate or modify

119
04:32.040 --> 04:34.500
our existing topology and make it into this one.

120
04:34.500 --> 04:36.900
So, our first step here would be to create

121
04:36.900 --> 04:38.820
the new Tier-1 Gateway-B,

122
04:38.820 --> 04:41.310
and then connect that to the correct segments.

123
04:41.310 --> 04:42.143
In this case,

124
04:42.143 --> 04:44.310
we wanna connect Tier-1 Gateway-B to Segment 20,

125
04:44.310 --> 04:46.950
which means we'll also go ahead and tell Gateway-A

126
04:46.950 --> 04:48.450
that it's still longer directly connected

127
04:48.450 --> 04:49.680
over here to Segment 20.

128
04:49.680 --> 04:51.510
And that way we can get the topology in place.

129
04:51.510 --> 04:53.520
And then third, let's go ahead and create

130
04:53.520 --> 04:55.650
our Tier-0 Gateway-0.

131
04:55.650 --> 04:57.180
And then once we have that gateway connected,

132
04:57.180 --> 04:59.070
we'll go ahead and we'll link up

133
04:59.070 --> 05:01.753
the Tier-1 Gateway-B to the Gateway-0.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

133
04:59.070 --> 05:01.753
the Tier-1 Gateway-B to the Gateway-0.

134
05:01.753 --> 05:04.920
And also we'll link up the Tier-1 Gateway-A

135
05:04.920 --> 05:07.290
up to the Tier-0 Gateway-0.

136
05:07.290 --> 05:11.040
So effectively, you're gonna link Tier-1 up to Tier-0.

137
05:11.040 --> 05:12.960
And one of the cool things when we link these together

138
05:12.960 --> 05:15.240
is that we don't have to manually come up

139
05:15.240 --> 05:16.680
with an IP addressing scheme

140
05:16.680 --> 05:19.590
for these inter gateway communications.

141
05:19.590 --> 05:21.450
It's automatically gonna use an address base

142
05:21.450 --> 05:25.590
of something in the range of 100.64 something.

143
05:25.590 --> 05:27.060
And it will auto assign those,

144
05:27.060 --> 05:29.280
and it often does that with a /31.

145
05:29.280 --> 05:31.620
So, when we see the automatic subnetting here
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

145
05:29.280 --> 05:31.620
So, when we see the automatic subnetting here

146
05:31.620 --> 05:34.844
and the IP addressing between the Tier-0s and the Tier-1s,

147
05:34.844 --> 05:36.716
just realize that's an automatic function

148
05:36.716 --> 05:38.550
that's happening by default

149
05:38.550 --> 05:40.350
when we link those gateways together.

150
05:40.350 --> 05:41.631
And one other challenge is this.

151
05:41.631 --> 05:44.040
We need to make sure that Tier-0,

152
05:44.040 --> 05:46.290
this Tier-0 Gateway that we're gonna deploy,

153
05:46.290 --> 05:48.030
we wanna make sure it knows about how to reach

154
05:48.030 --> 05:50.070
the 10.10 network down here

155
05:50.070 --> 05:51.690
and the 10.20 network down here.

156
05:51.690 --> 05:53.040
Because even though it's directly connected

157
05:53.040 --> 05:54.930
to each of the Tier-1 routers where it will be

158
05:54.930 --> 05:57.120
once we put that together, it doesn't.

159
05:57.120 --> 05:59.362
Meaning, the Tier-0 Gateway does not by default

160
05:59.362 --> 06:01.200
just automatically learn
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

160
05:59.362 --> 06:01.200
just automatically learn

161
06:01.200 --> 06:03.390
about all the reachable subnets below.

162
06:03.390 --> 06:04.770
So, we're also gonna need to take a moment

163
06:04.770 --> 06:07.620
and click a button on Tier-1 Gateway-A,

164
06:07.620 --> 06:09.150
and also that same button here

165
06:09.150 --> 06:10.417
on Tier-1 Gateway-B that says,

166
06:10.417 --> 06:11.310
"Hey, you know what?

167
06:11.310 --> 06:14.464
Please advertise any directly connected subnets

168
06:14.464 --> 06:17.760
up to your Tier-0 Logical Gateway."

169
06:17.760 --> 06:20.580
And that way, then Tier-0 will know about reachability

170
06:20.580 --> 06:23.040
to the 10.10 address space for Yellow here,

171
06:23.040 --> 06:25.620
and also the IP address space used on the Segment 20,

172
06:25.620 --> 06:29.100
which is our 10.20.0/24 network address space.

173
06:29.100 --> 06:29.933
So, make a note.

174
06:29.933 --> 06:33.030
We'll tell the Tier-1s to advertise
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

174
06:29.933 --> 06:33.030
We'll tell the Tier-1s to advertise

175
06:33.030 --> 06:34.980
their directly connected routes.

176
06:34.980 --> 06:36.450
Then once we do, we'll have full routing

177
06:36.450 --> 06:38.760
inside of our NSX environment here.

178
06:38.760 --> 06:42.180
So, if VM-1 wants to communicate with, for example, VM-2

179
06:42.180 --> 06:43.560
and here's their IP addresses.

180
06:43.560 --> 06:44.910
These do happen to be on the same host.

181
06:44.910 --> 06:47.730
And fortunately, ESXi-A has a copy,

182
06:47.730 --> 06:50.100
an instance, if you will, of the distributed routers.

183
06:50.100 --> 06:50.933
And as a result,

184
06:50.933 --> 06:53.192
it can make all those logical routing decisions internally

185
06:53.192 --> 06:54.660
and forward the traffic.

186
06:54.660 --> 06:58.440
Or if VM-1 is gonna communicate over here with VM-4,

187
06:58.440 --> 07:00.780
once again, ESXi-A having all the information
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

187
06:58.440 --> 07:00.780
once again, ESXi-A having all the information

188
07:00.780 --> 07:02.737
on the gateways will make the routing decision.

189
07:02.737 --> 07:04.920
Then, identify that the layer to address

190
07:04.920 --> 07:08.285
associated with VM-4 is reachable over at ESXi-B

191
07:08.285 --> 07:10.560
at which point it'll go ahead and forward

192
07:10.560 --> 07:12.510
that encapsulated traffic over the tunnel.

193
07:12.510 --> 07:14.880
ESXi-B will de-encapsulate that and then forward it on

194
07:14.880 --> 07:16.080
to the final destination.

195
07:16.080 --> 07:17.970
So, let me clean this up just a little bit

196
07:17.970 --> 07:19.980
and we'll use this as our game plan.

197
07:19.980 --> 07:22.170
So with that in mind, in the very next video,

198
07:22.170 --> 07:24.870
let's turn our attention to our NSX Topology.

199
07:24.870 --> 07:28.522
And let's start by creating this additional Tier-1 Gateway

200
07:28.522 --> 07:31.380
and we'll call it Tier-1 Gateway-B.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

200
07:28.522 --> 07:31.380
and we'll call it Tier-1 Gateway-B.

201
07:31.380 --> 07:34.030
So, we'll see you in the next video for exactly that.