WEBVTT

1
00:03.683 --> 00:06.510
So step one of this task

2
00:06.510 --> 00:08.730
is actually fairly simple.

3
00:08.730 --> 00:12.810
We're just adding new interfaces to router one.

4
00:12.810 --> 00:17.160
So all we have to do is go into interface gigabit three

5
00:17.160 --> 00:19.110
and we have to add an IP address.

6
00:19.110 --> 00:24.110
We're supposed to add 10.10.20.1,

7
00:24.720 --> 00:27.030
and it's a slash 24.

8
00:27.030 --> 00:29.550
We'll now shut the interface to bring it up.

9
00:29.550 --> 00:33.270
We're also supposed to create an interface loop back zero.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:29.550 --> 00:33.270
We're also supposed to create an interface loop back zero.

10
00:33.270 --> 00:37.950
Its IP address is supposed to be 10.100.1.1,

11
00:37.950 --> 00:40.560
and this one is a slash 32.

12
00:40.560 --> 00:44.970
We can exit configuration, do a show IP interface brief,

13
00:44.970 --> 00:47.370
and we see that we now have our gigabit three

14
00:47.370 --> 00:51.690
and our loop back zero as the task required.

15
00:51.690 --> 00:55.110
Task two involves doing the same thing on router two.

16
00:55.110 --> 00:57.060
So let's go over to router two.

17
00:57.060 --> 00:59.430
Once again, configuration mode.

18
00:59.430 --> 01:01.200
This one just requires a loop back,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
00:59.430 --> 01:01.200
This one just requires a loop back,

19
01:01.200 --> 01:03.660
so interface loop back zero.

20
01:03.660 --> 01:08.660
The IP address on this one is 10.100.2.2, also a slash 32,

21
01:11.100 --> 01:13.290
and if we do a show IP interface brief,

22
01:13.290 --> 01:15.930
we see this loop back interface is up.

23
01:15.930 --> 01:19.920
So the first two tasks are relatively simple.

24
01:19.920 --> 01:21.960
Task three is the one

25
01:21.960 --> 01:24.540
that gets a little bit more interesting.

26
01:24.540 --> 01:27.510
We're supposed to configure router one and router two

27
01:27.510 --> 01:32.510
so that they only advertise a very specific set of subnets.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:27.510 --> 01:32.510
so that they only advertise a very specific set of subnets.

28
01:32.640 --> 01:35.640
The 10.10.0.0/16,

29
01:35.640 --> 01:39.810
the 10.10.20.0/24,

30
01:39.810 --> 01:44.810
and the 10.100.0.0/16.

31
01:45.180 --> 01:47.869
Now here's an interesting problem,

32
01:47.869 --> 01:52.200
I can't have, for example, router two

33
01:52.200 --> 01:55.200
advertise networks that it doesn't know.

34
01:55.200 --> 01:57.743
So if I say, show IP route here,

35
01:57.743 --> 02:02.743
I can't exactly inject the 10.10.20.0/24 subnet
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:57.743 --> 02:02.743
I can't exactly inject the 10.10.20.0/24 subnet

36
02:04.980 --> 02:06.540
here on router two

37
02:06.540 --> 02:09.330
because it doesn't know anything about it.

38
02:09.330 --> 02:12.900
So although it wasn't specified in the task,

39
02:12.900 --> 02:16.260
clearly we are going to need an IGP

40
02:16.260 --> 02:18.840
running on our on-prem environment

41
02:18.840 --> 02:20.430
in order to exchange the routes

42
02:20.430 --> 02:22.650
between router one and router two.

43
02:22.650 --> 02:25.593
So let's go ahead and fire up an IGP.

44
02:26.910 --> 02:29.790
Honestly, you can use any IGP here.

45
02:29.790 --> 02:32.610
If you want to use RIP or EIGRP,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

45
02:29.790 --> 02:32.610
If you want to use RIP or EIGRP,

46
02:32.610 --> 02:35.520
ISIS, use whatever you want.

47
02:35.520 --> 02:38.400
We're gonna fire up OSPF just because,

48
02:38.400 --> 02:40.860
it's of course, a fairly common protocol.

49
02:40.860 --> 02:42.663
We'll just fire up OSPF.

50
02:43.500 --> 02:45.060
So since we're already here on router two,

