WEBVTT

1
00:00.000 --> 00:03.740
All right, so it's time to tackle step number one in our game plan.

2
00:03.740 --> 00:04.640
And that's right.

3
00:04.640 --> 00:06.800
Here's just to confirm our existing routing.

4
00:06.800 --> 00:08.480
So here's what I would expect to see.

5
00:08.480 --> 00:12.560
We should have default routes on our tier one gateways that they get

6
00:12.560 --> 00:13.580
automatically by

7
00:13.580 --> 00:15.800
being connected to tier zero.

8
00:15.800 --> 00:19.460
Also previously, when we configured the tier one gateways, we specified to

9
00:19.460 --> 00:20.120
include and

10
00:20.120 --> 00:22.360
advertise their respective subnets.

11
00:22.360 --> 00:26.580
So the 1010 network and the 1020 networks respectively should already be in the

12
00:26.580 --> 00:27.040
routing

13
00:27.040 --> 00:30.690
table on our tier zero gateway because the tier one gateways are advertising
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:27.040 --> 00:30.690
table on our tier zero gateway because the tier one gateways are advertising

14
00:30.690 --> 00:31.480
that information

15
00:31.480 --> 00:32.480
up there.

16
00:32.480 --> 00:35.730
So probably the easiest way of verifying all of our routing is to go to one of

17
00:35.730 --> 00:36.160
our edge

18
00:36.160 --> 00:39.000
nodes and we'll verify which one is the active edge node.

19
00:39.000 --> 00:41.020
I believe it's edge one will confirm that.

20
00:41.020 --> 00:45.100
And we can take a look at the routing table for tier zero at the edge, which

21
00:45.100 --> 00:45.640
because of

22
00:45.640 --> 00:49.480
the connectivity to the external network here is the edge transport nodes that

23
00:49.480 --> 00:50.000
are providing

24
00:50.000 --> 00:51.280
that functionality.

25
00:51.280 --> 00:53.840
So there's a few different ways we could look at the routing table one is right

26
00:53.840 --> 00:54.040
here

27
00:54.040 --> 00:58.560
from the NSX manager, we could click on networking and with networking selected

28
00:58.560 --> 00:59.000
, we could look

29
00:59.000 --> 01:02.990
at our topology by clicking on the left here on network topology and then we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

29
00:59.000 --> 01:02.990
at our topology by clicking on the left here on network topology and then we

30
01:02.990 --> 01:03.640
could make

31
01:03.640 --> 01:04.640
that a little bit bigger.

32
01:04.640 --> 01:07.400
And then we wanted to we could go ahead and first of all, let's double click on

33
01:07.400 --> 01:07.560
this

34
01:07.560 --> 01:11.960
tier zero gateway zero just to verify who is supporting the services of that.

35
01:11.960 --> 01:16.290
So here showing us that edge one is the active edge node and edge two is the

36
01:16.290 --> 01:17.080
standby.

37
01:17.080 --> 01:21.300
That's the two edge nodes that are providing the services for this tier zero

38
01:21.300 --> 01:22.040
gateway.

39
01:22.040 --> 01:25.160
And if we click again here on the gateway, it'll bring a panel over on the

40
01:25.160 --> 01:25.760
right with

41
01:25.760 --> 01:28.040
information about the tier zero gateway.

42
01:28.040 --> 01:30.830
And from here, if we wanted to, we could go ahead and download the routing
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
01:28.040 --> 01:30.830
And from here, if we wanted to, we could go ahead and download the routing

43
01:30.830 --> 01:31.360
table right

44
01:31.360 --> 01:32.360
here.

45
01:32.360 --> 01:34.400
So I'm going to go ahead and click on download routing table.

46
01:34.400 --> 01:37.510
And that's going to download that to my downloads folder on my local management

47
01:37.510 --> 01:38.320
computer.

48
01:38.320 --> 01:39.800
And let's take a look at it together.

49
01:39.800 --> 01:43.600
So I downloaded as a CSV file and then I happen to have Microsoft Excel on my

