Networking
--
Questions
--
Followers
Top Experts
How to Test EIGRP Load-Balancing
I have configured EIGRP on all routers.
From R1 I can see there are 2 unequal paths to get to 4.4.4.4 loopback on R4, that 's after I used Variance command.
R1#sh ip eigrp topology
EIGRP-IPv4 Topology Table for AS(1)/ID(192.168.13.1)
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status
P 192.168.24.0/24, 1 successors, FD is 30720
via 192.168.12.2 (30720/28160), FastEthernet0/0
P 192.168.34.0/24, 1 successors, FD is 33280
via 192.168.12.2 (33280/30720), FastEthernet0/0
via 192.168.13.3 (261120/28160), FastEthernet0/1
P 192.168.12.0/24, 1 successors, FD is 28160
via Connected, FastEthernet0/0
P 4.4.4.4/32, 2 successors, FD is 158720
via 192.168.12.2 (158720/156160), FastEthernet0/0
via 192.168.13.3 (389120/156160), FastEthernet0/1
P 192.168.13.0/24, 1 successors, FD is 258560
via Connected, FastEthernet0/1
via 192.168.12.2 (35840/33280), FastEthernet0/0
R1#R1#sh ip route eigrp
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, + - replicated route
Gateway of last resort is not set
4.0.0.0/32 is subnetted, 1 subnets
D 4.4.4.4 [90/389120] via 192.168.13.3, 01:04:06, FastEthernet0/1
[90/158720] via 192.168.12.2, 01:04:06, FastEthernet0/0
D 192.168.24.0/24 [90/30720] via 192.168.12.2, 01:04:06, FastEthernet0/0
D 192.168.34.0/24 [90/33280] via 192.168.12.2, 01:04:06, FastEthernet0/0
R1#I tried Traceroute, but realized it will use just one path , even when I use that command over and over :Traceroute 4.4.4.4
R1#traceroute 4.4.4.4
Type escape sequence to abort.
Tracing the route to 4.4.4.4
1 192.168.13.3 16 msec 52 msec 12 msec
2 192.168.34.4 24 msec 28 msec 44 msec
R1#the only time it took the other path through R2, is when I cleared EIGRP neighborship
R1#clear ip eigrp neighbors
it worked just one time though...
I am not sure if  Load-Balancing is working , but I am not using proper command to test, or it is not working...
Any help ?
Thank you
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Since both EIGRP routes are placed in routing table with different cost traffic should be load balanced unequally. But generally, something is wrong with your output, path via 192.168.12.2 should be preferred - since it is path with the lower cost (currently path that is taken is via 192.168.13.3). I guessthat you run into GNS3 bug, try to save configurations and reload lab).
You can also increase number of probes during testing:
traceroute 4.4.4.4 probe 5
You can also increase number of probes during testing:
traceroute 4.4.4.4 probe 5
Sorry Predrag
I was increasing /decreasing the Bandwidth on R1 Fa0/1, Â probably the output of topology and routing table was not at the same moment..
To answer Hemil Aquino, I believe what you area referring to is Fault- Tolerance, which means the feasible successor function will not kick in until the interface going through the Successor is down.
Load-Balancing should alternate between both paths... I could not find the good testing of it
I was increasing /decreasing the Bandwidth on R1 Fa0/1, Â probably the output of topology and routing table was not at the same moment..
To answer Hemil Aquino, I believe what you area referring to is Fault- Tolerance, which means the feasible successor function will not kick in until the interface going through the Successor is down.
Load-Balancing should alternate between both paths... I could not find the good testing of it
I guess the load-balancing works now, but It is an equal Load-Balancing:
R1#traceroute 4.4.4.4
Type escape sequence to abort.
Tracing the route to 4.4.4.4
 1 192.168.12.2 24 msec
  192.168.13.3 16 msec
  192.168.12.2 16 msec
 2 192.168.34.4 24 msec
  192.168.24.4 24 msec
  192.168.34.4 20 msec
R1#
R1#traceroute 4.4.4.4
Type escape sequence to abort.
Tracing the route to 4.4.4.4
 1 192.168.12.2 24 msec
  192.168.13.3 16 msec
  192.168.12.2 16 msec
 2 192.168.34.4 24 msec
  192.168.24.4 24 msec
  192.168.34.4 20 msec
R1#
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Unequal Load-balancing works now too, it is just I had to use  Traceroute  for 8 times , and it will choose one path then I  use it for about 20 times it will choose the other path...the ratio is about 20:8
Cannot find the command that will display the load-balancing ratio
Cannot find the command that will display the load-balancing ratio
probably this is the right command:
R1#sh ip route 4.4.4.4
Routing entry for 4.4.4.4/32
 Known via "eigrp 1", distance 90, metric 158720, type internal
 Redistributing via eigrp 1
 Last update from 192.168.12.2 on FastEthernet0/0, 00:11:29 ago
 Routing Descriptor Blocks:
 * 192.168.13.3, from 192.168.13.3, 00:11:29 ago, via FastEthernet0/1
   Route metric is 158720, traffic share count is 120
   Total delay is 5200 microseconds, minimum bandwidth is 100000 Kbit
   Reliability 255/255, minimum MTU 1500 bytes
   Loading 1/255, Hops 2
  192.168.12.2, from 192.168.12.2, 00:11:29 ago, via FastEthernet0/0
   Route metric is 389120, traffic share count is 49
   Total delay is 5200 microseconds, minimum bandwidth is 10000 Kbit
   Reliability 255/255, minimum MTU 1500 bytes
   Loading 1/255, Hops 2
R1#
Share count through 192.168.13.3 is 120
Share count through 192.168.12.2 is 49
is about 2.45.......Well that  's the math I did to come up with the rounded Variance Value of 3.. but I am not sure why using traceroute to 4.4.4.4   about 8 times it will keep showing as going through 192.168.12.2  before it will show the path through :192.168.13.3 and then use Traceroute 4.4.4.4 about 20 times before I see it change back to the path through  192.168.12.2
R1#sh ip route 4.4.4.4
Routing entry for 4.4.4.4/32
 Known via "eigrp 1", distance 90, metric 158720, type internal
 Redistributing via eigrp 1
 Last update from 192.168.12.2 on FastEthernet0/0, 00:11:29 ago
 Routing Descriptor Blocks:
 * 192.168.13.3, from 192.168.13.3, 00:11:29 ago, via FastEthernet0/1
   Route metric is 158720, traffic share count is 120
   Total delay is 5200 microseconds, minimum bandwidth is 100000 Kbit
   Reliability 255/255, minimum MTU 1500 bytes
   Loading 1/255, Hops 2
  192.168.12.2, from 192.168.12.2, 00:11:29 ago, via FastEthernet0/0
   Route metric is 389120, traffic share count is 49
   Total delay is 5200 microseconds, minimum bandwidth is 10000 Kbit
   Reliability 255/255, minimum MTU 1500 bytes
   Loading 1/255, Hops 2
R1#
Share count through 192.168.13.3 is 120
Share count through 192.168.12.2 is 49
is about 2.45.......Well that  's the math I did to come up with the rounded Variance Value of 3.. but I am not sure why using traceroute to 4.4.4.4   about 8 times it will keep showing as going through 192.168.12.2  before it will show the path through :192.168.13.3 and then use Traceroute 4.4.4.4 about 20 times before I see it change back to the path through  192.168.12.2
though 20/8 = 2.5 Â which is close to almost 2.45 (I picked Variance 3)
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Thank you Guys
You're welcome.
Networking
--
Questions
--
Followers
Top Experts
Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.