WEBVTT

1
00:00.000 --> 00:03.670
In the previous couple of videos, we walked through configuring EAGRP with

2
00:03.670 --> 00:04.960
traditional mode and name

3
00:04.960 --> 00:08.280
mode. And in this video, I'd like to walk you through using the option of

4
00:08.280 --> 00:10.160
variance for unequal cost

5
00:10.160 --> 00:14.170
load balancing inside EAGRP. I'm going to show you how to do it on either

6
00:14.170 --> 00:15.760
flavor of implementation

7
00:15.760 --> 00:19.920
named or traditional. Now, by default, a router like R4 or any other router

8
00:19.920 --> 00:20.880
running EAGRP,

9
00:20.880 --> 00:24.960
if it has two or three routes that have the same exact metric and it's the best

10
00:24.960 --> 00:25.760
for the lowest

11
00:25.760 --> 00:29.860
metric for a specific destination, it will automatically install and start

12
00:29.860 --> 00:31.360
using those equal cost
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:29.860 --> 00:31.360
using those equal cost

13
00:31.360 --> 00:36.050
paths. But in the event, R4 has a successor route that goes this way and then

14
00:36.050 --> 00:37.120
feasible successor

15
00:37.120 --> 00:41.300
routes to go this way and that way, we could tell R4 that we want to go ahead

16
00:41.300 --> 00:42.560
and start using

17
00:42.560 --> 00:47.040
additional potential paths and start doing load balancing across all of them.

18
00:47.040 --> 00:47.680
Now, here's how it

19
00:47.680 --> 00:52.320
works. Let's imagine that the successor route has a metric of 10. So I know

20
00:52.320 --> 00:54.720
that's a small number in EAGRP,

21
00:54.720 --> 00:58.670
but it's easier to look at and talk about. So if that's the successor metric,

22
00:58.670 --> 00:59.280
let's imagine we have

23
00:59.280 --> 01:03.910
feasible successor one that has a metric of 11 and we have feasible successor
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:59.280 --> 01:03.910
feasible successor one that has a metric of 11 and we have feasible successor

24
01:03.910 --> 01:05.280
two that has a metric

25
01:05.280 --> 01:11.040
of, let's say, 19 and let's say feasible successor three has a metric of, let's

26
01:11.040 --> 01:13.200
say, 21. Now, if this

27
01:13.200 --> 01:17.320
is our successor metric of 10, we're going to use a command called variance.

28
01:17.320 --> 01:18.320
Variant simply says

29
01:18.320 --> 01:21.740
to the router that you configured on how bad can a route be. So if we said the

30
01:21.740 --> 01:23.120
variance is two,

31
01:23.120 --> 01:27.100
that means that if we take the successor route and it's metric of 10 and we

32
01:27.100 --> 01:28.400
multiply that by two,

33
01:28.400 --> 01:33.020
which would be 20, it says basically any feasible successor that met that feas
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

33
01:28.400 --> 01:33.020
which would be 20, it says basically any feasible successor that met that feas

34
01:33.020 --> 01:34.240
ibility condition,

35
01:34.240 --> 01:38.440
any feasible successor that have a metric of 20 or less. So that would work and

36
01:38.440 --> 01:39.360
that would work

37
01:39.360 --> 01:43.530
can also be used and they can start load balancing across all three of those

38
01:43.530 --> 01:45.200
paths for the destination

39
01:45.200 --> 01:49.590
8888, for example. However, the feasible successor three because it's more than

40
01:49.590 --> 01:50.880
two times higher

41
01:50.880 --> 01:54.400
is 21 and so it's just above that threshold because it's higher than that

42
01:54.400 --> 01:55.440
threshold, it won't be

43
01:55.440 --> 01:58.640
considered to be used as part of equal cost load balancing. So once again, I'd

44
01:58.640 --> 01:59.280
like to give the

45
01:59.280 --> 02:03.210
opportunity if you want to launch the lab and do this right now with me. The
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

45
01:59.280 --> 02:03.210
opportunity if you want to launch the lab and do this right now with me. The

46
02:03.210 --> 02:04.000
link is near the end

47
02:04.000 --> 02:07.660
of the skill you can click on it, the lab come up and do that or you can do the

48
02:07.660 --> 02:08.480
lab at the very end

49
02:08.480 --> 02:11.780
as well. Either way is great because what we're going to do is we are going to

50
02:11.780 --> 02:12.720
reset the routing

51
02:12.720 --> 02:16.450
environment on this topology. So let's do that back at server one. So I

52
02:16.450 --> 02:18.080
minimize this. There's our

53
02:18.080 --> 02:22.070
text document. This is server one. So I've got my multi-tap putty here and I've

54
02:22.070 --> 02:23.040
also got our document

55
02:23.040 --> 02:27.310
right here and I'm going to go ahead and I'm going to first of all do it with

56
02:27.310 --> 02:29.120
traditional IPv4. So I'm

57
02:29.120 --> 02:34.330
going to take the traditional IPv4 implementation of eAGRP. Copy that, copy
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:29.120 --> 02:34.330
going to take the traditional IPv4 implementation of eAGRP. Copy that, copy

58
02:34.330 --> 02:35.680
that and then use the

59
02:35.680 --> 02:39.070
option we talked about earlier. I'll paste it in there and then I'm going to

60
02:39.070 --> 02:40.160
apply that to all the

61
02:40.160 --> 02:45.290
routers and not apply it to the PCs and send it. So effectively that removes

62
02:45.290 --> 02:46.320
all eAGRP whether it

63
02:46.320 --> 02:51.700
was named or traditional and it put in traditional eAGRP. So as a spot check if

64
02:51.700 --> 02:53.360
we did a show IP route

65
02:53.360 --> 02:59.700
for 8.8.8.8.8. There is our route going through the next top of 242 which is R2

66
02:59.700 --> 03:00.960
. So right now what
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
02:59.700 --> 03:00.960
. So right now what

67
03:00.960 --> 03:06.640
that means is that R4 if it wanted to forward traffic down to R8 to 8.8.8.8.8.

68
03:06.640 --> 03:07.760
It would send it up to R2

69
03:07.760 --> 03:11.000
and then R2 would make kids routing decision and so on and so forth. Now one

70
03:11.000 --> 03:12.000
question we might

71
03:12.000 --> 03:15.980
ask ourselves is why in the world is R4 going to forward a packet if we're

72
03:15.980 --> 03:18.960
trying to get to 8.8.8.8.8.

73
03:18.960 --> 03:22.780
Why is it forwarding it this way? Why is that the successor route? So I'll put

74
03:22.780 --> 03:23.280
it S there for

75
03:23.280 --> 03:26.680
successor and then we have feasible successors that it's not currently using

76
03:26.680 --> 03:28.160
going to R3 and then

77
03:28.160 --> 03:34.140
going down to R6. And I designed this topology with this in mind because I want
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

77
03:28.160 --> 03:34.140
going down to R6. And I designed this topology with this in mind because I want

78
03:34.140 --> 03:35.760
you to think about

79
03:35.760 --> 03:41.130
what is considered as part of the metric calculation for eAGRP. And if you

80
03:41.130 --> 03:42.480
think back to our earlier

81
03:42.480 --> 03:47.500
videos it's going to be the sum of delays. So that goes into the calculation

82
03:47.500 --> 03:49.520
and the lowest

83
03:49.520 --> 03:58.320
bandwidth in the path. So let's consider for a moment what the default delay is

84
03:58.320 --> 03:59.280
for gigabit,

85
03:59.280 --> 04:04.620
the default delay is for Ethernet and then also I artificially specified a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

85
03:59.280 --> 04:04.620
the default delay is for Ethernet and then also I artificially specified a

86
04:04.620 --> 04:06.240
bandwidth of 64

87
04:06.240 --> 04:09.890
kilovit per second on all the serial links. So let's go take a look and

88
04:09.890 --> 04:10.960
identify what those

89
04:10.960 --> 04:15.170
delays look like from the actual router's perspective. So we can go to R3 and

90
04:15.170 --> 04:16.640
look at all three of those

