If all you need is to track whether you can ping the directly connected IP address and react on the tracked object "down" status, you can use EEM with the "event track X state up|down" trigger.
See the "Not so very static routes" section in this article http://www.nil.com/ipcorner/SmallSiteMultiHoming/ for the SLA and tracking object configuration. The "Monitoring reliable static routing" section in the same article has the EEM examples. If you happen to be running EIGRP on the link (as your message subject would indicate), you can use syslog event detector in EEM to detect when the EIGRP neighbor goes down. EEM is also able to generate SNMP traps if that's what you prefer to receive. If you need more EEM sample code (for example, how to send an e-mail), check my EEM posts (http://blog.ioshints.info/search/label/EEM) or EEM sample scripts in our wiki (http://wiki.nil.com/Category:EEM). Hope this helps Ivan http://www.ioshints.info/about http://blog.ioshints.info/ > -----Original Message----- > From: Ryan Hughes [mailto:[email protected]] > Sent: Thursday, March 26, 2009 5:36 AM > To: [email protected] > Subject: [c-nsp] EIGRP Neighbor tracking > > Hi, > > Just wondering if anyone on list has run into issues where > their routed Metro-E links will sometimes stay up as the mux > isn't properly downing the interface ( cheap gear without > interface tracking per se) when the circuit goes down. > Pinging the interface doesn't really apply in this situation > as there is routed dark fiber links for backup connectivity. > I was thinking along the lines of an EEM script to source > pings from the connected interface and see if its up and send > an SNMP but I haven't had time to script it. I really don't > need to accomlish anything fancy - just an alarm so the NOC > can see it and report it to us. > > Researching the SNMP MIB but there didn't seem to be anything > available. I had run into this issue in the past but I was > doing BGP over the link which obviously offers the neighbor > down snmp trap.Honestly, I'd prefer to have the provider > resolve the issue on their gear but given the aggressive > pricing of the circuit I'm not sure I have much recourse. > > Appreciate the feedback. > > Ryan > > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
