WEBVTT

1
00:00.210 --> 00:02.310
So currently we have our gateway A

2
00:02.310 --> 00:04.560
and gateway B with a couple of VMs

3
00:04.560 --> 00:06.660
connected to each of those segments they're supporting.

4
00:06.660 --> 00:09.450
And right now, clients over here on Segment 10

5
00:09.450 --> 00:12.180
cannot communicate with devices over here on Segment 20

6
00:12.180 --> 00:14.520
because we have no connection between

7
00:14.520 --> 00:15.720
gateway A and gateway B.

8
00:15.720 --> 00:18.270
So to solve that, we're gonna add our third router,

9
00:18.270 --> 00:19.770
our third gateway right here.

10
00:19.770 --> 00:21.510
There'll be a tier zero gateway

11
00:21.510 --> 00:24.960
that we can link to both gateway A and gateway B.

12
00:24.960 --> 00:25.980
And based on our plan

13
00:25.980 --> 00:28.039
it's gonna be this, the green router right here.

14
00:28.039 --> 00:30.298
So we'll name it our tier zero gateway zero,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

14
00:28.039 --> 00:30.298
So we'll name it our tier zero gateway zero,

15
00:30.298 --> 00:32.760
and then we'll go ahead and connect it

16
00:32.760 --> 00:36.060
to both the tier one gateway A and tier one gateway B.

17
00:36.060 --> 00:38.003
And when we do that, it'll automagically

18
00:38.003 --> 00:40.757
use this address space of 10.64, something

19
00:40.757 --> 00:44.031
to go ahead and create an auto assigned IP addresses

20
00:44.031 --> 00:46.830
for the communication between tier zero

21
00:46.830 --> 00:49.020
and these two tier one gateways.

22
00:49.020 --> 00:50.730
So let's go to the N-S-X-C-L-I

23
00:50.730 --> 00:54.210
and let's create our brand new tier zero, gateway zero.

24
00:54.210 --> 00:56.310
So here with the networking tab selected,

25
00:56.310 --> 00:58.320
we'll leave our network topology view

26
00:58.320 --> 01:01.530
and click here on tier zero gateways.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
00:58.320 --> 01:01.530
and click here on tier zero gateways.

27
01:01.530 --> 01:02.940
So at the moment, we don't have any

28
01:02.940 --> 01:04.800
but it's super easy to create one,

29
01:04.800 --> 01:06.840
we'll simply click here on add gateway,

30
01:06.840 --> 01:08.880
then we'll specify the type of gateway we're creating

31
01:08.880 --> 01:10.590
a tier zero, select that,

32
01:10.590 --> 01:11.580
and then we'll give it a name.

33
01:11.580 --> 01:15.963
So let's call it, our tier zero, space gateway, dash zero.

34
01:17.316 --> 01:18.300
And the benefit of adding the "our" in front of it

35
01:18.300 --> 01:20.040
is just that every time you see these gateways,

36
01:20.040 --> 01:22.110
these logical gateways, you're gonna know

37
01:22.110 --> 01:23.536
these are the gateways that we created

38
01:23.536 --> 01:26.100
because we put an "our" in front of it.

39
01:26.100 --> 01:28.110
So when we setup our tier zero gateway,

40
01:28.110 --> 01:30.240
we have a choice of choosing active, active
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
01:28.110 --> 01:30.240
we have a choice of choosing active, active

41
01:30.240 --> 01:32.520
for fault tolerance or active standby.

42
01:32.520 --> 01:34.410
And when we specify either active, active

43
01:34.410 --> 01:37.770
or active standby, it's also going to require us to specify,

44
01:37.770 --> 01:41.010
hey, for that fault tolerant feature and high availability,

45
01:41.010 --> 01:43.350
which edge nodes do you wanna use?

46
01:43.350 --> 01:45.630
And so we have our two edge nodes in a cluster

