[c-nsp] Routing around errors

Mack McBride mack.mcbride at viawest.com
Mon Dec 12 11:34:29 EST 2011

EEM scripts are probably the easiest to do on most Cisco platforms.
BFD falls under the timers category.
I think most people use alerts and manual intervention as this isn't
a problem most people want to live with.  Most people try to fix the
error issue in a semi-permanent manner.


-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Geoffrey Pendery
Sent: Friday, December 09, 2011 1:16 PM
To: Cisco-nsp
Subject: [c-nsp] Routing around errors

We've seen an old nuisance issue becoming more prevalent lately - at dual-homed sites one of the circuits will run errors, but not bad enough to drop the routing protocol neighbor (OSPF in our case).

So a site with one good circuit and one error-heavy circuit will continue to route traffic over the circuit with errors.  I'm curious what solutions are prevalent out there, anybody want to weigh in?

Tune the hellos tight enough in the hopes of dropping the neighbors?
Alerts from monitoring system followed by manual intervention?
EEM scripts checking the counters?

cisco-nsp mailing list  cisco-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

More information about the cisco-nsp mailing list