03-07-2019 11:15 AM
I would like to better understand the role of Feasible Successor in EIGRP. I could not find documentation about it.
Thank you for your help
03-07-2019 11:20 AM - edited 03-07-2019 11:22 AM
Hello,
The variance command will not affect routes that do not meet the feasability condition: Lets say you have 4 equal metric routes for a destination using EIGRP, and the destination being 10.0.0.1. This is without using variance at all; all 4 routes just happen to all be equal. They ALL meet the feasibility condition because their reported distance (in bold) is less than the feasible distance 323072.
All these routes are in the routing table by default, load balancing as they are equal metric routes. Are there any routes that don't meet the feasability condition? Well let's see here. Lets issue the show ip eigrp topology all-links command and see
P 10.0.0.1/24, 4 successors, FD is 323072, tag is 13979
via 192.168.41.93 (323072/322816), GigabitEthernet1/13
via 192.168.41.97 (323072/322816), GigabitEthernet1/14
via 192.168.41.221 (323072/322816), GigabitEthernet1/15
via 192.168.41.225 (323072/322816), GigabitEthernet1/16
show ip eigrp topology all-links
#Lines omitted
P 10.0.0.1, 4 successors, FD is 323072, tag is 13979, serno 345876
via 192.168.41.93 (323072/322816), GigabitEthernet1/13
via 192.168.41.97 (323072/322816), GigabitEthernet1/14
via 192.168.41.221 (323072/322816), GigabitEthernet1/15
via 192.168.41.225 (323072/322816), GigabitEthernet1/16
via 192 168.38.130 (323328/323072), Port-channel17
Look, the above route in red does not meet the feasability condition as its reported distance is NOT LESS than the feasable distance. In this case if you wanted to add this route to the routing table as an equal metric route with the variance command, you would first need to modify the metric so that it meets the feasibility condition; either by changing bandwidth or delay, or by using an offset list.
Here, you can check others discussions about:
https://community.cisco.com/t5/networking-documents/eigrp-feasible-successor/ta-p/3156640
https://learningnetwork.cisco.com/thread/35690
Regards
03-07-2019 11:29 AM
Hello,
The variance command will not affect routes that do not meet the feasability condition: Lets say you have 4 equal metric routes for a destination using EIGRP, and the destination being 10.0.0.1. This is without using variance at all; all 4 routes just happen to all be equal. They ALL meet the feasibility condition because their reported distance (in bold) is less than the feasible distance 323072.
All these routes are in the routing table by default, load balancing as they are equal metric routes. Are there any routes that don't meet the feasability condition? Well let's see here. Lets issue the show ip eigrp topology all-links command and see
P 10.0.0.1/24, 4 successors, FD is 323072, tag is 13979
via 192.168.41.93 (323072/322816), GigabitEthernet1/13
via 192.168.41.97 (323072/322816), GigabitEthernet1/14
via 192.168.41.221 (323072/322816), GigabitEthernet1/15
via 192.168.41.225 (323072/322816), GigabitEthernet1/16
show ip eigrp topology all-links
#Lines omitted
P 10.0.0.1, 4 successors, FD is 323072, tag is 13979, serno 345876
via 192.168.41.93 (323072/322816), GigabitEthernet1/13
via 192.168.41.97 (323072/322816), GigabitEthernet1/14
via 192.168.41.221 (323072/322816), GigabitEthernet1/15
via 192.168.41.225 (323072/322816), GigabitEthernet1/16
via 192 168.38.130 (323328/323072), Port-channel17
Look, the above route in red does not meet the feasability condition as its reported distance is NOT LESS than the feasable distance. In this case if you wanted to add this route to the routing table as an equal metric route with the variance command, you would first need to modify the metric so that it meets the feasibility condition; either by changing bandwidth or delay, or by using an offset list.
Here, you can check others discussions about:
https://community.cisco.com/t5/networking-documents/eigrp-feasible-successor/ta-p/3156640
https://learningnetwork.cisco.com/thread/35690
Regards
03-07-2019 11:31 AM
Hello,
The variance command will not affect routes that do not meet the feasability condition: Lets say you have 4 equal metric routes for a destination using EIGRP, and the destination being 10.0.0.1. This is without using variance at all; all 4 routes just happen to all be equal. They ALL meet the feasibility condition because their reported distance (in bold) is less than the feasible distance 323072.
All these routes are in the routing table by default, load balancing as they are equal metric routes. Are there any routes that don't meet the feasability condition? Well let's see here. Lets issue the show ip eigrp topology all-links command and see
P 10.0.0.1/24, 4 successors, FD is 323072, tag is 13979
via 192.168.41.93 (323072/322816), GigabitEthernet1/13
via 192.168.41.97 (323072/322816), GigabitEthernet1/14
via 192.168.41.221 (323072/322816), GigabitEthernet1/15
via 192.168.41.225 (323072/322816), GigabitEthernet1/16
show ip eigrp topology all-links
#Lines omitted
P 10.0.0.1, 4 successors, FD is 323072, tag is 13979, serno 345876
via 192.168.41.93 (323072/322816), GigabitEthernet1/13
via 192.168.41.97 (323072/322816), GigabitEthernet1/14
via 192.168.41.221 (323072/322816), GigabitEthernet1/15
via 192.168.41.225 (323072/322816), GigabitEthernet1/16
via 192 168.38.130 (323328/323072), Port-channel17
Look, the above route in red does not meet the feasability condition as its reported distance is NOT LESS than the feasable distance. In this case if you wanted to add this route to the routing table as an equal metric route with the variance command, you would first need to modify the metric so that it meets the feasibility condition; either by changing bandwidth or delay, or by using an offset list.
Here, you can check others discussions about:
https://community.cisco.com/t5/networking-documents/eigrp-feasible-successor/ta-p/3156640
https://learningnetwork.cisco.com/thread/35690
Regards
Regards
03-07-2019 12:18 PM
Hi @John Ventura ,
Check this:
Another two terms that appear often in the EIGRP world are successor and feasible successor. A successor is the route with the best metric to reach a destination. That route is stored in the routing table. A feasible successor is a backup path to reach that same destination that can be used immediately if the successor route fails. These backup routes are stored in the topology table.
For a route to be chosen as a feasible successor, one condition must be met:
The following example explains the concept of a successor and a feasible successor.
R1 has two paths to reach the subnet 10.0.0.0/24. The path through R2 has the best metric (20) and it is stored in the R1’s routing table. The other route, through R3, is a feasible successor route, because the feasiblility condition has been met (R3’s advertised distance of 15 is less than R1’s feasible distance of 20). R1 stores that route in the topology table. This route can be immediately used if the primary route fails.
I leave the link with the full explanation:
https://study-ccna.com/eigrp-overview/
Also, I commented that there is an interesting event related to EIGRP, in case you have more doubts about this protocol:
https://community.cisco.com/t5/routing/ask-the-expert-eigrp-unveiled/td-p/3811434
Remember to mark the correct answers as solved, as this helps other users with similar doubts.
Regards
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: