ASA 5525 EIGRP is fine and quit working for almost 2 hours.

[mdieken011]

I have an ASA 5525 and a Catalyst 9500 switch that have been exchanging routes using EIGRP for years.  Last night that quit working.  I will include the show eigrp events below.

ASA/act# sh eigrp events

Event information for AS 100:

   1 23:49:10.074 Poison squashed: 10.10.12.14 255.255.255.255 reverse

   2 23:49:10.074 Ignored route, neighbor info: 10.100.10.1 Inside

   3 23:49:10.074 Ignored route, dup routerid ext: 10.100.10.2

   4 23:49:10.074 Poison squashed: 10.10.12.15 255.255.255.255 reverse

   5 23:49:10.074 Ignored route, neighbor info: 10.100.10.1 Inside

   6 23:49:10.074 Ignored route, dup routerid ext: 10.100.10.2

   7 23:49:10.074 Poison squashed: 10.10.12.58 255.255.255.255 reverse

Switch#sh ip eigrp events

Event information for AS 100:

1    23:49:10.191 Poison squashed: 10.202.2.0/24 reverse

2    23:49:10.191 Poison squashed: 10.203.2.0/24 reverse

3    23:49:10.191 Poison squashed: 10.210.7.0/24 reverse

4    23:49:10.191 Poison squashed: 10.218.2.0/24 reverse

5    23:49:10.191 Poison squashed: 10.209.2.0/24 reverse

6    23:49:10.191 Poison squashed: 10.201.71.0/24 reverse

7    23:49:10.191 Poison squashed: 10.201.11.0/24 reverse

8    23:49:10.191 Poison squashed: 10.201.31.0/24 reverse

9    23:49:10.191 Poison squashed: 10.210.2.0/24 reverse

10   23:49:10.187 Poison squashed: 10.10.12.14/32 reverse

Any ideas as to what can caused this?

[MHM Cisco World]

Poison squashed—The router threads a topology table entry as a poison in reply to an update (the router set up for poison reverse). While the router is building the packet that contains the poison reverse, the router realizes that it doesn't need to send it. For example, if the router receives a query for that route from the neighbor, it is currently threaded to poison.

Q is why route is poison in first place? 

Do you use any summary?

MHM

[mdieken011]

Thanks for the reply.  I don't know what could have prompted the poison to begin with.  This has been working flawlessly for years.  All of a sudden it started.  I don't summarize my routes because I have never had a reason to in the past.  I leave them as is normally so I can ensure a specific route is in place and check it.

I do not know why route is poison in the first place.

[MHM Cisco World]

I run lab and check event and also check cisco doc. 
it normal to see these message in event
the two Peer exchange the RIB table and to prevent one to resend update receive from it neighbor this message used.
check below cisco doc. and My lab event

