Re: OEM and SNMP
Date: Tue, 9 Mar 2010 22:29:24 +0000
Yes, I've configured it and have been using it live for around a year. I didn't have to configure anything on the management server, certainly not snmpd. As Brandon said, I used snmptrapd to test it. You do need to configure OEM itself. I think the steps are:
- Create a notification method using the ip address and port for the snmp application;
- There's a button to test it. Point it at snmptrapd and you should see the output;
- Add the notification method to the database critical states (sorry if I've got the name wrong - I'm not at the console now) notification rule;
- Test by raising an alert - I usually shut down an agent - if it sends out the alert via SNMP it will say so in the alert history, but it can take some fiddling to find it.
-- David Lord On 9 March 2010 21:42, Haroon A. Qureshi <haroon_a_qureshi_at_yahoo.com> wrote:Received on Tue Mar 09 2010 - 16:29:24 CST
> Has anyone been able to successfully configure OEM to send SNMP messages to
> a third-party application, such as CompuWare? We are trying to configure it
> to do so and having a difficult time doing so.
> On the OEM (unix/solaris) server, do we need the snmpd service running?
> Even with it down, the OEM test always returns as being successful, which
> leads one to believe that OEM is using some other method to send the
> messages. Or is the snmpd daemon only for receiving traps for OEM?
> Any help in this configuration is greatly appreciated.