91
04:16.640 --> 04:21.450
right now because R3 has a gigabit Ethernet interface, it has a fast Ethernet

92
04:21.450 --> 04:22.480
and it has a serial

93
04:22.480 --> 04:27.860
so let's go to R3. So here on R3 let's do a show interface gig one slash zero,

94
04:27.860 --> 04:29.120
fantastic. So here

95
04:29.120 --> 04:33.360
is showing us two things about this interface, the bandwidth which is 1 million
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

95
04:29.120 --> 04:33.360
is showing us two things about this interface, the bandwidth which is 1 million

96
04:33.360 --> 04:34.640
kilovits per second

97
04:34.640 --> 04:39.500
and also the delay. So the default delay on a gigabit Ethernet interface is 10

98
04:39.500 --> 04:40.320
microseconds.

99
04:40.320 --> 04:44.850
Let's document that. So for the gigabit links it'll be 10 microseconds, great

100
04:44.850 --> 04:45.840
great great and next

101
04:45.840 --> 04:49.860
let's take a look at fast Ethernet 4 slash zero. So on R3 we'll do a show

102
04:49.860 --> 04:51.520
interface for fast Ethernet

103
04:51.520 --> 04:55.710
4 slash zero and press enter. So here we have our bandwidth which is 100,000

104
04:55.710 --> 04:56.880
kilovits per second

105
04:56.880 --> 05:01.830
and this delay is 10 times worse than the gigabit. So the delay is 100 microse
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

105
04:56.880 --> 05:01.830
and this delay is 10 times worse than the gigabit. So the delay is 100 microse

106
05:01.830 --> 05:02.960
conds. So we'll document

107
05:02.960 --> 05:08.840
that next. So the fast Ethernet here would be 100 microseconds and 100 here.

108
05:08.840 --> 05:09.440
And then finally let's

109
05:09.440 --> 05:14.180
take a look at our serial links at their delay. So on R3 we'll look at serial

110
05:14.180 --> 05:15.920
interface 3 slash 2

111
05:15.920 --> 05:20.320
as an example and again on all these serial interfaces I artificially lowered

112
05:20.320 --> 05:22.320
the bandwidth to 64

113
05:22.320 --> 05:25.690
kilovits per second which is also going to have an effect on the delay. So if

114
05:25.690 --> 05:26.800
we do a show interface

115
05:26.800 --> 05:31.460
serial 3 slash 2 and press enter. So here's the bandwidth that I manually put
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

115
05:26.800 --> 05:31.460
serial 3 slash 2 and press enter. So here's the bandwidth that I manually put

116
05:31.460 --> 05:32.400
on all those serial

117
05:32.400 --> 05:38.130
interfaces and here is the delay. Oh my gosh, 20,000 microseconds. So let's go

118
05:38.130 --> 05:39.520
document that. So that's

119
05:39.520 --> 05:45.110
going to be 20K microseconds and the same thing for the serial link right here.

120
05:45.110 --> 05:46.640
Let's go to 20K

121
05:46.640 --> 05:51.610
here as well. So for this route to 8.8.8.8 and our four is making its

122
05:51.610 --> 05:53.440
calculations on what is the

123
05:53.440 --> 05:58.380
best path based on the composite metric. It's using the sum of the delays as

124
05:58.380 --> 05:59.760
well as the lowest

125
05:59.760 --> 06:03.250
bandwidth in the path. So from our fours perspective the lowest bandwidth in
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

125
05:59.760 --> 06:03.250
bandwidth in the path. So from our fours perspective the lowest bandwidth in

126
06:03.250 --> 06:04.400
the path is always going to be

127
06:04.400 --> 06:07.850
64K because it's going to have to go through either this serial link or that

128
06:07.850 --> 06:08.880
serial link to get there

129
06:08.880 --> 06:11.760
and that's the lowest bandwidth in the path. So that's going to go into the

130
06:11.760 --> 06:12.720
calculation and then the

131
06:12.720 --> 06:17.140
other factor is going to be the sum of the delays. So let's go ahead and use a

132
06:17.140 --> 06:18.400
couple colors. Let's go

133
06:18.400 --> 06:24.070
ahead and calculate the sum of the delays if our four was going to go here to