1 10:54:09.563 Poison squashed: 110.0.0.0/24 reverse
2 10:54:09.563 Ignored route, dup routerid int: 1.1.1.1
3 10:54:09.563 Poison squashed: 1.1.1.1/32 reverse
4 10:54:09.563 Ignored route, dup routerid int: 1.1.1.1
5 10:54:09.523 Poison squashed: 100.0.0.0/24 reverse
6 10:54:09.523 Ignored route, dup routerid int: 1.1.1.1
7 10:54:09.523 Poison squashed: 1.1.1.1/32 reverse
8 10:54:09.523 Ignored route, dup routerid int: 1.1.1.1
9 10:54:09.523 Metric set: 2.2.2.2/32 metric(156160)
10 10:54:09.523 Route installing: 2.2.2.2/32 110.0.0.3
11 10:54:09.523 Route installed: 2.2.2.2/32 100.0.0.2
12 10:54:09.523 Route installing: 2.2.2.2/32 100.0.0.2
13 10:54:09.523 FC sat rdbmet/succmet: metric(156160) metric(128256)
14 10:54:09.523 FC sat nh/ndbmet: 100.0.0.2 metric(156160)
15 10:54:09.523 Find FS: 2.2.2.2/32 metric(156160)
16 10:54:09.523 Rcv update met/succmet: metric(158720) metric(156160)
17 10:54:09.523 Rcv update dest/nh: 2.2.2.2/32 110.0.0.3
18 10:54:09.463 Change queue emptied, entries: 2
19 10:54:09.463 Metric set: 120.0.0.0/24 metric(30720)
20 10:54:09.463 Update reason, delay: new if delay(200000000)
21 10:54:09.463 Update sent, RD: 120.0.0.0/24 metric(30720)
22 10:54:09.463 Route installed: 120.0.0.0/24 100.0.0.2
23 10:54:09.463 Route installing: 120.0.0.0/24 100.0.0.2
24 10:54:09.463 Route installed: 120.0.0.0/24 110.0.0.3
25 10:54:09.459 Route installing: 120.0.0.0/24 110.0.0.3
26 10:54:09.459 FC sat rdbmet/succmet: metric(30720) metric(28160)
27 10:54:09.459 FC sat nh/ndbmet: 110.0.0.3 metric(30720)
28 10:54:09.459 Find FS: 120.0.0.0/24 metric(30720)
29 10:54:09.459 Rcv update met/succmet: metric(30720) metric(28160)
30 10:54:09.459 Rcv update dest/nh: 120.0.0.0/24 100.0.0.2
31 10:54:09.459 Metric set: 2.2.2.2/32 metric(156160)
32 10:54:09.459 Update reason, delay: new if delay(Infinity)
33 10:54:09.459 Update sent, RD: 2.2.2.2/32 metric(Infinity)
34 10:54:09.459 Update reason, delay: metric chg delay(Infinity)
35 10:54:09.459 Update sent, RD: 2.2.2.2/32 metric(Infinity)
36 10:54:09.459 Route installed: 2.2.2.2/32 100.0.0.2
37 10:54:09.459 Route installing: 2.2.2.2/32 100.0.0.2
38 10:54:09.459 Find FS: 2.2.2.2/32 metric(Infinity)
39 10:54:09.459 Rcv update met/succmet: metric(156160) metric(128256)
40 10:54:09.459 Rcv update dest/nh: 2.2.2.2/32 100.0.0.2
41 10:54:09.455 Metric set: 2.2.2.2/32 metric(Infinity)
42 10:54:09.343 Change queue emptied, entries: 1
43 10:54:09.343 Metric set: 120.0.0.0/24 metric(30720)
44 10:54:09.343 Update reason, delay: new if delay(Infinity)
45 10:54:09.343 Update sent, RD: 120.0.0.0/24 metric(Infinity)
46 10:54:09.343 Update reason, delay: metric chg delay(Infinity)
47 10:54:09.343 Update sent, RD: 120.0.0.0/24 metric(Infinity)
48 10:54:09.343 Route installed: 120.0.0.0/24 110.0.0.3
49 10:54:09.339 Route installing: 120.0.0.0/24 110.0.0.3
50 10:54:09.339 Find FS: 120.0.0.0/24 metric(Infinity)
51 10:54:09.339 Rcv update met/succmet: metric(30720) metric(28160)
52 10:54:09.339 Rcv update dest/nh: 120.0.0.0/24 110.0.0.3
53 10:54:09.339 Metric set: 120.0.0.0/24 metric(Infinity)
54 10:54:09.307 Rcv peer INIT: 100.0.0.2 FastEthernet0/0
55 10:54:09.243 Rcv peer INIT: 110.0.0.3 FastEthernet1/1
56 10:54:06.703 Conn rt change: 110.0.0.0/24 FastEthernet1/1
57 10:54:06.703 Lost route 1=forceactv: 110.0.0.0/24 0
58 10:54:06.699 Conn rt change: 110.0.0.0/24 FastEthernet1/1
59 10:54:06.699 Conn rt change: 100.0.0.0/24 FastEthernet0/0
60 10:54:06.699 Lost route 1=forceactv: 100.0.0.0/24 0
61 10:54:06.699 Conn rt change: 100.0.0.0/24 FastEthernet0/0
62 10:54:06.699 Conn rt change: 1.1.1.1/32 Loopback0
63 10:54:06.695 Lost route 1=forceactv: 1.1.1.1/32 0
64 10:54:06.695 Conn rt change: 1.1.1.1/32 Loopback0
65 10:54:06.695 Conn rt change: 110.0.0.0/24 FastEthernet1/1
66 10:54:06.695 Lost route 1=forceactv: 110.0.0.0/24 0
67 10:54:06.695 Change queue emptied, entries: 1
68 10:54:06.695 Metric set: 110.0.0.0/24 metric(28160)
69 10:54:06.695 Update reason, delay: new if delay(Infinity)
70 10:54:06.695 Update sent, RD: 110.0.0.0/24 metric(Infinity)
71 10:54:06.695 Update reason, delay: metric chg delay(Infinity)
72 10:54:06.695 Update sent, RD: 110.0.0.0/24 metric(Infinity)
73 10:54:06.695 Route installed: 110.0.0.0/24 0.0.0.0
74 10:54:06.695 Find FS: 110.0.0.0/24 metric(Infinity)
75 10:54:06.695 Rcv update met/succmet: metric(28160) metric(0)
76 10:54:06.695 Rcv update dest/orig: 110.0.0.0/24 Connected
77 10:54:06.691 Metric set: 110.0.0.0/24 metric(Infinity)
78 10:54:06.691 Conn rt change: 110.0.0.0/24 FastEthernet1/1
79 10:54:06.691 Conn rt change: 100.0.0.0/24 FastEthernet0/0
80 10:54:06.691 Lost route 1=forceactv: 100.0.0.0/24 0
81 10:54:06.691 Change queue emptied, entries: 1
82 10:54:06.691 Metric set: 100.0.0.0/24 metric(28160)
83 10:54:06.687 Update reason, delay: new if delay(Infinity)
84 10:54:06.687 Update sent, RD: 100.0.0.0/24 metric(Infinity)
85 10:54:06.687 Update reason, delay: metric chg delay(Infinity)
86 10:54:06.687 Update sent, RD: 100.0.0.0/24 metric(Infinity)
87 10:54:06.687 Route installed: 100.0.0.0/24 0.0.0.0
88 10:54:06.687 Find FS: 100.0.0.0/24 metric(Infinity)
89 10:54:06.687 Rcv update met/succmet: metric(28160) metric(0)
90 10:54:06.687 Rcv update dest/orig: 100.0.0.0/24 Connected
91 10:54:06.687 Metric set: 100.0.0.0/24 metric(Infinity)
92 10:54:06.687 Conn rt change: 100.0.0.0/24 FastEthernet0/0
93 10:54:06.687 Conn rt change: 1.1.1.1/32 Loopback0
94 10:54:06.687 Lost route 1=forceactv: 1.1.1.1/32 0
95 10:54:06.683 Change queue emptied, entries: 1
96 10:54:06.683 Metric set: 1.1.1.1/32 metric(128256)
97 10:54:06.683 Update reason, delay: new if delay(Infinity)
98 10:54:06.683 Update sent, RD: 1.1.1.1/32 metric(Infinity)
99 10:54:06.683 Update reason, delay: metric chg delay(Infinity)
100 10:54:06.683 Update sent, RD: 1.1.1.1/32 metric(Infinity)
101 10:54:06.683 Route installed: 1.1.1.1/32 0.0.0.0
102 10:54:06.683 Find FS: 1.1.1.1/32 metric(Infinity)
103 10:54:06.683 Rcv update met/succmet: metric(128256) metric(0)
104 10:54:06.683 Rcv update dest/orig: 1.1.1.1/32 Connected
105 10:54:06.683 Metric set: 1.1.1.1/32 metric(Infinity)
106 10:54:06.683 Conn rt change: 1.1.1.1/32 Loopback0
107 10:54:06.679 i/f delayed net add: 110.0.0.1 FastEthernet1/1
108 10:54:06.679 i/f delayed net add: 100.0.0.1 FastEthernet0/0
109 10:54:06.679 i/f delayed net add: 1.1.1.1 Loopback0
110 10:54:06.675 i/f delayed net add: 110.0.0.1 FastEthernet1/1
111 10:54:06.667 i/f delayed net add: 100.0.0.1 FastEthernet0/0
112 10:54:06.659 i/f delayed net add: 1.1.1.1 Loopback0

[paul driver]

Hello

---

@mdieken011 wrote:

I have an ASA 5525 and a Catalyst 9500 switch that have been exchanging routes using EIGRP for years.  Last night that quit working. 

Event information for AS 100:
5 23:49:10.074 Ignored route, neighbor info: 10.100.10.1 Inside
6 23:49:10.074 Ignored route, dup routerid ext: 10.100.10.2

---

Rtr seems to be reporting its seeing duplicate RID being advertised, as such this is a form of filtering, as the eigrp rtr will ignore/discard any prefix that was originates from another router with the same router id.