50
01:43.600 --> 01:44.320
local management

51
01:44.320 --> 01:45.320
computer.

52
01:45.320 --> 01:47.520
So when I double clicked on it, it opened it with that by default.

53
01:47.520 --> 01:48.520
So here's the route type.

54
01:48.520 --> 01:51.320
So those we have T zero and T one.

55
01:51.320 --> 01:53.160
We'll take a look at those here closer in a moment.

56
01:53.160 --> 01:57.480
And then we also have the C versus an S regarding the type of route.

57
01:57.480 --> 02:00.910
So let's go ahead and start with this IPV four route right here is the route
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
01:57.480 --> 02:00.910
So let's go ahead and start with this IPV four route right here is the route

58
02:00.910 --> 02:01.920
for the 10 10

59
02:01.920 --> 02:02.920
zero network.

60
02:02.920 --> 02:04.840
There's the next top IP address.

61
02:04.840 --> 02:07.200
It is a tier one connected route.

62
02:07.200 --> 02:08.960
That's what the T one C is.

63
02:08.960 --> 02:12.640
And then we have a similar route here for 10 20 zero network.

64
02:12.640 --> 02:14.080
It's a T one connected route.

65
02:14.080 --> 02:15.920
And that one's off of gateway B.

66
02:15.920 --> 02:17.120
And there's the next top.

67
02:17.120 --> 02:18.920
Then we have some directly connected networks.

68
02:18.920 --> 02:22.350
These are the connections between gateway zero and gateway A and be

69
02:22.350 --> 02:23.360
respectively.

70
02:23.360 --> 02:24.360
So there's one of them.

71
02:24.360 --> 02:25.360
There's the other one.

72
02:25.360 --> 02:27.440
Then we have a route for the back plane.

73
02:27.440 --> 02:31.740
So when the tier zero gateway is communicating internally between the DR and SR
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

73
02:27.440 --> 02:31.740
So when the tier zero gateway is communicating internally between the DR and SR

74
02:31.740 --> 02:32.560
functions.

75
02:32.560 --> 02:36.410
And in this context, that DR is the distributed router and the SR as a services

76
02:36.410 --> 02:37.000
router.

77
02:37.000 --> 02:38.520
It's going to use that subnet.

78
02:38.520 --> 02:42.840
And then we also have a default route that we applied in an earlier skill.

79
02:42.840 --> 02:45.920
And here is T zero S the S stands for a static route.

80
02:45.920 --> 02:48.920
And that's the static route saying, hey, to get to anywhere that you don't have

81
02:48.920 --> 02:49.280
a more

82
02:49.280 --> 02:53.360
specific route for your next top is 192 168 1.1.

83
02:53.360 --> 02:57.530
Now another way of seeing the routing table for our tier zero gateway is at the

84
02:57.530 --> 02:58.000
command

85
02:58.000 --> 02:59.000
line.

86
02:59.000 --> 03:00.240
And that can be very useful as well.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

86
02:59.000 --> 03:00.240
And that can be very useful as well.

87
03:00.240 --> 03:01.720
So they minimize that.

88
03:01.720 --> 03:04.220
So let's open up a command line interface on the management network and let's

89
03:04.220 --> 03:04.560
connect

90
03:04.560 --> 03:07.680
over to edge one with an SSH session.

91
03:07.680 --> 03:09.600
So here we're connected to edge one.

92
03:09.600 --> 03:13.120
And from here, if we do a get gateways, it'll give us a list of the gateways.

93
03:13.120 --> 03:18.250
So as we discussed in a previous skill, the VRF zero that gateway is like the

94
03:18.250 --> 03:19.080
transport

95
03:19.080 --> 03:23.080
network routing table for the VM itself, in this case edge one.

96
03:23.080 --> 03:26.770
And then for the services router, which is right here based on the label here,

97
03:26.770 --> 03:27.280
services