51
02:45.060 --> 02:47.700
we'll just go back into configuration mode.

52
02:47.700 --> 02:50.640
We'll say router OSPF one.

53
02:50.640 --> 02:53.970
We'll set our router ID to our loop back interface.

54
02:53.970 --> 02:56.850
So it's 10.100.2.2.

55
02:56.850 --> 03:00.000
Then we'll go into interface loop back zero.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

56
03:00.000 --> 03:03.750
So we'll simply say IP OSPF one, area zero.

57
03:03.750 --> 03:06.990
We'll also do this on the gigabit two interface.

58
03:06.990 --> 03:09.540
That should take care of router two's configuration.

59
03:09.540 --> 03:11.550
Now let's do router one.

60
03:11.550 --> 03:13.590
It's going to be almost the same, of course,

61
03:13.590 --> 03:15.930
just with different interfaces.

62
03:15.930 --> 03:18.870
So once again, router OSPF one,

63
03:18.870 --> 03:22.290
router ID is 10.100.1.1.

64
03:22.290 --> 03:25.260
We'll go into our interface loop back zero,

65
03:25.260 --> 03:30.260
put it in area zero, also gigabit two, and in this case,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

65
03:25.260 --> 03:30.260
put it in area zero, also gigabit two, and in this case,

66
03:30.600 --> 03:33.900
gigabit three since we brought that new network onto it,

67
03:33.900 --> 03:37.020
and router two needs to be aware of it.

68
03:37.020 --> 03:39.780
Let's verify our OSPF interfaces.

69
03:39.780 --> 03:41.160
This looks good.

70
03:41.160 --> 03:44.580
We can see in the state, on the gigabit interfaces,

71
03:44.580 --> 03:46.230
it is still in wait,

72
03:46.230 --> 03:49.140
since those are broadcast network types,

73
03:49.140 --> 03:51.630
it is still waiting for the DR election.

74
03:51.630 --> 03:54.090
So let's give it just a few moments.

75
03:54.090 --> 03:56.400
We do a show IPO SPF neighbor.

76
03:56.400 --> 03:59.400
We can see that now that we waited a few moments,

77
03:59.400 --> 04:03.570
we are now up with neighbor 10.100.2.2,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

77
03:59.400 --> 04:03.570
we are now up with neighbor 10.100.2.2,

78
04:03.570 --> 04:05.850
which is, of course, router two.

79
04:05.850 --> 04:08.460
If we do a show IP route OSPF,

80
04:08.460 --> 04:09.870
we can see that we are now learning

81
04:09.870 --> 04:13.080
about router two's loop back through OSPF,

82
04:13.080 --> 04:16.230
which means we could inject this into BGP.

83
04:16.230 --> 04:18.540
But more importantly is router two

84
04:18.540 --> 04:20.730
getting the network that it needs.

85
04:20.730 --> 04:22.980
If we do a show IP route OSPF,

86
04:22.980 --> 04:27.980
we see that now it has that 10.10.20.0/24 network.

87
04:28.890 --> 04:31.140
So our next step is simply going to be
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
04:28.890 --> 04:31.140
So our next step is simply going to be

88
04:31.140 --> 04:35.280
to inject these into BGP, using network statements.

89
04:35.280 --> 04:37.770
So we'll just go ahead and paste this configuration in.

90
04:37.770 --> 04:41.130
It's just network statements matching those networks.

91
04:41.130 --> 04:43.053
We'll do the same thing on router one.

92
04:45.390 --> 04:48.000
So now we can check what router one

93
04:48.000 --> 04:52.050
is actually advertising to AWS.

94
04:52.050 --> 04:54.630
We'll just pick on one of the neighbor-ships here

95
04:54.630 --> 04:57.330
and we'll do a show IP BGP neighbor

96
04:57.330 --> 04:59.310
for that specific neighbor that happens to be

97
04:59.310 --> 05:02.940
the one out router one's tunnel one interface,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

97
04:59.310 --> 05:02.940
the one out router one's tunnel one interface,

98
05:02.940 --> 05:05.520
and we'll say advertised routes.

99
05:05.520 --> 05:09.870
This tells us what routes we're sending to that neighbor.

100
05:09.870 --> 05:12.630
Now we can see here that this isn't exactly

101
05:12.630 --> 05:14.580
what we're supposed to be sending.

