SNMP link up automation
2014-07-23 19:27:40 GMT
I am sorry if this is a repost or worded poorly.
We currently have an implementation of ONMS version 1.8.1 it was installed some time ago by and employee who is no longer with us and there is little to no documentation on the system. I finally have the time to work on a reinstall of the system. I am not going to upgrade as I think that he wrote a bunch of customizations to the system and if it breaks I have nothing to really fall back on.
I have some cisco 6500s and 7200s that I have that I am testing this new implementation on. I have created the requisition groups and added one of the devices to this group. I have a policy that removes Null and admin down interfaces that I am only dealing with interfaces that are actually in service.
We on the 7200’s a bunch of serial interfaces some of them have IP addresses others do not (members of multilink). I have the device send linkup/linkdown traps to the ONMS box that way I do not have to rely on ICMP. The problem with ICMP is it will not tell me when a link in a multilink bundle has gone down.
I see the traps coming and I have created a notification for when a line goes down. The issue I am having now is that when the up trap comes in the notification is not cleared. From what I can fathom out about automations is that I cannot use the %params% in the event to identify the specific interface notice and auto acknowledge it.
I edited the notification to so that the numericmsg field has the nodeid and the %params[# <at> ]% but when it comes to auto acknowledging based on that it seems that that data has not yet been created in the database to match on that field.
I have been looking at the translations to see if the translations can change the interface parameter on the even to be the interface name vs the IP of the device sending the trap.
I get the feeling this is something very simple that an NMS system should do and I either overcomplicating the matter.
The end result of this is I want to make sure that if a line just flaps that the notification will be sent and then when it comes back suddenly the notification is auto-acknowledged and the RESOLVED email is sent.
This way I will only escalate the line down to my support team if it has been down for more than a certain time. Also if it is after hours I can change the parameters so that there is a higher tolerance for a downed lines and the afterhours team can be notified on a different schedule.
Right now I have the link down and the link up notifications in my outstanding notifications.
Any help on this issue will be greatly appreciated. (sorry if I rambled)
------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds
_______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-discuss mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-discuss