134
06:24.070 --> 06:25.680
here and then our three

135
06:25.680 --> 06:29.370
could route it down to our 8. So we'll call that path a. So some of the delays

136
06:29.370 --> 06:32.080
there would be 20,100
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

136
06:29.370 --> 06:32.080
there would be 20,100

137
06:32.080 --> 06:35.720
for the sum there. So that would go into the calculation as we're talking about

138
06:35.720 --> 06:36.400
these sum of

139
06:36.400 --> 06:40.740
the delays and let's use another color here for the path from our four going

140
06:40.740 --> 06:42.000
this direction. So the

141
06:42.000 --> 06:47.250
delays here would be ethernet would be 100. So here on path B the sum of the

142
06:47.250 --> 06:50.400
delays would be 20,100

143
06:50.400 --> 06:53.600
and let's calculate the path that based on the routing table is going to be

144
06:53.600 --> 06:54.400
using and that's going

145
06:54.400 --> 06:59.830
this direction. So for path C it'd be 10 for this leg of the journey and 10

146
06:59.830 --> 07:01.120
more for that leg and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

146
06:59.830 --> 07:01.120
more for that leg and

147
07:01.120 --> 07:06.550
then 10 more for there and then it'd be 20,000 here so that'd be 20,000 and 30.

148
07:06.550 --> 07:06.880
And that's why

149
07:06.880 --> 07:11.320
router 4 has a lower feasible distance going up through our two is because as

150
07:11.320 --> 07:12.560
part of its calculation

151
07:12.560 --> 07:19.930
the sum of the delay is 20,030 versus 20,100 this way going through path a or

152
07:19.930 --> 07:22.960
20,100 going through path b.

153
07:22.960 --> 07:28.780
So just to confirm if we go back to our four and we do a show IP eEdGRP top

154
07:28.780 --> 07:29.920
ology and press enter

155
07:29.920 --> 07:34.280
we'll go down a few lines we'll stop around the 888 network right here it has
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

155
07:29.920 --> 07:34.280
we'll go down a few lines we'll stop around the 888 network right here it has

156
07:34.280 --> 07:35.440
one successor

157
07:35.440 --> 07:39.690
and that feasible distance is this metric right here and that's going through

158
07:39.690 --> 07:40.480
our two and then we

159
07:40.480 --> 07:44.870
have two feasible successors where we could use those if the primary route goes

160
07:44.870 --> 07:46.320
away or if we use

161
07:46.320 --> 07:50.930
the variance command we can specify that anything that two times are three

162
07:50.930 --> 07:52.720
times are four times

163
07:52.720 --> 07:55.970
this current metric. If we have feasible successors within that range they

164
07:55.970 --> 07:57.440
could also be used and we

165
07:57.440 --> 08:01.060
can start doing proportional load balancing. Now in this case each of the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

165
07:57.440 --> 08:01.060
can start doing proportional load balancing. Now in this case each of the

166
08:01.060 --> 08:02.240
metrics is so close

167
08:02.880 --> 08:05.930
for the feasible successors that it'd probably be doing equal cost load

168
08:05.930 --> 08:06.800
balancing but if you

169
08:06.800 --> 08:10.630
had some links that were like two or three or four times as worse and you set

170
08:10.630 --> 08:12.400
the variance to like five

171
08:12.400 --> 08:16.760
if then do proportional load balancing and send more traffic over the much

172
08:16.760 --> 08:17.600
better paths

173
08:17.600 --> 08:21.440
and less traffic over the least best paths but because our metrics are so darn

174
08:21.440 --> 08:22.400
close it's very likely

175
08:22.400 --> 08:26.650
to do equal cost load balancing because it's just a almost a rounding error

176
08:26.650 --> 08:27.520
about the metrics

177
08:27.520 --> 08:31.600
involved here. So currently let me verify which flavor of eEdGRP we just put in
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

177
08:27.520 --> 08:31.600
involved here. So currently let me verify which flavor of eEdGRP we just put in

178
08:31.600 --> 08:32.080
we'll do a show

179
08:32.080 --> 08:36.250
IP protocols. So let's do a show run pipe section router. I think we did

180
08:36.250 --> 08:38.080
traditional but just to confirm

181
08:38.080 --> 08:41.390
sure enough and so if we wanted to we could go into router configuration mode

182
08:41.390 --> 08:42.400
with a config T

183
08:42.400 --> 08:49.040
I'll just copy paste router eEdGRP 18 in and let's do a quick do show IP route

184
08:49.040 --> 08:51.120
for 8888. We should have

185
08:51.120 --> 08:55.950
one specific route that's going through the next top of 10.0.24.2 which is true

186
08:55.950 --> 08:57.680
. Now check this out

187
08:57.680 --> 09:01.570
now we can use the variance command and we can say variance for example five
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

187
08:57.680 --> 09:01.570
now we can use the variance command and we can say variance for example five

188
09:01.570 --> 09:02.480
and what effectively

189
09:02.480 --> 09:07.600
that means is that any feasible successors that we have if their metric is not

190
09:07.600 --> 09:09.520
worse than five times

191
09:09.520 --> 09:13.000
the current metric or the feasible distance for the successor route go ahead

192
09:13.000 --> 09:13.920
and also use them.

193
09:13.920 --> 09:17.770
Now in our case they're all super close so we could do a variance of two and

194
09:17.770 --> 09:18.320
what that would mean

195
09:18.320 --> 09:22.530
is that any feasible successors that have a metric that's not greater than two

196
09:22.530 --> 09:23.360
times the current

197
09:23.360 --> 09:27.320
feasible distance that's the metric for the winning route they can be used for

198
09:27.320 --> 09:28.720
load balancing. So

199
09:28.720 --> 09:33.210
let's go ahead and do variance two. Let's do a do show IP route in fact I can
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

199
09:28.720 --> 09:33.210
let's go ahead and do variance two. Let's do a do show IP route in fact I can

200
09:33.210 --> 09:33.920
hit the upper

201
09:33.920 --> 09:36.650
acute few times for that. Well the do show route in fact I can hit the upper

202
09:36.650 --> 09:37.440
acute a couple times

203
09:37.440 --> 09:43.090
for that. Let's do a do show IP route for 8888 and check this out. Now we have

204
09:43.090 --> 09:45.040
this route 10.0.24.2

205
09:45.040 --> 09:51.180
is the next top but we also have the next top of 10.0.34.3 and 10.2.46.6 and

206
09:51.180 --> 09:52.160
also because the metrics

207
09:52.160 --> 09:56.470
are so close check this out. We have that metric versus that metric. No no

208
09:56.470 --> 09:57.440
store even those are

209
09:57.440 --> 10:01.880
feasible successors and then we have this metric for what was the successor
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

209
09:57.440 --> 10:01.880
feasible successors and then we have this metric for what was the successor

210
10:01.880 --> 10:02.960
route because they're so

211
10:02.960 --> 10:07.420
darn close it's showing the traffic share count for this route is one and one

212
10:07.420 --> 10:08.880
for that and one for

213
10:08.880 --> 10:12.970
that where if we had significantly different metrics and we use the variance

214
10:12.970 --> 10:14.080
command the routes that

215
10:14.080 --> 10:18.760
did qualify and they did get the routing table they would have a traffic count

216
10:18.760 --> 10:19.840
that's higher for

217
10:19.840 --> 10:23.780
the preferred route and a lower traffic share count for the less preferred

218
10:23.780 --> 10:24.640
routes based on the

219
10:24.640 --> 10:28.640
metrics. So also right here if we did a show IP route and we get down to 8888

220
10:28.640 --> 10:29.520
so we'll be down a

221
10:29.520 --> 10:33.600
page or two here. There we go. Now in our routing table we have three routes
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

221
10:29.520 --> 10:33.600
page or two here. There we go. Now in our routing table we have three routes

222
10:33.600 --> 10:35.040
that we can load balance

223
10:35.040 --> 10:40.710
across. And if we did a show IP edg rp topology and pressed enter check this

224
10:40.710 --> 10:41.440
out for you down to

