tiochan_hyperic
Contributor
Contributor

Receiving SNMP traps

Jump to solution
Hi.

I have read some posts about it, but I still don't understand how to configure it.

[here is the post:
http://communities.vmware.com/message/1916186#1916186
]

Suppose that I want to monitorize a CISCO switch, which is sending snmp traps to the host where I have installed the hyperic server.

Its simply to create the platform, using its snmp comunity, and soon it appears with its iFaces.
Now I would like to detect the traps that it is sending to the server.

Now, dougm says:
"The catch is that HQ agent must be able to bind to the default udp 162 to listen. However, this can be changed in agent.propertieslike so:
snmpTrapReceiver.listenAddress=udp:0.0.0.0/1620"

But, which agent?
I have installed a local agent on the same server and I have looked for this property and I couldn't find it.

Could some one explain it to me please, step by step?


Thanks in advanced.
0 Kudos
1 Solution

Accepted Solutions
cwitt_hyperic
Hot Shot
Hot Shot
There is a difference between setting up SNMP traps to be sent by HQ, and setting up HQ to be able to receive SNMP traps. The SQL modifications you speak of are to enable a trap to be generated by an alert firing from HQ, and this is a feature of the Enterprise product. Documentation on that configuration can be found here:

http://support.hyperic.com/confluence/display/DOCSHQ30/Enabling+SNMP+Traps

Receiving traps from SNMP devices capable of sending them is built-in to the Open Source and Enterprise versions of HQ. The process by which you setup and use SNMP traps coming into HQ has not been well documented, so we've added some new information to faciliate setting up the SNMP trap receiver on an HQ agent, and then configuring the network device for acting upon those traps. See it here:

http://support.hyperic.com/confluence/display/DOCSHQ30/Agent+SNMP+Trap+Receiver

Additional questions, or comments welcome as a continuation of this thread. Specifically, some have kicked around the idea that it might make sense to change the default agent listen port for SNMP traps from 162 to 1620 (from a privileged port to a unprivileged port). This would allow the SNMP trap receiver setup to work as a non-root user by default, and would therefore require no modification to the agent.properties file.

View solution in original post

0 Kudos
4 Replies
ygolan99
Contributor
Contributor
Hi,

I assume that you have enabled SNMP trap reciever, did you manage to see "When you view an alert definition, if SNMP is enabled, then you will see SNMP Trap as one of the notification tabs. " ???
i didn't manage to see it after entering the SQL and doing the step required.including server restart.

can you haelp me with understanding what was wrong?

thanks.

Yariv.
0 Kudos
tiochan_hyperic
Contributor
Contributor
I only have executed the SQL query that I have found on the installation docs, but I'm blind, I don't know what I have to do next.

- I think that I have to install an agent on the same server host.

- I have read, on the post that I referenced before, that I have to add some properties, but I don't know finally how it is going to run. (Who is acting as trap reader?)

- And, if one day I can receive traps, how to link a trap to a platform to generate an alarm?
0 Kudos
cwitt_hyperic
Hot Shot
Hot Shot
There is a difference between setting up SNMP traps to be sent by HQ, and setting up HQ to be able to receive SNMP traps. The SQL modifications you speak of are to enable a trap to be generated by an alert firing from HQ, and this is a feature of the Enterprise product. Documentation on that configuration can be found here:

http://support.hyperic.com/confluence/display/DOCSHQ30/Enabling+SNMP+Traps

Receiving traps from SNMP devices capable of sending them is built-in to the Open Source and Enterprise versions of HQ. The process by which you setup and use SNMP traps coming into HQ has not been well documented, so we've added some new information to faciliate setting up the SNMP trap receiver on an HQ agent, and then configuring the network device for acting upon those traps. See it here:

http://support.hyperic.com/confluence/display/DOCSHQ30/Agent+SNMP+Trap+Receiver

Additional questions, or comments welcome as a continuation of this thread. Specifically, some have kicked around the idea that it might make sense to change the default agent listen port for SNMP traps from 162 to 1620 (from a privileged port to a unprivileged port). This would allow the SNMP trap receiver setup to work as a non-root user by default, and would therefore require no modification to the agent.properties file.
0 Kudos
tiochan_hyperic
Contributor
Contributor
Great!

This was what I needed. Thank you, very much.
0 Kudos