Send SNMP from Windows Cellserver

Hi,

i checked the documentation:

"On Windows systems

On a Windows Cell Manager, SNMP traps are sent to the systems configured in the Windows SNMP traps configuration. You need to configure Windows SNMP traps to use the SNMP send method on Windows systems."

 

This is not helpfull at all.... SNMP is already activated, nothing happens.

  • Okay, is correct, you need to have the traps enabled on Windows side. But also you need to configure the report or notification that will be sent specifying the server that will read the traps. 

  • I run a linux snmpd server on the receiving end, but neither snmpd-logs nor a tcpdump shows any received traps (notificaitons created). It's not an issue on the linux box, a telnet on port 162 from the cell server shows activity in a tcpdump on the reciving server.

  • As far as I can remember, one must create a public community profile to be able to send traps. If I find my old documentation, I will send you more information by PM

  • Hi,

     

    does omnisv still lists following?

     

    ProcName Status [PID]
    ===============================
    crs : Active [6632]
    mmd : Active [7112]
    kms : Active [5684]
    hpdp-idb : Active [4364]
    hpdp-idb-cp : Active [2532]
    hpdp-as : Active [2716]
    omnitrig : Active
    omniinet : Active [5500]
    Sending of traps disabled.
    ===============================
    Status: All Cell Server processes/services up and running.

    If so, you would need to execute omnisnmp.exe to create necessary registry keys, setup a public community (or with read/create access) and edit OVDest file in <CONFIG>\server\SNMP directory to add the entry of the destination server. e.g. trap-dest:<DEST_SERVER_IP>

    The documentation is insufficient. But some things are rarely changed in new versions, so old documentation might be useful. Search for DP Operations Guide, which was written for DP 6.10, the SNMP section there might helpful for you.

  • Verified Answer

    Hello ,

    You're right, the documentation is incomplete. I have requested an update. This will take a few days. Important for the Windows Cell Manager is that you need to re-create the OVdests and OVfilter files. The are not properly encoded for a Windows system. I asked support to fix this in the next release.

    If you just change them omnisv status may not report the SNMP destination.

    So the OVdests file should look like this.

    trap-dest: monitoring1.domain.com trap-dest: monitoring2.domain.com

    The OVfilter may look like this, if you want to exclude messages in normal and minor events. Other valid options are major, critical and warning.

    normal minor

    Regards,
    Sebastian Koehler

  • Verified Answer

    Hello ,

    You're right, the documentation is incomplete. I have requested an update. This will take a few days. Important for the Windows Cell Manager is that you need to re-create the OVdests and OVfilter files. The are not properly encoded for a Windows system. I asked support to fix this in the next release.

    If you just change them omnisv status may not report the SNMP destination.

    So the OVdests file should look like this.

    trap-dest: monitoring1.domain.com trap-dest: monitoring2.domain.com

    The OVfilter may look like this, if you want to exclude messages in normal and minor events. Other valid options are major, critical and warning.

    normal minor

    Regards,
    Sebastian Koehler