I am not familiar with failover in Eigrp... help please....
EIGRP Variance Traffic Engineering
Scenario
You are the senior network engineer for a company specialized in 80's pop-music. The network is experiencing congestion and you want to use one of the WAN links to share the bandwidth so the load on the main Fast Ethernet link will decrease....let's boogy!
Goal:
- All IP addresses have been preconfigured as specified in the topology picture.
- Configure EIGRP on all routers, disable auto-summary. Achieve full connectivity.
- Change the EIGRP metrics so only delay is being used for the calculations.
- Change the delay on every interface (including the loopback) to 300usec
- If you send a ping from router Jermaine to the loopback of router Michael it should use the link to router Jackie. (succesor route)
- Change the delays on the routers so the link between Jermaine and Tito becomes a feasible succesor route to reach the loopback.
- Change the delays so traffic will be sent in a 1:5 ratio. Use the "show ip route 3.3.3.0" command to check this.
IOS:
c3640-jk9s-mz.124-16.bin
Topology:
Video Solution:
You need to register to download the GNS3 Topology File. (Registration is Free!)
Only registered users can write comments!
Comments (9)
-
ReneMolenaar 2011-01-06 15:54:07EIGRP failover isn't something i can quickly explain in a few lines and at this moment i don't have a video for it...
I'd recommend to read this Cisco article which explains it pretty well:
http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080093f07.shtml
Rene
-
kumar981 2011-01-06 19:20:03Thanks Rene... wrong lab.... this question was for the Maximum Path & Variance lab of EIGRP...
-
jtmajorx 2011-01-27 15:39:12Any advice on this line?
"Change the delays so traffic will be sent in a 1:5 ratio. Use the "show ip route 3.3.3.0" command to check this."
-
aaaa2209 2011-04-25 01:09:09Hello Jon,
I did not successfully finish the line. But I think we need to change the delay so the two delay ratio in 1:5. We also need to use variance command for load balancing.
Also the command show ip eigrp topology ip/mask might be useful in this part.
There is a useful link for this lab : http://www.cisco.com/en/US/docs/ios/12_0/np1/command/reference/1reigrp.htmlThanks Rene for the lab. I learn a lot.
-
amitesh 2011-06-24 08:15:06I completed the lab successfully. It showed up on the ip route cmd too. However i wasn't able to verify it through pings. Technically, R3 should receive ICMP from both exit ints of R1: 192.168.12.1 and 14.1. But this is not the case.
After doing some digging on the cisco website, it seemed the culprit was ip cef, which is enabled by default. cef, by default does per destination balancing. SO i created one more loopback int on R3.
same issue: ping from R1 to both destinations on R3 went through only one interface:no load balancing.
Next i tried changing int behavior on R1 by going to both ints of R1 and did 'ip load-sharing per-packet'. still , R1 was sending every packet (almost 200 count) through 192.168.12.1 interface.Would appreciate anyone's help on this.
-
ReneMolenaar 2011-06-24 09:41:31
Hi Pintu,
I don't have the answer on this one right now, hopefully in two weeks I can start recording the EIGRP videos and then i'll find out...i'll be back!
-
Ollie 2011-07-21 18:06:49Which link has x5 its not too clear ? When variance was 1 i got lovely results when the total path delay equaled each other load balancing came on otherwise >90 delay sent the traffic via Tito as expected. Balancing the traffic was sticky...eventually got perfect 1:5 at #delay 2580 (total delay 31700 usec) on f1/0.
-
ReneMolenaar 2011-07-21 23:08:17
The trick to this lab is:
1. Make sure the second path becomes a feasible successor.
2. Increase the variance so it shows up in the routing table.
3. Change the delays so you get the correct traffic ratio without breaking the feasible successor rule...use "show ip route " to check it.In my video I got roughly a 1:5 ratio, your delay 2580 sounds good
