Hi All,
Is it possible to integrate SolarWinds with IBM Tivoli Netcool OMNIbus? If so, then what would be the requirements from our end (SolarWinds per se) for this integration?
Thank you very much.
I am not sure what modules you have in your Solarwinds environment, by saying that there are a couple of options
1. Forward Alerts from Solarwinds as an SNMP Trap to Netcool - (provide Solarwinds MIB.cfg to netcool team - ask them to convert it into rules - MTtrapd (snmp) probe)
Integrate Solarwinds events with IBM Tivoli Netcool OMNIbus | Orb Data
2. Forward Alerts from Solarwinds as posteifmsg and these messages can be received by Netcool EIF Probe
IBM Knowledge Center
Hope it helps
Hi vinay.by, thanks for the reply. We'll check on this one. Thank you very much.
No Worries, if you feel the response was helpful please mark it as helpful as it would be useful for others who search for the same.
Later on if you apply any of these in your project please post the details and mark it as correct on the same thread
We send traps to Netcool from our solarwinds servers. Netcool parses the trap and the Alert Message from the Trigger Action.
The alert message sends the severity and either a SET or CLEAR.
CRITICAL&SET&Node Down&${IP_Address}&Node ${NodeName} is ${Status}
This is our node down trap. We created the traps and the rules to match for node down, interface down, interface errors, hardware sensor, application, component, volume, custom poller, and a generic trap.
.
Hi, how can we send traps to Netcool from our solarwinds servers? Is it by editing the alert? For instance, I want to send an alert to IBM that the node is down. How can we execute that alert?
See the NPM administrator guide on how to configure sending a trap as an alert action: NPM alert action: send an SNMP trap - SolarWinds Worldwide, LLC. Help and Support
Hi tdanner, thanks for providing the link. What is the purpose of trap template?
I would forward it as a syslog instead, that way you can format it in Solarwinds to look exactly like you want before it reaches Netcool. That way there is no need need to edit a second time in Netcool for every alert.
Then you can build a few rules in Netcool once and forget about it.