225
10:41.440 --> 10:45.830
8888 network. It's now showing that we have three successors three winners that

226
10:45.830 --> 10:46.480
all got in and

227
10:46.480 --> 10:50.630
that's because we set up the variance of two and just as a verification of that

228
10:50.630 --> 10:51.520
video show run

229
10:51.520 --> 10:56.660
section router we can verify that as well. So there's our variance command and

230
10:56.660 --> 10:57.920
if we remove that

231
10:57.920 --> 11:02.560
for example let's go ahead and go into router edg rp 18 and we said no variance
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

231
10:57.920 --> 11:02.560
for example let's go ahead and go into router edg rp 18 and we said no variance

232
11:02.560 --> 11:03.600
and then we do do show

233
11:03.600 --> 11:08.080
IP edg rp topology and go down to 8888 network you'll notice that we now only

234
11:08.080 --> 11:09.360
can have one successor

235
11:09.360 --> 11:12.890
route and the other two are feasible successors. Then we put it back with

236
11:12.890 --> 11:14.240
variance two so now we do

237
11:14.240 --> 11:18.970
variance two and we look at the IP edg rp topology table once again for that 8

238
11:18.970 --> 11:21.120
888 network we now have

239
11:21.120 --> 11:25.130
three successors. We could also verify that with a trace. So if we did a trace

240
11:25.130 --> 11:26.560
down in fact let's just

241
11:26.560 --> 11:31.320
do it long hand with a trace route IP going to 8888 and let's go ahead and use
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

241
11:26.560 --> 11:31.320
do it long hand with a trace route IP going to 8888 and let's go ahead and use

242
11:31.320 --> 11:32.480
this default source

243
11:32.480 --> 11:35.950
address and we'll press enter a few times and then for the probe count let's go

244
11:35.950 --> 11:37.120
ahead and do

245
11:37.120 --> 11:41.640
let's do 10 for each probe press enter a few times let that run check this out

246
11:41.640 --> 11:42.160
for the first

247
11:42.160 --> 11:45.910
top let's bring up our topology real quick. For the first top as r4 is doing a

248
11:45.910 --> 11:47.440
trace to 8888 it's

249
11:47.440 --> 11:54.400
using 10 0242 and then for the second one 10 0343 that's r3 and for the third

250
11:54.400 --> 11:56.400
one 10246 and this

251
11:56.400 --> 12:00.260
doing a round robin once again for two three and six two three and six and then
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

251
11:56.400 --> 12:00.260
doing a round robin once again for two three and six two three and six and then

252
12:00.260 --> 12:00.800
for the second

253
12:00.800 --> 12:05.290
hop in the path that would be depending on the routing tables for r2 and r3 and

254
12:05.290 --> 12:06.480
r6 respectively.

255
12:06.480 --> 12:10.590
So that's another quick way to verify that the behavior that we're expecting

256
12:10.590 --> 12:11.520
with load balancing

257
12:11.520 --> 12:15.580
with eagrp is happening as expected. Now I also want to show you the other

258
12:15.580 --> 12:17.280
option that's using variants

259
12:17.280 --> 12:21.540
in the world of named eagrp so if we grab the notepad document again and we go

260
12:21.540 --> 12:22.160
to the section we're

261
12:22.160 --> 12:24.520
going to remove all of our current routing and we're going to use the address

262
12:24.520 --> 12:25.360
families I'll go down

263
12:25.360 --> 12:29.090
right here we'll copy that and I'm going to plug this into all eight routers

264
12:29.090 --> 12:30.000
once again so we'll
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

265
12:30.000 --> 12:34.030
go to the option here we'll go to the type your script section click there

266
12:34.030 --> 12:35.040
paste it in send that

267
12:35.040 --> 12:39.330
to all of our devices except for our PCs and then click on send script and that

268
12:39.330 --> 12:40.240
will remove any

269
12:40.240 --> 12:44.320
current routing that we have and it will then set up named eagrp so I can

270
12:44.320 --> 12:45.600
demonstrate how to do

271
12:45.600 --> 12:51.510
variants inside named eagrp and so the option for that is to go into your eagrp

272
12:51.510 --> 12:53.360
named configuration

