"The router threads a

murugananthamamir · ‎05-11-2015

Dear Xperts,

In our network, we are facing frequent drops towards router Say R4, whereas nil drops towards R2 & R3 from R1.

Right now we are in a situation, can't take console & required logs, from R4. Redistribution is existing between BGP & EIGRP as well.

R4's CPU is 40% and the rest of the routers is below 10% approx. During the drops occuring in our network, not facing neighbourship outage in between.

FYI., High-lighted network x.x.204 is the concern R4 incurring drops from R1 router.

Router #sh ip eigrp neighbors detail
EIGRP-IPv4 Neighbors for AS(10)
H   Address                 Interface       Hold Uptime   SRTT   RTO Q Seq
                                            (sec)         (ms)       Cnt Num
2   149.24.155.204          Vl300             14 4w0d      732 5000 0 83
   Version 8.0/2.0, Retrans: 2, Retries: 0, Prefixes: 8
   Topology-ids from peer - 0
1   149.24.155.205          Vl300             11 4w0d        1 1518 0 79
   Version 8.0/2.0, Retrans: 6, Retries: 0, Prefixes: 2
   Topology-ids from peer - 0
0   149.24.155.206          Vl300             14 4w0d        1 2277 0 73
   Version 8.0/2.0, Retrans: 6, Retries: 0, Prefixes: 2
   Topology-ids from peer - 0

EIGRP event logs partial o/p FYR, around 300 entries been attached on further reference,

169 06:00:12.688 Ignored route, inaccessible: 149.24.0.0/16 4294967295
170 06:00:12.688 Ignored route, inaccessible: 147.249.155.0/24 4294967295
171 06:00:12.688 Ignored route, inaccessible: 147.249.153.0/24 4294967295
172 06:00:12.688 Ignored route, inaccessible: 10.148.0.0/16 4294967295
173 06:00:12.688 Ignored route, inaccessible: 10.64.52.0/23 4294967295
174 06:00:12.688 Ignored route, inaccessible: 10.64.48.0/22 4294967295
175 06:00:12.688 Ignored route, inaccessible: 10.64.32.0/20 4294967295
176 06:00:12.688 Ignored route, inaccessible: 10.64.0.0/19 4294967295
177 06:00:12.679 Rcv peer INIT: 149.24.155.204 Vlan300
178 06:00:10.280 Poison squashed: 149.24.155.82/32 reverse
179 06:00:10.280 Poison squashed: 149.24.155.81/32 reverse
180 06:00:08.519 Poison squashed: 149.24.155.208/28 reverse

on top of this EIGRP statistics on your view-point,

Router#sh ip eigrp traffic
EIGRP-IPv4 Traffic Statistics for AS(10)
Hellos sent/received: 3478015/5221346
Updates sent/received: 18/114
Queries sent/received: 22/1
Replies sent/received: 0/28
Acks sent/received: 121/36
SIA-Queries sent/received: 0/0
SIA-Replies sent/received: 0/0
Hello Process ID: 342
PDM Process ID: 304
Socket Queue: 0/2000/4/0 (current/max/highest/drops)
Input Queue: 0/2000/4/0 (current/max/highest/drops)

Plz advise us to overcome this challenge.

Regrds,

Murugan

schaef350 · ‎05-12-2015

"The router threads a topology table entry as a poison in reply to an update received (the router sets up for poison reverse). While the router is building the packet that contains the poison reverse, the router realizes that it does not need to send it. For example, if the router receives a query for the route from the neighbor, it is currently threaded to poison. Thus, it sends the poison squashed message."

From:

http://www.cisco.com/c/en/us/support/docs/ip/enhanced-interior-gateway-routing-protocol-eigrp/13681-eigrpfaq.html#poison

Do you have any split horizon config added to these routers? Please send topology and configs.

Please rate helpful posts!

- Be sure to rate all helpful posts

EIGRP LAN >> drops & disconnection <<