47
01:45.630 --> 01:49.350
called "Our Edge Cluster" that can provide those services.

48
01:49.350 --> 01:51.420
And that's all we need to specify right here.

49
01:51.420 --> 01:54.180
So we've now created our tier zero, gateway zero.

50
01:54.180 --> 01:56.580
So if we scroll down, we'll click on save.

51
01:56.580 --> 01:57.720
And now that it's created,

52
01:57.720 --> 01:59.377
it's giving us a further option to click on,

53
01:59.377 --> 02:01.100
"Yes", we wanna do further configuration like,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
01:59.377 --> 02:01.100
"Yes", we wanna do further configuration like,

54
02:01.100 --> 02:03.960
specify additional details, for example,

55
02:03.960 --> 02:06.810
routing information or specifying interface and so forth.

56
02:06.810 --> 02:08.400
So for now, I gonna click on "No."

57
02:08.400 --> 02:10.256
So we have our tier zero gateway zero.

58
02:10.256 --> 02:12.330
It's not currently connected

59
02:12.330 --> 02:14.040
to any tier one gateways at the moment.

60
02:14.040 --> 02:15.840
And we also don't have any link segments.

61
02:15.840 --> 02:18.150
So effectively we've got this router

62
02:18.150 --> 02:20.070
gateway zero that's sitting up there in space.

63
02:20.070 --> 02:21.480
We can verify that by going back

64
02:21.480 --> 02:23.190
to the network topology tab here.

65
02:23.190 --> 02:24.600
And there it is, right there.

66
02:24.600 --> 02:26.320
So tier zero, gateway zero,

67
02:26.320 --> 02:30.150
it has a gateway firewall rule in place as a service.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
02:26.320 --> 02:30.150
it has a gateway firewall rule in place as a service.

68
02:30.150 --> 02:32.460
However, we have no connectivity whatsoever yet

69
02:32.460 --> 02:34.680
to gateway A or gateway B,

70
02:34.680 --> 02:36.810
which are our tier one gateways.

71
02:36.810 --> 02:38.970
So what we wanna do is link them together

72
02:38.970 --> 02:40.650
so that linking together would look like this.

73
02:40.650 --> 02:42.750
We wanna go ahead and do a connection here

74
02:42.750 --> 02:44.520
and a connection here.

75
02:44.520 --> 02:45.900
And as I mentioned, once we do that,

76
02:45.900 --> 02:49.330
it'll automatically be using the address base of 100.64

77
02:49.330 --> 02:52.950
and then some extension to that for those segments.

78
02:52.950 --> 02:55.050
So we'll have a logical IP subnet here,

79
02:55.050 --> 02:56.910
another logical IP subnet here

80
02:56.910 --> 03:00.330
between our tier zero gateway and our tier one gateways.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
02:56.910 --> 03:00.330
between our tier zero gateway and our tier one gateways.

81
03:00.330 --> 03:02.520
So let's go ahead and associate or link

82
03:02.520 --> 03:04.594
the tier zero gateway of gateway zero

83
03:04.594 --> 03:06.780
to both these tier one gateways.

84
03:06.780 --> 03:07.800
Now one question might be,

85
03:07.800 --> 03:08.840
well, how do we go about doing that?

86
03:08.840 --> 03:10.380
Do we go to the gateway zero

87
03:10.380 --> 03:12.630
and tell it, we're linking it to gateway A and gateway B?

88
03:12.630 --> 03:14.610
Or do we go to the, gateway A and B

89
03:14.610 --> 03:16.680
and tell it that we're linking up to gateway zero?

90
03:16.680 --> 03:19.530
And the way we do this is from the tier one gateways.

91
03:19.530 --> 03:21.990
So we go to the properties of each of our tier one gateways

92
03:21.990 --> 03:24.119
and say, "Hey, we want you to have as a connection,

93
03:24.119 --> 03:26.160
a link to the tier zero."