273
12:53.360 --> 12:57.950
go into the address family for ib-4 then you go into topology base and then

274
12:57.950 --> 12:59.040
into topology base you

275
12:59.040 --> 13:03.000
save variants too so I'm going to take that and I'm going to go ahead and put
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

275
12:59.040 --> 13:03.000
save variants too so I'm going to take that and I'm going to go ahead and put

276
13:03.000 --> 13:04.160
that on actually I don't

277
13:04.160 --> 13:07.790
need all routers I see it on r4 for demo so I'm going to grab this and just put

278
13:07.790 --> 13:08.640
these commands here

279
13:08.640 --> 13:13.300
on r4 so I'll right click copy that and then here on r4 let's do a show ip

280
13:13.300 --> 13:14.480
route and take a look at

281
13:14.480 --> 13:18.940
8888 we have one specific route that's going through r2 again but once we go

282
13:18.940 --> 13:20.320
ahead and I just highlighted

283
13:20.320 --> 13:24.060
that so I need to go back and copy again so I'm going to copy that from notepad

284
13:24.060 --> 13:25.440
paste it into r4

285
13:25.440 --> 13:28.860
another variants is to check this out now if we do a show ip route and we go

286
13:28.860 --> 13:30.240
down a little bit now
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

286
13:28.860 --> 13:30.240
down a little bit now

287
13:30.240 --> 13:34.770
for the 8888 network we now have three routes in our routing table going

288
13:34.770 --> 13:36.480
through r6 our three and

289
13:36.480 --> 13:39.930
our two as next tops and let me show this syntax for that once again with this

290
13:39.930 --> 13:41.040
show run section

291
13:41.040 --> 13:44.650
router and press center give that a moment to process and there's the

292
13:44.650 --> 13:46.400
configuration so inside the

293
13:46.400 --> 13:50.510
address family for ipv4 we go into topology base and then use your variants

294
13:50.510 --> 13:51.760
command right there as

295
13:51.760 --> 13:56.870
opposed to traditional eagrp where you just do it simply in eagrp configuration

296
13:56.870 --> 13:57.520
mode and then for

297
13:57.520 --> 14:01.750
verification if you do a show ip protocols here's the eagrp atom system that's
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

297
13:57.520 --> 14:01.750
verification if you do a show ip protocols here's the eagrp atom system that's

298
14:01.750 --> 14:03.520
running 100 and

299
14:03.520 --> 14:07.670
right here we have the variance specified as to because we configured it that

300
14:07.670 --> 14:08.720
way which allows us

301
14:08.720 --> 14:13.060
to take feasible successors and as long as their metric doesn't exceed twice

302
14:13.060 --> 14:14.240
the metric of the

303
14:14.240 --> 14:17.440
successor route they could also be used in the routing table so up to this

304
14:17.440 --> 14:18.240
point we've had some

305
14:18.240 --> 14:22.960
fun and taking a look at the behaviors and characteristics of eagrp and what it

306
14:22.960 --> 14:24.400
's using to calculate a

307
14:24.400 --> 14:28.760
metric and decide on which route goes or which routes go into the routing table

308
14:28.760 --> 14:29.520
and up to this point

309
14:29.520 --> 14:32.420
you've had a few options you could have clicked the lab to join me and go
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

309
14:29.520 --> 14:32.420
you've had a few options you could have clicked the lab to join me and go

310
14:32.420 --> 14:33.840
through a step by step or

311
14:33.840 --> 14:37.770
if you've waited and want to do it now in the next video i'd like to put you on

312
14:37.770 --> 14:38.880
a hands-on lab so

313
14:38.880 --> 14:42.080
if you've already done the work that's fantastic however if you haven't done

314
14:42.080 --> 14:43.120
the hands-on lab yet

315
14:43.120 --> 14:47.710
here for eagrp in the next video i'd like to present you with some lab tasks so

316
14:47.710 --> 14:48.640
you my friend can get

317
14:48.640 --> 14:53.720
hands-on practice in working with and verifying eagrp so i'll see you in the

318
14:53.720 --> 14:55.280
next video in just a moment