98
03:27.280 --> 03:31.160
router tier zero, an easy way of working with it and using commands just for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

98
03:27.280 --> 03:31.160
router tier zero, an easy way of working with it and using commands just for

99
03:31.160 --> 03:32.440
that one virtual

100
03:32.440 --> 03:35.560
router is to go ahead and simply go into the VRF.

101
03:35.560 --> 03:37.880
So currently this is VRF four.

102
03:37.880 --> 03:41.360
So we type in VRF space for and press enter.

103
03:41.360 --> 03:45.240
This is the prompt change to tell us that we're now in VRF number four here.

104
03:45.240 --> 03:48.120
And now if we do a question mark, it'll show us the commands of can issues.

105
03:48.120 --> 03:50.680
So we do a get space and then a question mark.

106
03:50.680 --> 03:53.440
And let's go ahead and do a get route, see the IP routing table.

107
03:53.440 --> 03:57.050
So we'll type get route press enter and the output here reflects what we also

108
03:57.050 --> 03:57.520
saw in the

109
03:57.520 --> 03:58.520
spreadsheet.

110
03:58.520 --> 04:01.920
So here is our static default route with the next top of 192, once you see
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

110
03:58.520 --> 04:01.920
So here is our static default route with the next top of 192, once you see

111
04:01.920 --> 04:02.440
eight one

112
04:02.440 --> 04:03.440
dot one.

113
04:03.440 --> 04:07.260
And then we have two tier one connected routes that are connected to gateway

114
04:07.260 --> 04:08.920
and be respectively.

115
04:08.920 --> 04:12.400
And for this edge router to go ahead and reach those, there's the respective

116
04:12.400 --> 04:13.280
next hops on

117
04:13.280 --> 04:14.280
gateway and be.

118
04:14.280 --> 04:17.710
And then we have the two networks associated with the router to router links

119
04:17.710 --> 04:18.480
between tier

120
04:18.480 --> 04:21.440
zero and gateway and gateway B.

121
04:21.440 --> 04:25.980
And then we have a T zero directly connected network of 169 to 2,400, which is

122
04:25.980 --> 04:26.440
showing

123
04:26.440 --> 04:28.200
right here is the back plane connection.

124
04:28.200 --> 04:32.010
So think of it like logically, if the DR function on the tier zero gateway
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

124
04:28.200 --> 04:32.010
So think of it like logically, if the DR function on the tier zero gateway

125
04:32.010 --> 04:33.160
needed to communicate

126
04:33.160 --> 04:38.080
with the SR function on the T zero gateway, it would do so on the back plane.

127
04:38.080 --> 04:41.250
And then here we have our connection to the 192, 160 one network, which we have

128
04:41.250 --> 04:41.800
connectivity

129
04:41.800 --> 04:47.060
through courtesy of our edge nodes using dot 61 on edge one and dot 62 using

130
04:47.060 --> 04:47.920
edge two.

131
04:47.920 --> 04:50.400
And then we also have a virtual IP address of dot 60.

132
04:50.400 --> 04:53.520
And then following that we have some IPV six routing information as well.

133
04:53.520 --> 04:58.080
So since we're sitting right here also inside the VRF, let's also do a ping out

134
04:58.080 --> 05:00.960
to 192.168.1.1.1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

134
04:58.080 --> 05:00.960
to 192.168.1.1.1.

135
05:00.960 --> 05:02.800
And if that works, that would be great.

136
05:02.800 --> 05:08.460
It does and that is our connectivity from our tier zero gateway to the physical

137
05:08.460 --> 05:09.120
gateway

138
05:09.120 --> 05:10.120
over a dot one.

139
05:10.120 --> 05:12.720
And it's what it confirmed that we have that connectivity.

140
05:12.720 --> 05:16.520
Also I would mind confirming just some basic connectivity with our VMs.

141
05:16.520 --> 05:20.440
So let's go to our VM right here, which is VM one.

142
05:20.440 --> 05:21.440
This is verified.

