EIGRP Issue Not Accepting Routes from Neighbor

[bssmith10]

I have an issue I am trying to understand with EIGRP not accepting or not using routes advertised from an EIGRP neighbor.  Router A is directly connected to Router B, and both have established eigrp neighbor relationship with one another.  When displaying IP PROTOCOL, Router A does not list Router B as a Routing Information Source, but Router B does show Router A as a Routing Information Resource.  Router B has 5 directly connected networks it is advertising to Router A, but Router A will not put the networks in it's routing table, nor are they in the topology table.  What would cause this?  Below are snipets from the two routers:

Router A

interface Multilink203386
ip address 10.250.241.66 255.255.255.252
ip route-cache flow
delay 20
ppp multilink
ppp multilink group 203386
max-reserved-bandwidth 100
service-policy output UDN-EDGE

!

router eigrp 2013
network 10.0.0.0
auto-summary

!

IP-EIGRP neighbors for process 2013
H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
                                            (sec)         (ms)       Cnt Num
7   10.250.241.65           Mu203386          12 14:14:54    1   200  0  1532
6   10.250.170.154          Mu205680          12 6w3d        3   200  0  83199
4   10.250.170.106          Se1/3:0           13 6w3d        6   200  0  584572
5   10.250.170.114          Mu204840          14 10w1d       1   200  0  1505421
1   10.250.100.93           Se6/1             11 14w3d       1   200  0  4207627
8   10.250.170.217          Hs5/0             11 14w4d       5   200  0  346884
0   10.250.170.202          Se6/0             12 15w2d       1   200  0  2246571
2   10.250.110.53           Se3/0             11 17w5d       1   200  0  5440745
3   10.250.170.133          Se3/1             10 40w2d       1   200  0  2682260

!

sh ip protocols

Routing Information Sources:
    Gateway         Distance      Last Update
    10.250.170.114        90      00:10:58
    10.250.170.106        90      00:10:58
    10.250.170.217        90      00:10:58
    10.250.170.202        90      00:10:58
    10.250.110.53         90      00:10:58
    10.250.170.154        90      00:10:58
    10.250.100.93         90      00:10:58
    10.250.170.150        90      10w4d
    10.250.170.133        90      00:10:58

Router B

interface Multilink203386
ip address 10.250.241.65 255.255.255.252
delay 20
ppp multilink
ppp multilink group 203386
max-reserved-bandwidth 100
service-policy output UDN-EDGE

!

router eigrp 2013
network 10.0.0.0
auto-summary

!

IP-EIGRP neighbors for process 2013
H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
                                            (sec)         (ms)       Cnt Num
5   10.168.1.10             Gi1/0.300         13 14:20:02    1   200  0  61786
4   10.250.130.69           Se0/0/0:0         12 14:20:02    4   200  0  531447
3   10.250.241.66           Mu203386          14 14:20:02    1   200  0  3056950
2   10.168.1.11             Gi1/0.300         13 14:20:02    1   200  0  61189
1   10.168.1.9              Gi1/0.300         10 14:20:02    2   200  0  61342
0   10.168.1.3              Gi1/0.300         13 14:20:02    1   200  0  53499

!

sh ip protocols

Routing Information Sources:
    Gateway         Distance      Last Update
    10.250.130.69         90      00:01:49
    10.250.241.66         90      00:01:49
    10.168.1.3            90      00:01:50
    10.168.1.11           90      00:01:50
    10.168.1.10           90      00:01:50
    10.168.1.9            90      00:01:50

[bssmith10]

show output of ip protocols is in my original post.

[Richard Burts]

Your original post contained highly abreviated output from show ip protocol. I would like to see the complete output of show ip protocol.

And as I think about it I would also ask that you post the output of show ip eigrp neighbor detail from both routers.

HTH

Rick

[bssmith10]

