EIGRP having wrong route in routing table

[ramcm.rr]

Hello All,

Here is the output from my router. Why is it having the route with higher metric in its routing table?

Router#sh ip route 10.108.1.96
Routing entry for 10.108.1.96/27
  Known via "eigrp 1", distance 170, metric 26933760, type external
  Redistributing via eigrp 1
  Last update from 10.0.1.96 on FastEthernet1/0, 10:42:36 ago
  Routing Descriptor Blocks:
  * 10.0.1.96, from 10.0.1.96, 10:42:36 ago, via FastEthernet1/0
      Route metric is 26933760, traffic share count is 1
      Total delay is 52100 microseconds, minimum bandwidth is 100 Kbit
      Reliability 255/255, minimum MTU 1476 bytes
      Loading 1/255, Hops 2

Router#sh ip eigrp topology 10.108.1.96 255.255.255.224
IP-EIGRP topology entry for 10.108.1.96/27
  State is Passive, Query origin flag is 1, 1 Successor(s), FD is 10537472
  Routing Descriptor Blocks:
  0.0.0.0, from Redistributed, Send flag is 0x0
      Composite metric is (10537472/0), Route is External
      Vector metric:
        Minimum bandwidth is 256 Kbit
        Total delay is 21000 microseconds
        Reliability is 255/255
        Load is 106/255
        Minimum MTU is 1500
        Hop count is 1
      External data:
        Originating router is 192.168.1.1 (this system)
        AS number of route is 2
        External protocol is EIGRP, external metric is 10537472
        Administrator tag is 0 (0x00000000)
  10.0.1.96 (FastEthernet1/0), from 10.0.1.96, Send flag is 0x0
      Composite metric is (26933760/26931200), Route is External
      Vector metric:
        Minimum bandwidth is 100 Kbit
        Total delay is 52100 microseconds
        Reliability is 255/255
        Load is 1/255
        Minimum MTU is 1476
        Hop count is 2
      External data:
        Originating router is 148.73.1.242
        AS number of route is 2
        External protocol is EIGRP, external metric is 26931200
        Administrator tag is 0 (0x00000000)
IP-EIGRP topology entry for 10.108.1.96/27
  State is Passive, Query origin flag is 1, 1 Successor(s), FD is 10537472
  Routing Descriptor Blocks:
  192.168.1.2 (Serial0/0), from 192.168.1.2, Send flag is 0x0
      Composite metric is (10537472/10025472), Route is External
      Vector metric:
        Minimum bandwidth is 256 Kbit
        Total delay is 21000 microseconds
        Reliability is 255/255
        Load is 106/255
        Minimum MTU is 1500
        Hop count is 1
      External data:
        Originating router is 192.168.1.2
        AS number of route is 0
        External protocol is RIP, external metric is 3
        Administrator tag is 0 (0x00000000)

[Peter Paluch]

Ram,

It seems that you are running two EIGRP processes, and you are redistributing from one process to another. The one from which you are redistributing is the one that is present in the routing table. The second EIGRP process retakes this route with another metric configured in the redistribution command.

What is the configuration of your router? There seem to be lots of routing protocols and processes - EIGRP 1, EIGRP 2, RIP... Quite confusing from what is seen in your output so far.

Best regards,

Peter

[ramcm.rr]

Hi Peter,

Thanks for you reply. I was testing failover of two eigrp routes by changing metrics. I guess it is not the correct way to test.

So I blocked the route being advertised from primary router, backup router routed traffic as expected.

Thanks,

Ram

[Ajay Patel]

Hi Ram,

As you told; Blocking the traffic on Backup router solved issues but it is not good practies to Block Routes learning by backup; in the case of Prymary router fail; you won't be having reachbility for the block routes.

Use Route-map; match the traffic and tag them then manupulate the traffic by incressing or decreasing the metrics; this wouln't create any confusion for routers.

Please let us know how do you want to perform the  failover? which routes should take which path? could you share Network Topology and running configuration so will help us for better understanding the your expected result.

Thank you

Ajay

[ramcm.rr]

Hi Ajay,

I blocked it only to test. When I unblocked it primary route came up  (in the routing table)

Let me explain why changing metrics to test eigrp did not work

Route A (primary route)  has lower metric then Route B ( backup) . To test failover I reduced Route B to have lower metric than Route A,

Route B was installed in the routing table. But when I increased Route B metric to original value, Route A was not in the routing table. Route B with higher metric was still in the routing table.

To rectify it, I had to restart the eigrp process. So apparently changing metrics is NOT the right way to test eigrp.

Thanks,

Ram