143
05:21.440 --> 05:23.520
We can ping our other three VMs.

144
05:23.520 --> 05:24.960
They'll confirm our East West traffic.

145
05:24.960 --> 05:30.300
And let's also confirm that we can ping from VM one to the logical VIP address
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

145
05:24.960 --> 05:30.300
And let's also confirm that we can ping from VM one to the logical VIP address

146
05:30.300 --> 05:30.880
that we're

147
05:30.880 --> 05:33.000
using up here on Gateway zero.

148
05:33.000 --> 05:38.330
So we're going to avoid pinging the 192.168.1.1 because that router, that

149
05:38.330 --> 05:39.000
device at this

150
05:39.000 --> 05:44.590
moment has no idea about how to reach back or route back to the 10 10 or 10 20

151
05:44.590 --> 05:45.440
network.

152
05:45.440 --> 05:48.760
So let me bring a little remote console for this VM right here, VM one.

153
05:48.760 --> 05:52.320
Let me also confirm it's IP address with an IF config.

154
05:52.320 --> 05:54.760
And sure enough, it is 10 10 zero 10.

155
05:54.760 --> 05:58.670
And let's also issue the command route just to confirm it has a default gateway

156
05:58.670 --> 05:59.160
that points

157
05:59.160 --> 06:03.920
to Gateway A's address of 10.10.0.1 as a default gateway.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

157
05:59.160 --> 06:03.920
to Gateway A's address of 10.10.0.1 as a default gateway.

158
06:03.920 --> 06:05.040
So let's do a quick ping.

159
06:05.040 --> 06:10.400
Let's do a ping over to VM three at 10.10.0.11.

160
06:10.400 --> 06:11.400
That looks good.

161
06:11.400 --> 06:12.400
We'll do a control C to break that.

162
06:12.400 --> 06:17.000
Then we'll do a ping to 10.20.0.20 verify that works.

163
06:17.000 --> 06:20.160
And then our last one is at 10.20.0.21.

164
06:20.160 --> 06:21.920
So we'll go ahead and do that as well.

165
06:21.920 --> 06:23.640
Just to verify we have East West connectivity.

166
06:23.640 --> 06:30.640
And that looks good.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

166
06:23.640 --> 06:30.640
And that looks good.

167
06:30.640 --> 06:30.740
Let's also go ahead and do a ping to the virtual IP address up here at our tier

168
06:30.740 --> 06:30.880
zero gateway.

169
06:30.880 --> 06:35.530
We could also try a ping up to dot 61 and dot 62 because this gateway who owns

170
06:35.530 --> 06:36.000
those

171
06:36.000 --> 06:39.880
addresses knows how to route back to the 10 10 network.

172
06:39.880 --> 06:44.080
So let's ping those IP addresses next once again from our VM number one.

173
06:44.080 --> 06:51.560
So we'll bring back VM number one here and let's do a ping to 192.168.1.60.

174
06:51.560 --> 06:55.840
Just a virtual address here on this gateway on the 192.168.1 segment.

175
06:55.840 --> 06:56.840
Fantastic.

176
06:56.840 --> 06:57.840
That works.

177
06:57.840 --> 07:01.090
And let's also go ahead and do a ping of 61, which is the edge one interface
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

177
06:57.840 --> 07:01.090
And let's also go ahead and do a ping of 61, which is the edge one interface

178
07:01.090 --> 07:01.720
address.

179
07:01.720 --> 07:05.650
And we'll also go ahead and do it to dot 62, which is the IP address for edge

180
07:05.650 --> 07:06.000
two.

181
07:06.000 --> 07:09.160
And I just realized that we don't have active active setup.

182
07:09.160 --> 07:10.920
We just have active standby.

183
07:10.920 --> 07:13.800
So that ping to dot 62 is not working.

184
07:13.800 --> 07:17.730
And here's why if we double click on the tier zero gateway, take a look at the

185
07:17.730 --> 07:18.440
fabric.

186
07:18.440 --> 07:20.440
Edge two is in standby.

187
07:20.440 --> 07:21.720
So at the moment it's not being used.

188
07:21.720 --> 07:25.200
It's very likely that's why it didn't respond to the ping when we tried to ping

189
07:25.200 --> 07:26.600
dot 62.

190
07:26.600 --> 07:30.170
Also while we're here in the NSX manager, let's go to the T zero gateway and I
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

190
07:26.600 --> 07:30.170
Also while we're here in the NSX manager, let's go to the T zero gateway and I

191
07:30.170 --> 07:30.680
want to

192
07:30.680 --> 07:32.960
just modify just a little bit.

193
07:32.960 --> 07:34.200
It's default route.

194
07:34.200 --> 07:37.740
So if we click on the three dots to edit our tier zero gateway and from the

195
07:37.740 --> 07:38.320
menu, we

196
07:38.320 --> 07:39.320
click on edit.

197
07:39.320 --> 07:43.610
Then if he's scroll down a little bit down under routing, if we expand that

198
07:43.610 --> 07:43.960
here, we

199
07:43.960 --> 07:45.320
have one static route.

200
07:45.320 --> 07:46.320
So there's a one there.

201
07:46.320 --> 07:47.560
We'll go ahead and click on that.

202
07:47.560 --> 07:51.160
So there's our static default route and I want to go ahead and edit that as

203
07:51.160 --> 07:51.680
well.

204
07:51.680 --> 07:55.690
And what I want to do is for the next hop, I want to leave it at 192.168.1.1,

205
07:55.690 --> 07:56.080
but I want

206
07:56.080 --> 07:58.400
to change the administrative distance.

207
07:58.400 --> 08:00.600
So I'm going to change that to 150.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

207
07:58.400 --> 08:00.600
So I'm going to change that to 150.

208
08:00.600 --> 08:02.800
And let's talk about why I'm going to modify that.

209
08:02.800 --> 08:06.870
Let's imagine that we have gateway zero and let's imagine we've trained gateway

210
08:06.870 --> 08:07.440
zero about

211
08:07.440 --> 08:10.000
how to reach the 10 dot 90 network.

212
08:10.000 --> 08:11.880
So that's the networking question.

213
08:11.880 --> 08:15.320
And this gateway, let's imagine it's learning it via a static route.

214
08:15.320 --> 08:18.160
And let's also imagine it's learning it via OSPF.

215
08:18.160 --> 08:21.230
Well if this gateway is being trained or learning about the same exact route,

216
08:21.230 --> 08:21.720
the 10

217
08:21.720 --> 08:25.630
90 zero network in this case, and it's learning it from two different sources,

218
08:25.630 --> 08:26.400
which one should

219
08:26.400 --> 08:27.400
it believe?

220
08:27.400 --> 08:29.920
Which one should you use this one or this one?

221
08:29.920 --> 08:33.460
And the answer as far as how is going to decide which one to use, which source
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

221
08:29.920 --> 08:33.460
And the answer as far as how is going to decide which one to use, which source

222
08:33.460 --> 08:33.800
it's

223
08:33.800 --> 08:37.920
going to use is based on the administrative distance, which is a lot like golf.

224
08:37.920 --> 08:41.440
So if you think about golf, even if you're not a golf expert, which I am not, I

225
08:41.440 --> 08:41.880
do know

226
08:41.880 --> 08:45.400
that the person with the lowest score wins.

227
08:45.400 --> 08:49.300
And so if we have a static route, for example, as we do right here with this

228
08:49.300 --> 08:50.160
number, this

229
08:50.160 --> 08:55.340
administrative distance of 150 and then OSPF as it's advertising that same

230
08:55.340 --> 08:56.200
route into this

231
08:56.200 --> 09:00.280
gateway, if it has an administrative distance is lower, like 110, that will
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

231
08:56.200 --> 09:00.280
gateway, if it has an administrative distance is lower, like 110, that will

232
09:00.280 --> 09:01.240
cause this gateway

233
09:01.240 --> 09:03.280
to say, you know what, it's the same exact route.

234
09:03.280 --> 09:05.160
I'm learning it from two different sources.

235
09:05.160 --> 09:08.990
I'm going to go ahead and choose the one with the lowest administrative

236
09:08.990 --> 09:09.800
distance.

237
09:09.800 --> 09:10.880
And that's what this is right here.

238
09:10.880 --> 09:15.530
So the reason I'm changing this is because in a little bit, as we start config

239
09:15.530 --> 09:16.320
uring OSPF

240
09:16.320 --> 09:20.160
and advertising a default route down to this gateway, I want to see this route,

241
09:20.160 --> 09:20.680
which has

242
09:20.680 --> 09:25.390
an administrative distance of 150, be replaced by the better and lower

243
09:25.390 --> 09:27.040
administrative distance

244
09:27.040 --> 09:28.920
being advertised by OSPF.

245
09:28.920 --> 09:31.160
And that's why I want to go ahead and modify that right now.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

245
09:28.920 --> 09:31.160
And that's why I want to go ahead and modify that right now.

246
09:31.160 --> 09:36.300
So we'll go ahead and click on apply and save and then close and scroll down

247
09:36.300 --> 09:37.040
and click

248
09:37.040 --> 09:41.710
on close editing and then collapse that and I just want to confirm that it took

249
09:41.710 --> 09:42.040
.

250
09:42.040 --> 09:46.370
So one way of doing that is right here at the command line interface for edge

251
09:46.370 --> 09:46.840
one and

252
09:46.840 --> 09:50.880
I'm currently in the VRF4, which is effectively the services router for the

253
09:50.880 --> 09:52.160
tier zero gateway.

254
09:52.160 --> 09:54.830
And then I'm going to hit the upper okay a few times and we'll do that get

255
09:54.830 --> 09:55.320
route one

256
09:55.320 --> 09:56.320
more time.

257
09:56.320 --> 09:57.720
So previously we had a static route.

258
09:57.720 --> 10:02.720
So the S is right there and there is the default route and it had an AD of one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

258
09:57.720 --> 10:02.720
So the S is right there and there is the default route and it had an AD of one.

259
10:02.720 --> 10:04.200
That's what this value is right here.

260
10:04.200 --> 10:08.460
But now that we modified that AD to 150, so now if we scroll down, we still

261
10:08.460 --> 10:09.320
have our static

262
10:09.320 --> 10:13.160
route is still a static default route and now we have an AD of 150.

263
10:13.160 --> 10:17.640
So if and when I might add, we advertise a default route from a physical route

264
10:17.640 --> 10:18.200
running

265
10:18.200 --> 10:23.440
OSPF with an AD by default of 110, we should automatically have this static

266
10:23.440 --> 10:24.440
route replaced

267
10:24.440 --> 10:28.600
in our routing table and instead have this default route learned via OSPF.

268
10:28.600 --> 10:30.760
All right, so let's check our work so far.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

268
10:28.600 --> 10:30.760
All right, so let's check our work so far.

269
10:30.760 --> 10:34.580
So now that we have confirmed our existing routing in our infrastructure and we

270
10:34.580 --> 10:35.120
've also

271
10:35.120 --> 10:40.360
confirmed our connectivity up here to dot one from the VRF for our tier zero

272
10:40.360 --> 10:41.160
gateway,

273
10:41.160 --> 10:45.250
our next step is to go ahead and begin our configuration of OSPF right here on

274
10:45.250 --> 10:45.480
this

275
10:45.480 --> 10:50.080
tier zero gateway in preparation for sharing routing information back and forth

276
10:50.080 --> 10:50.480
with this

277
10:50.480 --> 10:51.640
external router.

278
10:51.640 --> 10:54.760
So I look forward to seeing you in the next video as we take that next logical

279
10:54.760 --> 10:55.040
step.

280
10:55.040 --> 10:57.280
(clicking)