EIGRP AD manipulation

[noliveira]

Hi all,

The below route for 192.168.2.0 is learned from two sources, one external eigrp and second internal eigrp with distance changed to 171.
When I clear the route with distance 171 the one learned from 10.0.0.2 with distance 170 takes over and stays in the routing table but if I flap the one learned from 10.0.0.2 with distance 170 it never takes over route with distance 171.

Any ideas why?

LNS5(config-router)#do sh ip route 192.168.2.0
Routing entry for 192.168.2.0/24
Known via "eigrp 115", distance 170, metric 53760
Tag 2755, type external
Redistributing via eigrp 115
Last update from 10.0.0.2 on FastEthernet1/0, 00:05:48 ago
Routing Descriptor Blocks:
* 10.0.0.2, from 10.0.0.2, 00:05:48 ago, via FastEthernet1/0
Route metric is 53760, traffic share count is 1
Total delay is 1100 microseconds, minimum bandwidth is 100000 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 100/255, Hops 1
Route tag 2755

LNS5(config-router)#do sh ip route 192.168.2.0
Routing entry for 192.168.2.0/24
Known via "eigrp 115", distance 171, metric 293120, type internal
Redistributing via eigrp 115
Last update from 172.16.0.1 on FastEthernet0/0, 00:04:19 ago
Routing Descriptor Blocks:
* 172.16.0.1, from 172.16.0.1, 00:04:19 ago, via FastEthernet0/0
Route metric is 293120, traffic share count is 1
Total delay is 5200 microseconds, minimum bandwidth is 16000 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 2

Many thanks

[Deepak Kumar]

Hi,

Can you share some more details as EIGRP configuration, EIGRP routers, topology details with us?

[paul driver]

Hello

---

@noliveira wrote:

Hi all,

The below route for 192.168.2.0 is learned from two sources, one external eigrp and second internal eigrp with distance changed to 171.
When I clear the route with distance 171 the one learned from 10.0.0.2 with distance 170 takes over and stays in the routing table but if I flap the one learned from 10.0.0.2 with distance 170 it never takes over route with distance 171.

---

It sounds like the route is "stuck in active"  when you failover with the flapping of the interface.

May I ask how long did you wait for convergence?  The SIA timer defaults to 3mins(180 seconds) If you had waited most probably you would have seen the primary route re-populated because the neighbor of the alternative route would reset.
When you failover again can you post the following command:
sh ip eigrp topology active

[Georg Pauwen]

Hello,

on a side note, if your IOS supports it, try and configure the fast-reroute feature:

LNS5(config)#router eigrp LNS
LNS5(config-router)#address-family ipv4 unicast autonomous-system 115
LNS5(config-router-af)#topology base
LNS5(config-router-af-topology)#fast-reroute per-prefix all