Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
automatic email for critical alarms
- Thread starter novak
- Start date
moonsdarkside
Technical User
novak,
Please find below what I provided to the above thread. While it doesn't specifically address your question, its content should be helpful. The post is as follows:
Do you have an NMS messaging tool (like TelAlert)? If so don't read all the crap I'm talking about below this paragraph. You should be able to find an NNM SNMP trap that notifies of new objects that can be piped to TelAlert for the purpose of emailing and/or paging. And even if you don't have TelAlert, there may be some way of executing a command line mail program from the trap's “automatic action” section that allows you to do this.
With NNM, there are buckets of ways of achieving what you want to do. If you have auto discovery enabled (you'll find that you are able to configure the interval that NNM looks for new devices), then there are numerous binaries you can run that will give you visibility of new "objects" discovered. One that comes to mind for me is "/opt/OV/bin/ovobjprint". This may be an OVO binary, but I believe it comes with NNM. Running ovobjprint from the command line will print to standard output a list of all objects (and certain attributes associated with these objects) currently known by your NNM instance. I have written many scripts using ovobjprint for the purpose of generating non-standard reports. However, for your purposes the aim would be to run ovobjprint at a configured interval that is sync with your auto discovery interval. I would write a script (most likely in PERL) that records all of your known objects to a file that gets appended when a new object is discovered. The script would write to email a list of the new objects identified.
The real value of writing a script to do this is a function of greater control over when emails get sent and what will be included in the content of the emails sent. If you message (by that I mean email or page) a customer each time a new object is identified, you run the risk of someone getting a bushel of single messages each representing the discovery of one or maybe two new objects. Some of these objects may not even be important to your end customer (like interfaces on a switch). So think about it. If you want, I'll send you one of the scripts I've written that uses the output of "ovobjprint".
Cheers
Larry Moon
Please find below what I provided to the above thread. While it doesn't specifically address your question, its content should be helpful. The post is as follows:
Do you have an NMS messaging tool (like TelAlert)? If so don't read all the crap I'm talking about below this paragraph. You should be able to find an NNM SNMP trap that notifies of new objects that can be piped to TelAlert for the purpose of emailing and/or paging. And even if you don't have TelAlert, there may be some way of executing a command line mail program from the trap's “automatic action” section that allows you to do this.
With NNM, there are buckets of ways of achieving what you want to do. If you have auto discovery enabled (you'll find that you are able to configure the interval that NNM looks for new devices), then there are numerous binaries you can run that will give you visibility of new "objects" discovered. One that comes to mind for me is "/opt/OV/bin/ovobjprint". This may be an OVO binary, but I believe it comes with NNM. Running ovobjprint from the command line will print to standard output a list of all objects (and certain attributes associated with these objects) currently known by your NNM instance. I have written many scripts using ovobjprint for the purpose of generating non-standard reports. However, for your purposes the aim would be to run ovobjprint at a configured interval that is sync with your auto discovery interval. I would write a script (most likely in PERL) that records all of your known objects to a file that gets appended when a new object is discovered. The script would write to email a list of the new objects identified.
The real value of writing a script to do this is a function of greater control over when emails get sent and what will be included in the content of the emails sent. If you message (by that I mean email or page) a customer each time a new object is identified, you run the risk of someone getting a bushel of single messages each representing the discovery of one or maybe two new objects. Some of these objects may not even be important to your end customer (like interfaces on a switch). So think about it. If you want, I'll send you one of the scripts I've written that uses the output of "ovobjprint".
Cheers
Larry Moon
- Status
Similar threads
