Categories > Anime/Manga > Battle Royale
Cisco CCNA Certification Exam Tutorial: Variance And Unequal Cost Load Balancing
0 ReviewsTo victorian house 3d model go the CCNA exam, you've got to understand how to assist IGRP and EIGRP unequal-cost load balancing. May very well not see much IGRP in production networks anymore, but ...
To victorian house 3d model go the CCNA exam, you've got to understand how to assist IGRP and EIGRP unequal-cost load balancing. May very well not see much IGRP in production networks anymore, but you'll see plenty of EIGRP, and part of fine-tuning your EIGRP system is ensuring all routes have been in use while permitting varying bandwidth costs.
Using the variance control may be the easy part - it is getting the metric that's the difficult part with IGRP. With EIGRP, you just try looking in the table and that's it. With IGRP, you have surely got to run a debug to get the right metric.
The check out 3d models architecture 796 3d studio max file max variance command is a multiplier when the value provided with the variance command is multiplied by the metric, it should exceed the higher-cost metric in order for the route to be included.
If that seems complicated, it's not. It is one particular things that seems hard, but isn't. Trust in me!
In this example, R1 has two paths to 172.23.0.0, but is currently using only one. By looking in the Ip Address routing table, we've seen that the metric for network 172.23.0.0 on R1 is 8576. This route goes through the 172.12.123.0 network. There is another good path that uses the 172.12.13.0 system, but is not currently in use.
I 172.23.0.0/16 [100/8576] via 172.12.123.2, 00:00:53, Serial0
IGRP doesn't have a command that displays all good routes to a location, as does EIGRP. The command debug internet protocol address igrp transactions will show the present full of the routes using the 512 KBPS way.
R1#debug ip igrp transactions
IGRP protocol debugging is on
19:17:51: IGRP: broadcasting request on Loopback0
19:17:51: IGRP: transmission request on Serial0
19:17:51: IGRP: broadcasting request on Serial1
On Serial1 19:17:51: IGRP: obtained update from 172.12.13.3
19:17:51: subnet 172.12.13.0, full 23531 (neighbor 21531)
19:17:51: subnet 172.12.123.0, full 23531 (friend 8476)
19:17:51: system 1.0.0.0, metric 24031 (neighbor 8976)
19:17:51: community 2.0.0.0, full 22131 (friend 1600)
19:17:51: network 3.0.0.0, metric 22031 (neighbor 501)
19:17:51: system 172.23.0.0, metric 21631 (neighbor 1100)
R1( config )#router igrp 1
R1( config-router )#variance 3
R1#show internet protocol address route 172.23.0.0
Routing entry for 172.23.0.0/16
Known via "igrp 1", range 100, metric 8576
Redistributing via igrp 1
Marketed by igrp 1 (home started)
Last update from 172.12.123.2 on Serial0, 00:00:01 before
Routing Descriptor Blocks:
* 172.12.13.3, from 172.12.13.3, 00:00:20 ago, via Serial1
Route metric is 21631, traffic share count is 1
Total delay is 21000 microseconds, minimum bandwidth is 512 Kbit
Stability 255/255, minimal MTU 1500 bytes
Loading 1/255, Hops 0
172.12.123.3, from 172.12.123.3, 00:00:20 ago, via Serial0
Route metric is 8576, traffic share count is 3
Complete delay is 21000 microseconds, minimum bandwidth is 1544 Kbit
Stability 255/255, minimal MTU 1500 bytes
Packing 1/255, Hops 0
172.12.123.2, from 172.12.123.2, 00:00:01 before, via Serial0
Route metric is 8576, traffic share count is 3
Total delay is 21000 microseconds, minimum bandwidth is 1544 Kbit
Reliability 255/255, minimal MTU 1500 bytes
Packing 1/255, Hops 0
The metric for 172.23.0.0 through the direct 3d models gmc sierra regular cab standard box 2011 3d studio 3ds relationship is 21631. A variance of 3 implies that any course with a metric significantly less than the best metric multiplied by the variance (in this instance, 8576 x 3 = 25728) is going to be entered into the routing table. R1 now has three unequal-cost routes to 172.23.0.0 in its routing table, and place will be taken by load balancing.
IGRP unequal-cost load balancing requires some practice, but as you can see, when you obtain the metric it's simple to use. Just be sure you learn how to get that full!
Using the variance control may be the easy part - it is getting the metric that's the difficult part with IGRP. With EIGRP, you just try looking in the table and that's it. With IGRP, you have surely got to run a debug to get the right metric.
The check out 3d models architecture 796 3d studio max file max variance command is a multiplier when the value provided with the variance command is multiplied by the metric, it should exceed the higher-cost metric in order for the route to be included.
If that seems complicated, it's not. It is one particular things that seems hard, but isn't. Trust in me!
In this example, R1 has two paths to 172.23.0.0, but is currently using only one. By looking in the Ip Address routing table, we've seen that the metric for network 172.23.0.0 on R1 is 8576. This route goes through the 172.12.123.0 network. There is another good path that uses the 172.12.13.0 system, but is not currently in use.
I 172.23.0.0/16 [100/8576] via 172.12.123.2, 00:00:53, Serial0
IGRP doesn't have a command that displays all good routes to a location, as does EIGRP. The command debug internet protocol address igrp transactions will show the present full of the routes using the 512 KBPS way.
R1#debug ip igrp transactions
IGRP protocol debugging is on
19:17:51: IGRP: broadcasting request on Loopback0
19:17:51: IGRP: transmission request on Serial0
19:17:51: IGRP: broadcasting request on Serial1
On Serial1 19:17:51: IGRP: obtained update from 172.12.13.3
19:17:51: subnet 172.12.13.0, full 23531 (neighbor 21531)
19:17:51: subnet 172.12.123.0, full 23531 (friend 8476)
19:17:51: system 1.0.0.0, metric 24031 (neighbor 8976)
19:17:51: community 2.0.0.0, full 22131 (friend 1600)
19:17:51: network 3.0.0.0, metric 22031 (neighbor 501)
19:17:51: system 172.23.0.0, metric 21631 (neighbor 1100)
R1( config )#router igrp 1
R1( config-router )#variance 3
R1#show internet protocol address route 172.23.0.0
Routing entry for 172.23.0.0/16
Known via "igrp 1", range 100, metric 8576
Redistributing via igrp 1
Marketed by igrp 1 (home started)
Last update from 172.12.123.2 on Serial0, 00:00:01 before
Routing Descriptor Blocks:
* 172.12.13.3, from 172.12.13.3, 00:00:20 ago, via Serial1
Route metric is 21631, traffic share count is 1
Total delay is 21000 microseconds, minimum bandwidth is 512 Kbit
Stability 255/255, minimal MTU 1500 bytes
Loading 1/255, Hops 0
172.12.123.3, from 172.12.123.3, 00:00:20 ago, via Serial0
Route metric is 8576, traffic share count is 3
Complete delay is 21000 microseconds, minimum bandwidth is 1544 Kbit
Stability 255/255, minimal MTU 1500 bytes
Packing 1/255, Hops 0
172.12.123.2, from 172.12.123.2, 00:00:01 before, via Serial0
Route metric is 8576, traffic share count is 3
Total delay is 21000 microseconds, minimum bandwidth is 1544 Kbit
Reliability 255/255, minimal MTU 1500 bytes
Packing 1/255, Hops 0
The metric for 172.23.0.0 through the direct 3d models gmc sierra regular cab standard box 2011 3d studio 3ds relationship is 21631. A variance of 3 implies that any course with a metric significantly less than the best metric multiplied by the variance (in this instance, 8576 x 3 = 25728) is going to be entered into the routing table. R1 now has three unequal-cost routes to 172.23.0.0 in its routing table, and place will be taken by load balancing.
IGRP unequal-cost load balancing requires some practice, but as you can see, when you obtain the metric it's simple to use. Just be sure you learn how to get that full!
Log in to rate and review this story