102
05:14.580 --> 05:15.870
So now let's configure this

103
05:15.870 --> 05:19.440
to send only the prefixes that we need to.

104
05:19.440 --> 05:22.110
Let's start with the easy one.

105
05:22.110 --> 05:27.110
We can very easily summarize the 10.100.0.0/16

106
05:28.980 --> 05:31.860
from these two loop backs that we have.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

106
05:28.980 --> 05:31.860
from these two loop backs that we have.

107
05:31.860 --> 05:36.860
So we simply go into BGP, into address family IPv4,

108
05:36.935 --> 05:41.935
and we'll do an aggregate address for 10.100.0.0/16,

109
05:44.910 --> 05:47.223
and we'll tell it to send summary only.

110
05:48.150 --> 05:50.670
Remember that BGP's default behavior

111
05:50.670 --> 05:52.680
when you do an aggregate address

112
05:52.680 --> 05:56.820
is to actually send the aggregate and the subnets.

113
05:56.820 --> 05:58.440
But if you look at our requirements,

114
05:58.440 --> 06:01.230
we're not supposed to send the subnets in this case,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

114
05:58.440 --> 06:01.230
we're not supposed to send the subnets in this case,

115
06:01.230 --> 06:02.763
so we'll say summary only.

116
06:03.630 --> 06:05.850
We'll go ahead and hit enter,

117
06:05.850 --> 06:09.150
and then we'll take a look at our advertised routes again.

118
06:09.150 --> 06:12.060
We see here it has not done the aggregate yet.

119
06:12.060 --> 06:13.260
Give it just a few moments,

120
06:13.260 --> 06:15.810
and we can see here that now it is.

121
06:15.810 --> 06:20.520
So now we're advertising the 10.100.0.0/16.

122
06:20.520 --> 06:25.520
Now the trickier one is the 10.10.0.0/16,

123
06:26.130 --> 06:31.130
and still sending the subnet, 10.10.20.0/24.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

123
06:26.130 --> 06:31.130
and still sending the subnet, 10.10.20.0/24.

124
06:33.570 --> 06:34.470
There's actually, sort of,

125
06:34.470 --> 06:37.530
two different approaches to this with PGP.

126
06:37.530 --> 06:41.850
I could do the aggregate address and then do a suppress map

127
06:41.850 --> 06:44.280
on the one that I don't wanna advertise,

128
06:44.280 --> 06:46.860
or I could still do the summary only,

129
06:46.860 --> 06:51.690
like we just did here, and then use an unsuppressed map.

130
06:51.690 --> 06:53.700
I think that one's a little more interesting,

131
06:53.700 --> 06:56.545
so let's take a look at the unsuppressed map.

132
06:56.545 --> 07:00.750
First thing we're gonna need is a prefix list.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

132
06:56.545 --> 07:00.750
First thing we're gonna need is a prefix list.

133
07:00.750 --> 07:03.720
So we're gonna create this prefix list

134
07:03.720 --> 07:08.160
and we're simply gonna call it PL_BGP leak,

135
07:08.160 --> 07:10.980
and it's gonna permit that subnet,

136
07:10.980 --> 07:15.980
the 10.10.20.0/24 that we still want to send.

137
07:16.560 --> 07:19.110
Then we create a route map.

138
07:19.110 --> 07:22.890
The route map will call RM_BGP leak,

139
07:22.890 --> 07:27.750
and this will match on the prefix list that we just wrote.

140
07:27.750 --> 07:31.950
Then we'll go into a router BGP process and we'll paste in
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

140
07:27.750 --> 07:31.950
Then we'll go into a router BGP process and we'll paste in

141
07:31.950 --> 07:35.730
the information that we need to make this work.

142
07:35.730 --> 07:37.140
So the important things to note

143
07:37.140 --> 07:40.080
that we're doing here in our BGP statements,

144
07:40.080 --> 07:43.320
first, we're putting in our aggregate address, as we said,

145
07:43.320 --> 07:45.450
but then for each of our neighbors,

146
07:45.450 --> 07:48.030
we're calling to the route map we created

147
07:48.030 --> 07:50.550
with an unsuppressed map.

148
07:50.550 --> 07:53.610
If we were to say, show IP BGP,

149
07:53.610 --> 07:55.060
notice that the 10.10.10.0/24