94
03:26.160 --> 03:27.840
So with networking on the top selected

95
03:27.840 --> 03:28.920
and under connectivity,

96
03:28.920 --> 03:30.390
we're gonna click on tier one gateways.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
03:28.920 --> 03:30.390
we're gonna click on tier one gateways.

97
03:30.390 --> 03:33.810
And currently here where it shows linked tier zero gateways,

98
03:33.810 --> 03:34.950
not set, not set.

99
03:34.950 --> 03:37.917
However, now that we do have a tier zero gateway to link to,

100
03:37.917 --> 03:41.190
we can simply modify the properties of our tier one gateways

101
03:41.190 --> 03:42.810
and tell them we wanna automatically link up

102
03:42.810 --> 03:44.100
to our tier zero gateway.

103
03:44.100 --> 03:45.690
So we'll start with gateway A first,

104
03:45.690 --> 03:46.920
we'll click on the three dots,

105
03:46.920 --> 03:49.320
and then from the menu, click on edit.

106
03:49.320 --> 03:52.230
And then here where it says linked tier zero gateway,

107
03:52.230 --> 03:53.220
we'll use the dropdown.

108
03:53.220 --> 03:55.320
And because we now have a tier zero gateway,

109
03:55.320 --> 03:56.880
we'll simply select it and boom,

110
03:56.880 --> 03:59.790
now we have our connectivity from tier zero to tier one.

111
03:59.790 --> 04:02.430
So if we scroll down, click on close editing.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
03:59.790 --> 04:02.430
So if we scroll down, click on close editing.

112
04:02.430 --> 04:04.110
Then if we collapse this.

113
04:04.110 --> 04:05.088
Notice now under linked tier zero gateway,

114
04:05.088 --> 04:07.860
It's now showing us the tier zero gateway

115
04:07.860 --> 04:09.000
that we are linked to.

116
04:09.000 --> 04:11.580
And if we click on network topology, once again,

117
04:11.580 --> 04:13.140
it should reflect that as well.

118
04:13.140 --> 04:14.610
So here's our connectivity.

119
04:14.610 --> 04:16.080
Let me make that full screen

120
04:16.080 --> 04:17.430
and make that a little bit bigger.

121
04:17.430 --> 04:19.200
There we go. So there's our connectivity

122
04:19.200 --> 04:23.070
from our tier zero gateway zero over to gateway A.

123
04:23.070 --> 04:24.990
And also what is interesting to note is

124
04:24.990 --> 04:26.640
that it's using a slash 31.

125
04:26.640 --> 04:30.360
So I teach a lot of the fundamentals of IP addressing
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

125
04:26.640 --> 04:30.360
So I teach a lot of the fundamentals of IP addressing

126
04:30.360 --> 04:32.370
and subnetting and so forth, and I love it.

127
04:32.370 --> 04:34.770
But at the entry level, we tell people, you know what,

128
04:34.770 --> 04:36.570
you can't have any host addresses

129
04:36.570 --> 04:37.449
that are all ones or all zeros.

130
04:37.449 --> 04:39.540
And so really when you use the slash 30,

131
04:39.540 --> 04:41.040
and then within that you're gonna have, for example,

132
04:41.040 --> 04:45.060
in the first subnet, usable addresses of one and two.

133
04:45.060 --> 04:46.860
And that'd be for example, zero in the last octet.

134
04:46.860 --> 04:49.860
And then if you had, for example, a subnet ending in four

135
04:49.860 --> 04:51.840
with a slash 30, the valid addresses on

136
04:51.840 --> 04:55.170
that subnet subnet four would be dot five and dot six.

137
04:55.170 --> 04:56.640
And then on the next subnet eight,

138
04:56.640 --> 05:00.090
the valid addresses on a slash 30 would be nine and 10.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

138
04:56.640 --> 05:00.090
the valid addresses on a slash 30 would be nine and 10.

139
05:00.090 --> 05:02.400
And if you want more detail and training on subnetting