Below are the ip porotocols and neighbor details you asked for.  Last night I tried to force Router A to accept the routes from Router B by using a distribution-list on Router B's other outbound interface to stop one of the internal routes (10.168.2.253/32).  Router A lost the route to that network but still would not install the route from Router B.  Wonder if I am looking at a bug.

Router A

sh ip proto
Routing Protocol is "eigrp 2013"
  Outgoing update filter list for all interfaces is not set
  Incoming update filter list for all interfaces is not set
  Default networks flagged in outgoing updates
  Default networks accepted from incoming updates
  EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
  EIGRP maximum hopcount 100
  EIGRP maximum metric variance 1
  Redistributing: eigrp 2013
  EIGRP NSF-aware route hold timer is 240s
  Automatic network summarization is in effect
  Maximum path: 4
  Routing for Networks:
    10.0.0.0
  Routing Information Sources:
    Gateway         Distance      Last Update
    10.250.170.114        90      00:20:16
    10.250.170.106        90      00:20:15
    10.250.170.217        90      00:20:15
    10.250.170.202        90      00:20:16
    10.250.110.53         90      00:20:15
    10.250.170.154        90      00:20:16
    10.250.100.93         90      00:20:15
    10.250.170.150        90      10w5d
    10.250.170.133        90      00:20:15
  Distance: internal 90 external 170

!

sh ip eigrp nei det
IP-EIGRP neighbors for process 2013
H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
                                            (sec)         (ms)       Cnt Num
7   10.250.241.65           Mu203386          12 17:40:57    1   200  0  4679
   Version 12.4/1.2, Retrans: 0, Retries: 0
6   10.250.170.154          Mu205680          13 6w4d        1   200  0  84450
   Version 12.4/1.2, Retrans: 1, Retries: 0, Prefixes: 37
4   10.250.170.106          Se1/3:0           11 6w4d        6   200  0  586698
   Version 12.4/1.2, Retrans: 0, Retries: 0, Prefixes: 2125
5   10.250.170.114          Mu204840          11 10w2d       2   200  0  1507185
   Version 12.4/1.2, Retrans: 15, Retries: 0, Prefixes: 36
1   10.250.100.93           Se6/1             12 14w4d       1   200  0  4213915
   Version 12.2/1.2, Retrans: 3, Retries: 0, Prefixes: 1988
8   10.250.170.217          Hs5/0             12 14w5d       5   200  0  349231
   Version 12.2/1.2, Retrans: 4, Retries: 0, Prefixes: 1071
0   10.250.170.202          Se6/0             10 15w3d       1   200  0  2249060
   Version 12.4/1.2, Retrans: 5, Retries: 0, Prefixes: 40
2   10.250.110.53           Se3/0             13 17w6d       1   200  0  5447192
   Version 12.2/1.2, Retrans: 1, Retries: 0, Prefixes: 1999
3   10.250.170.133          Se3/1             13 40w3d       1   200  0  2685439
   Version 12.4/1.2, Retrans: 119, Retries: 0, Prefixes: 2005

Router B

sh ip prot
Routing Protocol is "eigrp 2013"
  Outgoing update filter list for all interfaces is not set
  Incoming update filter list for all interfaces is not set
  Default networks flagged in outgoing updates
  Default networks accepted from incoming updates
  EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
  EIGRP maximum hopcount 100
  EIGRP maximum metric variance 1
  Redistributing: eigrp 2013
  EIGRP NSF-aware route hold timer is 240s
  Automatic network summarization is in effect
  Maximum path: 4
  Routing for Networks:
    10.0.0.0
  Passive Interface(s):
    GigabitEthernet0/0
    GigabitEthernet0/1
    Serial0/0/1:0
    Serial0/1/0:0
    GigabitEthernet1/0
    GigabitEthernet1/0.50
    GigabitEthernet1/0.66
    GigabitEthernet1/0.298
    Loopback256
    VoIP-Null0
  Routing Information Sources:
    Gateway         Distance      Last Update
    10.250.130.69         90      00:21:16
    10.250.241.66         90      00:21:16
    10.168.1.3            90      00:21:16
    10.168.1.11           90      00:21:16
    10.168.1.10           90      00:21:16
    10.168.1.9            90      00:21:16
  Distance: internal 90 external 170