150
07:57.471 --> 08:00.523
and the 10.10.20.0/24 are both suppressed.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

150
07:57.471 --> 08:00.523
and the 10.10.20.0/24 are both suppressed.

151
08:03.030 --> 08:04.080
However,

152
08:04.080 --> 08:07.030
if we look at what we're sending to our neighbor again,

153
08:07.030 --> 08:10.680
notice that suppressed prefix,

154
08:10.680 --> 08:15.680
the 10.10.20.0/24, is in fact being sent.

155
08:16.950 --> 08:20.670
So the only thing we have here that we really shouldn't

156
08:20.670 --> 08:25.670
is the 10.20.0.0/16

157
08:25.710 --> 08:30.710
is actually being advertised back to AWS.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

157
08:25.710 --> 08:30.710
is actually being advertised back to AWS.

158
08:30.720 --> 08:33.180
That's the prefix that we're learning from AWS,

159
08:33.180 --> 08:35.220
and we're sending it back.

160
08:35.220 --> 08:37.230
This is not a good thing to do.

161
08:37.230 --> 08:39.510
Of course, AWS would discard it

162
08:39.510 --> 08:42.750
because it has their AS in the AS path,

163
08:42.750 --> 08:44.790
but we still shouldn't be sending it.

164
08:44.790 --> 08:48.390
So just one more thing we want to do here for good measure,

165
08:48.390 --> 08:53.390
let's add a prefix list to not send that route back to AWS.

166
08:54.990 --> 08:57.510
So we'll simply create a prefix list.

167
08:57.510 --> 09:00.843
We'll call it PL_BGP_filter_out.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

167
08:57.510 --> 09:00.843
We'll call it PL_BGP_filter_out.

168
09:01.800 --> 09:05.640
We're gonna deny the 10.20.0.0/16,

169
09:05.640 --> 09:08.100
and then permit everything else.

170
09:08.100 --> 09:10.860
Then we simply go back into BGP

171
09:10.860 --> 09:14.910
and apply that prefix list to our two neighbors.

172
09:14.910 --> 09:16.410
Now that that's applied,

173
09:16.410 --> 09:19.560
let's take a look at what's being advertised again.

174
09:19.560 --> 09:22.576
And if we take a look at this output, this is exactly

175
09:22.576 --> 09:26.353
what we were supposed to accomplish in this task.

176
09:26.353 --> 09:29.490
Now, as you can see, this wasn't exactly easy.

177
09:29.490 --> 09:32.340
Took a couple prefix lists, the route maps,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

177
09:29.490 --> 09:32.340
Took a couple prefix lists, the route maps,

178
09:32.340 --> 09:35.105
to it filtering and BGP manipulation.

179
09:35.105 --> 09:37.560
We've only done this on router one.

180
09:37.560 --> 09:40.138
We need to configure it on router two as well,

181
09:40.138 --> 09:43.020
but there's no sense in typing all of that in again.

182
09:43.020 --> 09:46.320
It's all going to be the exact same configuration.

183
09:46.320 --> 09:49.980
So we'll just paste the same configuration in on router two

184
09:49.980 --> 09:53.070
and make sure that it behaves the same way.

185
09:53.070 --> 09:53.903
Let's go ahead and paste

186
09:53.903 --> 09:56.790
that exact same configuration in here.

187
09:56.790 --> 09:58.500
As long as everything has worked okay,

188
09:58.500 --> 10:01.260
we can verify our advertised routes here as well.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

188
09:58.500 --> 10:01.260
we can verify our advertised routes here as well.

189
10:01.260 --> 10:03.150
We'll just give BGPA moment

190
10:03.150 --> 10:06.420
to converge and run the BGP scanner.

191
10:06.420 --> 10:08.670
So we'll look at one of router two's neighbors,

192
10:08.670 --> 10:10.290
look at its advertised routes,

193
10:10.290 --> 10:12.270
and we see that this is exactly

194
10:12.270 --> 10:14.520
what it's supposed to be advertising.

195
10:14.520 --> 10:17.550
So now we have BGP configured properly.

196
10:17.550 --> 10:20.670
That takes care of task three.

197
10:20.670 --> 10:24.450
Task four says we're supposed to configure VRRP,

198
10:24.450 --> 10:27.163
or HSRP, if that's what you're using.

199
10:27.163 --> 10:31.830
So that router one will switch to a backup or standby
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

199
10:27.163 --> 10:31.830
So that router one will switch to a backup or standby

200
10:31.830 --> 10:35.670
if both of the tunnels on R one go down,

201
10:35.670 --> 10:38.550
but not if only one tunnel goes down.

202
10:38.550 --> 10:41.460
Well, this is actually far easier than it sounds.

203
10:41.460 --> 10:43.830
Let's jump over to router one.

204
10:43.830 --> 10:46.470
Let's do a show VRRP.

205
10:46.470 --> 10:51.470
Remember, we're the master and we have a priority of 110.

206
10:51.810 --> 10:53.850
Well, here's the thing.

207
10:53.850 --> 10:58.320
We already have tracked objects tracking our tunnels.

208
10:58.320 --> 11:00.480
So literally, all we have to do
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

208
10:58.320 --> 11:00.480
So literally, all we have to do

209
11:00.480 --> 11:03.120
is go into configuration mode,

210
11:03.120 --> 11:06.270
go into our interface gigabit two,

211
11:06.270 --> 11:09.060
which is where VRRP is configured,

212
11:09.060 --> 11:14.060
say VRRP one, track 100, and decrement it by,

213
11:15.930 --> 11:20.930
well, something more than five and less than 10.

214
11:22.260 --> 11:23.340
We just need to make sure

215
11:23.340 --> 11:27.900
that both numbers added together will drop it below 100,

216
11:27.900 --> 11:30.360
which is what the backup is right now.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

216
11:27.900 --> 11:30.360
which is what the backup is right now.

217
11:30.360 --> 11:33.570
So let's say, for example, we decrement by six.

218
11:33.570 --> 11:37.830
We'll do the same thing, tracking 200.

219
11:37.830 --> 11:39.630
Here's how this works.

220
11:39.630 --> 11:43.440
If I go into interface tunnel one

221
11:43.440 --> 11:48.390
and I do a shutdown on it, and I do a show VRRP,

222
11:48.390 --> 11:52.020
we can see that the tracked object isn't quite that fast.

223
11:52.020 --> 11:54.150
Let's give it just a moment.

224
11:54.150 --> 11:56.610
We'll try our VRRP again.

225
11:56.610 --> 12:01.260
Now we can see that it sees the track object 100 is down,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

225
11:56.610 --> 12:01.260
Now we can see that it sees the track object 100 is down,

226
12:01.260 --> 12:02.850
it's decremented by six.

227
12:02.850 --> 12:07.850
Our priority is currently 104, but we're still master.

228
12:09.270 --> 12:12.480
If both tunnels go down, however,

229
12:12.480 --> 12:14.460
again, we'll give it a moment.

230
12:14.460 --> 12:16.590
Do show VRRP again,

231
12:16.590 --> 12:21.590
notice that our two decrements together are now 12,

232
12:21.600 --> 12:25.890
taking us down to 98, which is below the 100

233
12:25.890 --> 12:28.290
that router two is configured with.

234
12:28.290 --> 12:30.450
So we see that we are now back up
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

234
12:28.290 --> 12:30.450
So we see that we are now back up

235
12:30.450 --> 12:34.230
and router two is now the master.

236
12:34.230 --> 12:37.020
Of course, if we were to bring these back up,

237
12:37.020 --> 12:39.866
we'll exit out of configuration, we'll leave it this way.

238
12:39.866 --> 12:43.020
Once the tracked objects come back up,

239
12:43.020 --> 12:45.750
VRRP should take back over.

240
12:45.750 --> 12:49.440
We can see here that we're back up to a priority of 110

241
12:49.440 --> 12:52.020
and our state is now the master.

242
12:52.020 --> 12:55.380
So that takes care of all of the parts in this challenge

243
12:55.380 --> 12:58.860
as well as everything that we need to cover in this skill.

244
12:58.860 --> 13:02.070
So that said, congratulations on completing
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

244
12:58.860 --> 13:02.070
So that said, congratulations on completing

245
13:02.070 --> 13:06.450
Configure Redundancy with iOS, XE, and AWS.

246
13:06.450 --> 13:09.060
I hope this has been informative for you,

247
13:09.060 --> 13:11.103
and I'd like to thank you for viewing.