140
05:02.400 --> 05:03.840
and variable link subnetting,

141
05:03.840 --> 05:07.020
you can check out our CCNA course here at CBT Nuggets.

142
05:07.020 --> 05:09.390
That course has some really rated sections, plural,

143
05:09.390 --> 05:12.540
on IP subnetting including variable length subnet masking,

144
05:12.540 --> 05:14.490
and also our CompTIA Network+

145
05:14.490 --> 05:16.205
has information there as well

146
05:16.205 --> 05:18.690
regarding how to do and implement IP subnetting.

147
05:18.690 --> 05:21.603
So again, generally we're not gonna go past a slash 30

148
05:21.603 --> 05:23.520
as we teach the entry level stuff.

149
05:23.520 --> 05:26.580
However, there are some exceptions based on the vendor.

150
05:26.580 --> 05:29.524
And here's one of them, where we're using a slash 31.

151
05:29.524 --> 05:32.940
And then we can actually literally have this address,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

151
05:29.524 --> 05:32.940
And then we can actually literally have this address,

152
05:32.940 --> 05:35.989
100.64.0.0 on one end of that connection

153
05:35.989 --> 05:40.650
and the address of 100.64.0.1 at the other end

154
05:40.650 --> 05:42.060
using a slash 31.

155
05:42.060 --> 05:43.745
So that's what it's done right here for us.

156
05:43.745 --> 05:45.810
And if we wanna control that address base

157
05:45.810 --> 05:47.880
and not use that specific range,

158
05:47.880 --> 05:50.010
we can do so by going to the properties here

159
05:50.010 --> 05:51.810
of our tier zero gateway

160
05:51.810 --> 05:54.600
and simply telling it what addressing space we wanna use.

161
05:54.600 --> 05:56.760
So I'm gonna go ahead and take this out of full screen

162
05:56.760 --> 05:58.050
and let's go back to the tier zero

163
05:58.050 --> 05:59.430
gateway just for a moment.

164
05:59.430 --> 06:01.680
And if we look at the details here, in fact, I'll go ahead
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

164
05:59.430 --> 06:01.680
And if we look at the details here, in fact, I'll go ahead

165
06:01.680 --> 06:03.900
and click on the three dots to edit it.

166
06:03.900 --> 06:05.310
From the menu, select edit.

167
06:05.310 --> 06:07.080
And then here on additional settings

168
06:07.080 --> 06:08.670
for our tier zero gateway,

169
06:08.670 --> 06:10.110
here's where we can specify

170
06:10.110 --> 06:11.340
the addressing that we wanna use.

171
06:11.340 --> 06:12.570
So right here where it specifies the

172
06:12.570 --> 06:15.270
T-zero to T-one transit, it's automatically using

173
06:15.270 --> 06:16.890
that 164 address space.

174
06:16.890 --> 06:18.720
And so we could go ahead and choose

175
06:18.720 --> 06:21.330
to put in a different range there if we wanted to.

176
06:21.330 --> 06:23.190
However, for now we can take that default.

177
06:23.190 --> 06:24.930
I just want you to be aware of where

178
06:24.930 --> 06:26.820
that IP addressing space is coming from

179
06:26.820 --> 06:29.160
and it is a default that's in place.

180
06:29.160 --> 06:30.499
All right, so back to network topology,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

180
06:29.160 --> 06:30.499
All right, so back to network topology,

181
06:30.499 --> 06:31.332
I'm gonna click on, "Yes",

182
06:31.332 --> 06:33.120
I don't wanna change anything there on the T-zero.

183
06:33.120 --> 06:35.880
So next, let's add another link between gateway B

184
06:35.880 --> 06:38.850
and the gateway zero, the T-zero gateway, zero router.

185
06:38.850 --> 06:40.620
And when we do that, it's very likely to go ahead

186
06:40.620 --> 06:41.970
and use the next two IP addresses,

