08-07-2009 02:20 PM - edited 03-06-2019 07:09 AM
Scenario: Point-to-point WAN connection between two EIGRP routers. Wan link is taking excessive errors to the point where EIGRP neighbor flaps but link itself does not i.e. line protocol remains up.
Dampening does not help in this case as link itself doesn't flap. Connectivity, however, is intermittent because of EIGRP neighbor flaps. UDP traffic is hardest hit.
Question: Is there a way to take an interface out of action for a period of time (like dampening) based solely on that interface exceeding some predefined error threshold versus it actually flapping? Alternatively, is there a dampening-type feature in EIGRP (beyond the hold timer) that removes routes for a period of time for a neighbor that is flapping?
08-08-2009 07:43 AM
Not that I'm aware of. Generally to help with flapping, you'd use summary routes. Of course, this would only keep the routes that are in the remote routing tables from dropping out of the table and wouldn't do anything for your neighbor relationships. Is this what you're looking for?
HTH,
John
08-10-2009 12:31 PM
Thanks, John. As you said, summary routes don't help with the intermittent connectivity on the router with the serial interface taking the errors. Looking for a way to take that specific interface out of action until the circuit errors/EIGRP neighbor flaps have stabilized much like IP event dampening would do if the interface itself was flapping.
08-10-2009 01:17 PM
Depending on the IOS you are using, there is a feature called EEM that may be able to help:
http://www.cisco.com/en/US/products/ps6815/products_ios_protocol_group_home.html
HTH,
__
Edison.
08-10-2009 02:38 PM
Thanks, Edison. At first glance, that does look very promising! Will investigate further. Appreciate the pointer...
08-11-2009 08:55 AM
If you have any questions, or require help designing your EEM policy, post your question to the Network Management forum. There is also a good repository for sample EEM policies at http://www.cisco.com/go/ciscobeyond/ .
08-28-2009 06:46 AM
EEM did the trick! We created a policy that automatically makes an interface EIGRP passive (and sends an SNMP trap) when certain interface error counters exceed thresholds. Thanks again!
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: