You may also want to limit which nodes the emails are being sent for. If this is the case, you could create a node group containing only those nodes, and then create a node-based action, rather than a general action, on the incidents you want to email.
I, BTW, generally use blat.exe when sending emails from NNMi, but obviously this is just one out of many alternatives.
I can't use Blat because I'm on RedHat, but I make a bash script who works with mailx. This script is working on the command line interface but I don't manage to put it on NNM. Could you help me to configure the NNM to use my script please?
Furthermore, if the action is in fact enabled, have a look at the logfiles in the $nnmdatadir/log/nnm directory. I usually look at the last update timestamp of the files, to see which would be worth opening.
When I test incident based actions, I do this by manually changing the lifecycle state of an incident that should trigger the action. I.e. setting it to closed, then changing it back to registered. Rather than waiting for a new incident to happen, or trying to generate them from the command line. Just a little testing tip
Copy your script to the nnm actions folder /var/opt/OV/ shared/nnm/actions/
In the Incident Configuration type the command directly without absolute path and pass the parameters as needed using Custom Incident Attributes as needed.
Regards, Mahmoud Ibrahim http://www.mahmoudthoughts.com --- Say thanks by clicking the "Kudos! Star" which is on the left. Make it easier for other people to find solutions, by marking my answer with "Accept as Solution" if it solves your issue.
Guys, I'm missing something, at the "Select the Event" step. Which event? Obviously we'd like to get e-mail notification for ALL incidents, so picking any specific one of the many predefined ones seems a bad idea. If I try to create new one, the dialog lists "SNMP Object ID .220.127.116.11.18.104.22.168.22.214.171.124.9999". Hmmm.
Using this approach, you would have to configure it on an incident by incident basis. But if you want a more general forwarding of all/many incidents, you are probably better off investigating the xMatters Lite alternative.
The problem with this alternative, though, seems to be that you will not be able to use NNMi's own way of identifying a group of nodes (i.e. node groups).
Thanks for the hint, but 3rd party stuff is out of the equation here. Let me rephrase it:
OK, so we have this nice big NNMi thing monitoring the network. When something happens, anything, we want to get notified, as the staff has better things to do than constantly staring at NNMi maps. Basic e-mail is fine, operator will lookup the details in NNMi map when notified ... So where can I put that e-mail? Individually into tens to hundreds of each and every possible Incident type?? Please say I'm wrong on this one ... ;-)
Ok. There's not that much scripting for "send me an e-mail". But first there needs to be a sane way to hook the script into NNMi for "all incidents, thank you". I thought I was missing something obvious in the docs, but maybe it really isn't there. Thanks!
I hope that someone is still watching this thread.
I have configured blat and email.ovpl to work properly and I receive e-mails properly.
But, my problem is when I try to configure sending e-mails to several e-mails. I created node group 1 (contains all routers) and node group 2 (contains several routers). I want NNM (blat/email.ovpl) to send e-mail company1 (which have access to all routers) and to company2 (which has access to several routers) when incident occurs in group of several routers.
I went to Incidents - Snmp Trap Configurations - opened incident - node settings.
- Under Node group i added group1 and defined "group1.ovpl $firstOccurrenceTime $name $priority $severity $managementAddress $sourceNodeName $sourceObjectName" under actions (lifecycle state registered, and command type scriptOrExecutable.); ordering is 1
- Under Node group i added group2 and defined "group2.ovpl $firstOccurrenceTime $name $priority $severity $managementAddress $sourceNodeName $sourceObjectName" under actions (lifecycle state registered, and command type scriptOrExecutable.); ordering is 1
when incident occurs, e-mail is sent only to firstname.lastname@example.org and I don't receive anything to email@example.com