Go ahead and open a ticket on http://dev.zenoss.org/trac/  There are a  
pair of SNMP trap tickets already verified for 2.3.3:
http://dev.zenoss.org/trac/ticket/4183
http://dev.zenoss.org/trac/ticket/4219

Thanks,
Matt Ray
Zenoss Community Manager
community.zenoss.com
[email protected]



On Jan 13, 2009, at 2:29 PM, crosse wrote:

> Ok, after doing a little more research, a coworker and I found out  
> some more information about the issue.  Say I get a trap of type  
> GEIST-MIB:gstClimateTempCTRAP (this is an environmental monitoring  
> unit).  The OID for this trap is
>
> Code:
> [zen...@it-zenoss1 ~]$ snmptranslate -On GEIST-MIB:gstClimateTempCTRAP
> .1.3.6.1.4.1.21239.0.10205
>
>
> Notice the "0" right before the ending "10205".
>
> Zenoss 2.3.2 builds an event around this trap with a summary like so:
>
> Code:
> snmp trap geistmfg.21805
>
>
> whereas Zenoss 2.2.4 (the version I was on previously) would build  
> an event with the following summary:
>
> Code:
> snmp trap gstClimateTempCTRAP
>
>
> Doing an snmptranslate on the "geistmfg.21805" string from 2.3.2's  
> summary text gives me this:
>
> Code:
> [zen...@it-zenoss1 ~]$ snmptranslate -On GEIST-MIB:geistmfg.10205
> .1.3.6.1.4.1.21239.10205
>
>
> Notice the conspicuous lack of a zero before the "10205".  I believe  
> Zenoss is decoding these traps wrong by completely removing a zero  
> from the OID.  The correct OID in this case should be:
>
> Code:
> [zen...@it-zenoss1 ~]$ snmptranslate .1.3.6.1.4.1.21239.0.10205
> GEIST-MIB::gstClimateTempCTRAP
>
>
> which decodes properly.  So, whereas the problem psmith was having  
> was that the ".0" was making its way into the event fields  
> unnecessarily, it looks like my issue is the utter lack of that zero  
> being the OID, leading to incorrect SNMP OID translations and  
> therefore incorrect event correlation.
>
> Matt, do I need to submit this as a trouble ticket via the customer  
> portal?  I don't want to have to redo all my event transforms based  
> on a broken OID string, and this is somewhat of a production issue.   
> Thanks!
>
> --seth
>
>
>
>
> -------------------- m2f --------------------
>
> Read this topic online here:
> http://forums.zenoss.com/viewtopic.php?p=29980#29980
>
> -------------------- m2f --------------------
>
>
>
> _______________________________________________
> zenoss-users mailing list
> [email protected]
> http://lists.zenoss.org/mailman/listinfo/zenoss-users

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to