Bug 547830

Summary:	SNMP packets not sent upon alert triggering
Product:	[Other] RHQ Project	Reporter:	Steve Salevan <ssalevan>
Component:	Alerts	Assignee:	Heiko W. Rupp <hrupp>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	ckannan, whayutin
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	2.4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-08-12 16:51:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	547833, 565617

Description Steve Salevan 2009-12-15 19:14:00 UTC

Description of problem:
If an alert triggers in RHQ and SNMP alert senders are enabled, SNMP packets will not be sent to the configured SNMP MIB (the host that receives the SNMP packets).

Version-Release number of selected component (if applicable):
RHQ, master branch, 12/15/09 git pull

How reproducible:
Always

Steps to Reproduce:
1. Create an alert and enable the SNMP alert sender
2. On the MIB, make sure your SNMP ports are open, and run a tcpdump -i eth0 udp | grep <ip of RHQ server>
  
Actual results:
No SNMP packets sent when alerts trigger

Expected results:
SNMP packets sent when alerts trigger

Additional info:

Comment 1 Heiko W. Rupp 2010-01-13 13:26:37 UTC

Steve,
I think this is/was caused by the usage of desination port 161, where 162 is the right one.
With the correct destination port, an snmptrapd instance shows the following in syslog

Jan 13 12:20:36 snert snmptrapd[8929]: 0.0.0.0: Cold Start Trap (0) Uptime: 0:00:00.00, iso.2.3.4.5.6.7.1 = STRING: "test2", iso.2.3.4.5.6.7.2 = STRING: "snert-e", iso.2.3.4.5.6.7.3 = STRING: "snert-e", iso.2.3.4.5.6.7.4 = STRING: "\n- Bedingung 1: Free Memory < 2,0GB\n- Datum/Uhrzeit: 2010/01/13 12:20:28 MEZ\n  - Details: 41,0MB\n", iso.2.3.4.5.6.7.5 = STRING: "!! - medium", iso.2.3.4.5.6.7.6 = STRING: "http://localhost:7080/alerts/Alerts.do?mode=viewAlert&id=10001&a=10001"

I am not sure if tcpdump can see the snmp packet sent when you are sending to localhost and tcpdump is listening on eth0 instead of lo0

Default port has been changed in 67943fe

Comment 2 Heiko W. Rupp 2010-01-13 13:47:23 UTC

Second change (if port is not set in configuration) is in f00ad9a

Comment 4 Steve Salevan 2010-02-16 20:36:49 UTC

Alas, my SNMP trap OID was set to a string and not an integer, and, as such, the SNMP Alert Sender was failing to send an SNMP trap.  Changing this maligned option caused traps to flow appropriately; thus, this bug is verified.

Comment 5 wes hayutin 2010-02-17 13:27:09 UTC

mass move to rhq_chainsaw tracker bug

Comment 6 wes hayutin 2010-02-18 14:49:37 UTC

This bug has now been triaged by Chainsaw on 2/18. The expectation is the bug to be addressed by the end of sprint06 roughly 3/10/10.

Comment 7 wes hayutin 2010-03-10 14:19:31 UTC

moving verified bugs to rhq_sprint06, and removing from rhq_chainsaw

Comment 11 Corey Welton 2010-08-12 16:51:12 UTC

Mass-closure of verified bugs against JON.