!

sh ip eigrp nei det
IP-EIGRP neighbors for process 2013
H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
                                            (sec)         (ms)       Cnt Num
3   10.250.241.66           Mu203386          13 17:41:58    1   200  0  3060402
   Version 12.4/1.2, Retrans: 0, Retries: 0, Prefixes: 2122
5   10.168.1.3              Gi1/0.300         10 18:13:11    1   200  0  894
   Version 12.4/1.2, Retrans: 2, Retries: 0, Prefixes: 5
0   10.168.1.10             Gi1/0.300         14 18:13:15    1   200  0  968
   Version 12.4/1.2, Retrans: 2, Retries: 0, Prefixes: 1
4   10.250.130.69           Se0/0/0:0         11 1d13h       1   200  0  533773
   Restart time 13:28:08
   Version 12.4/1.2, Retrans: 0, Retries: 0, Prefixes: 2112
2   10.168.1.11             Gi1/0.300         10 1d13h       1   200  0  62585
   Version 12.4/1.2, Retrans: 6, Retries: 0, Prefixes: 1
1   10.168.1.9              Gi1/0.300         14 1d13h       2   200  0  62744
   Version 12.4/1.2, Retrans: 7, Retries: 0, Prefixes: 1

[Richard Burts]

Thanks for the additional information. I do not see anything that explains why the problem is happening.

I do not know if another attempt to clear the neighbor and then show ip eigrp event trying to get the display of events at the moment of the clearing would show anything useful. But it might be worth a try.

I would also suggest that it might be worth doing an interface shutdown/no shutdown on the multilink on router A. I have seen some situations where a routing protocol got confused or otherwise out of sync with its neighbor and a shut/no shut cleared it up. And the ultimate extension of that would be to schedule a reload of the router.

Since we are not making good progress in resolving this it might also be time to be thinking about opening a Cisco TAC case. Are these routers covered under maintenance?

HTH

Rick

[bssmith10]

I did open a TAC earlier today.  At this point I am going to wait for Cisco to respond.  Rebooting of the router is going to require an outage request, scheduled two weeks out.

[Richard Burts]

I recognize that planning for a reload may require planning and effort (and administrative overhead) which produce delay. I only lay it out as one of the possibilities to consider.

Opening a case with TAC was a good thing. When you get a response or when you have found a solution to the problem please post back to the forum and update us. We would very much like to know how this turns out.

HTH

Rick

[bssmith10]

I will definately update the forum when the solution is found.  Appreciate your time

on this.

[bssmith10]

The problem has been resolved, though I still don't know what caused it.  I pulled one of the t1 from the ppp link, gave it an ip address, and established an eigrp neighbor relation over the link.  This immediately saw proper routing as it now had a better metric.  I then blew away the mlppp configuration and rebuilt it.  Once I removed the ip address from the t1 and put it back into the ppp link, we saw Router A accepting routes from Router B.

[Richard Burts · Accepted solution]

I am glad that you have got the problem resolved. Thanks for posting back to the forum about it. Perhaps you could mark the question as solved. This would benefit other people who might read the thread to find out about the problem and about its solution.

Your solution of removing and rebuilding the multilink configuration is a stronger action but similar to my suggestion about interface shutdown/no shutdown. As I commented in a previous post I have seen situations where a routing protocol got confused or out of sync about a neighbor (sometimes it seems related to a configuration change made and then removed where the protocol seems to be remembering the change even though it is no longer in the running config, and sometimes we never had a clue what caused it) and terminating and rebuilding the neighbor relationship would solve the issue.

So congratulations on getting your problem resolved.

HTH

Rick