187
06:41.970 --> 06:45.120
which would be 100.64.0.2

188
06:45.120 --> 06:47.670
and three respectively with a slash 31.

189
06:47.670 --> 06:50.280
Again, that's being done automatically by the system.

190
06:50.280 --> 06:52.039
So let's go to our tier one gateway

191
06:52.039 --> 06:55.054
and we'll go to tier one gateway B, click on the three dots,

192
06:55.054 --> 06:57.540
click on edit from the menu,

193
06:57.540 --> 06:59.790
and then select the tier zero gateway like that.

194
06:59.790 --> 07:01.260
And then click on save.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

194
06:59.790 --> 07:01.260
And then click on save.

195
07:01.260 --> 07:02.640
And then we'll go ahead and scroll down.

196
07:02.640 --> 07:04.110
We'll click on close editing.

197
07:04.110 --> 07:06.930
So now we can see we have our tier one gateways A and B

198
07:06.930 --> 07:08.790
both connected to gateway zero,

199
07:08.790 --> 07:10.770
which is a tier zero gateway.

200
07:10.770 --> 07:12.120
And here it says in progress.

201
07:12.120 --> 07:13.800
So if we click on the refresh button there,

202
07:13.800 --> 07:15.480
just wanna confirm that it's done.

203
07:15.480 --> 07:16.500
All right, that looks great.

204
07:16.500 --> 07:18.076
So if we go back to our network topology

205
07:18.076 --> 07:20.190
and if we expand that a little bit,

206
07:20.190 --> 07:22.800
so there's our second connection now between the gateway B

207
07:22.800 --> 07:24.600
and the tier zero router.

208
07:24.600 --> 07:26.550
And here are the IP address that it's using

209
07:26.550 --> 07:27.990
for each end of those connections.

210
07:27.990 --> 07:30.390
So these are two different subnets logically
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

210
07:27.990 --> 07:30.390
So these are two different subnets logically

211
07:30.390 --> 07:34.164
between the tier zero gateway and gateway A

212
07:34.164 --> 07:35.430
and the tier zero gateway and gateway B.

213
07:35.430 --> 07:36.720
So let me zoom out a little bit here.

214
07:36.720 --> 07:39.420
So if we took these PCs here, that are connect,

215
07:39.420 --> 07:42.180
these little VMs that are connected to these segments,

216
07:42.180 --> 07:43.830
they still don't have the ability to reach each other.

217
07:43.830 --> 07:45.030
And the reason for that is

218
07:45.030 --> 07:47.220
that even though we now have these three gateways,

219
07:47.220 --> 07:50.250
this tier zero gateway has no knowledge about the

220
07:50.250 --> 07:53.400
10 10 network down here behind gateway A

221
07:53.400 --> 07:55.560
and also doesn't have any knowledge about the routes

222
07:55.560 --> 07:58.650
down here to 10 20, which is behind gateway B.

223
07:58.650 --> 07:59.670
And also to verify that

224
07:59.670 --> 08:01.200
and also not to reinforce
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

224
07:59.670 --> 08:01.200
and also not to reinforce

225
08:01.200 --> 08:03.600
that all of our transport nodes have

226
08:03.600 --> 08:05.340
all three of these distributed routers.

227
08:05.340 --> 08:06.953
Let's for a moment go back to the command line.

228
08:06.953 --> 08:09.450
So here at both of our edges,

229
08:09.450 --> 08:12.150
let's go ahead and do a get gateways and press enter.

230
08:12.150 --> 08:13.380
And here are the three right here.

231
08:13.380 --> 08:15.993
So we have gateway A, B, and also gateway zero.

232
08:15.993 --> 08:18.630
And those same three distributed routers exist

233
08:18.630 --> 08:19.920
on both of our edges.

234
08:19.920 --> 08:22.440
And if we also looked at our host transport nodes,

235
08:22.440 --> 08:25.140
they would also have these three distributed routers

236
08:25.140 --> 08:26.580
and all the information regarding them.

237
08:26.580 --> 08:28.400
So if we were gonna take a look at the routing table

238
08:28.400 --> 08:30.819
on gateway zero, because it's in VRF four
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

238
08:28.400 --> 08:30.819
on gateway zero, because it's in VRF four

239
08:30.819 --> 08:32.340
as shown right here.

240
08:32.340 --> 08:34.936
The easiest way to work with and look at the details

241
08:34.936 --> 08:37.080
for that specific virtual router

242
08:37.080 --> 08:39.562
is to go ahead and simply go into VRF mode, for VRF four.

243
08:39.562 --> 08:43.110
And to do that, we'll type in "VRF 4", press enter.

244
08:43.110 --> 08:45.150
You'll notice the prompt changes to help us remember

245
08:45.150 --> 08:47.160
that we are now in VRF four.

246
08:47.160 --> 08:50.610
And then from here we can do commands like, get forwarding.

247
08:50.610 --> 08:52.980
So that command right here in VRF four

248
08:52.980 --> 08:55.260
is showing us the IP routing table.

249
08:55.260 --> 08:56.640
So also it's showing us down below,

250
08:56.640 --> 08:58.680
it's showing us the IPV6 as well.

251
08:58.680 --> 08:59.790
We're gonna focus our attention here

252
08:59.790 --> 09:01.530
for the moment on IPV4.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

252
08:59.790 --> 09:01.530
for the moment on IPV4.

253
09:01.530 --> 09:03.030
So notice that this logical router,

254
09:03.030 --> 09:04.720
our tier zero, gateway zero router,

255
09:04.720 --> 09:08.542
it knows about the directly connected networks of 100.64.0.0

256
09:08.542 --> 09:11.970
and 100.64.0.2,

257
09:11.970 --> 09:15.000
and it has IP addresses on those specific subnets.

258
09:15.000 --> 09:18.690
And those are the interlinks between itself, gateway zero

259
09:18.690 --> 09:21.660
and gateway A and gateway B, both as tier one routers.

260
09:21.660 --> 09:23.974
However, what it does not know about yet,

261
09:23.974 --> 09:25.800
it doesn't know anything about how

262
09:25.800 --> 09:30.240
to forward packets in the direction of 10 10 or 10 20.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

262
09:25.800 --> 09:30.240
to forward packets in the direction of 10 10 or 10 20.

263
09:30.240 --> 09:32.580
So to solve that, we're gonna go back to our game plan

264
09:32.580 --> 09:33.810
and implement this step right here,

265
09:33.810 --> 09:35.820
which is telling our tier one gateways,

266
09:35.820 --> 09:39.690
gateway A and gateway B, that they both need to advertise

267
09:39.690 --> 09:41.280
their directly connected networks.

268
09:41.280 --> 09:42.780
And when we tell 'em to advertise their

269
09:42.780 --> 09:44.100
directly connected networks,

270
09:44.100 --> 09:46.620
they'll then start advertising the 10 10 network,

271
09:46.620 --> 09:49.710
or at least gateway A will, up to the tier zero router.

272
09:49.710 --> 09:51.564
So the 10 10 network will be in the routing table.

273
09:51.564 --> 09:54.660
And when we tell gateway B to advertise

274
09:54.660 --> 09:55.762
its directly connected networks

275
09:55.762 --> 09:58.080
that will cause gateway zero to then learn

276
09:58.080 --> 10:01.530
about how to forward in the direction of 10 20 as well.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

276
09:58.080 --> 10:01.530
about how to forward in the direction of 10 20 as well.

277
10:01.530 --> 10:04.410
So in the next step, let's train these two tier one routers

278
10:04.410 --> 10:07.110
to advertise their directly connected subnets.

279
10:07.110 --> 10:09.660
So I'll see you in the next video for exactly that.