[jboss-jira] [JBoss JIRA] Commented: (JBAS-4227) [SnmpAgentService] MIB2SystemGroup violates RFC-1213

Thu Sep 10 05:10:36 EDT 2009

    [ https://jira.jboss.org/jira/browse/JBAS-4227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12485111#action_12485111 ] 

Dimitris Andreadis commented on JBAS-4227:
------------------------------------------

Scott, I had a look at your solution. It will probably work, however, the more generic one would be to provide an explicit mapping mechanism, rather than the implicit one we have now. I might do it sometime, if I find the time...

> [SnmpAgentService] MIB2SystemGroup violates RFC-1213
> ----------------------------------------------------
>
>                 Key: JBAS-4227
>                 URL: https://jira.jboss.org/jira/browse/JBAS-4227
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: SNMP adapter
>    Affects Versions: JBossAS-4.2.3.GA
>            Reporter: Kenny MacLeod
>            Assignee: Scott Marlow
>             Fix For: JBossAS-5.2.0.Beta1, JBossAS-6.0.0.Alpha1
>
>
> The SnmpAgentService exposes a standard MIB2 System Group.  However, the OIDs that are produced violate RFC-1213, which dictates that the sysUpTime value should have a type of TimeTicks.  Instead, SnmpAgentService generates a type of int32.
> Take the following output from snmpwalk:
> SNMPv2-MIB::sysDescr = STRING: Central Computer
> SNMPv2-MIB::sysObjectID = OID: SNMPv2-SMI::enterprises.18016.1.1.2
> SNMPv2-MIB::sysUpTime = Wrong Type (should be Timeticks): Gauge32: 769331
> SNMPv2-MIB::sysContact = STRING: Agent Smith
> SNMPv2-MIB::sysName = STRING: kizoom at 10.10.0.208
> SNMPv2-MIB::sysLocation = STRING: In The Matrix
> SNMPv2-MIB::sysServices = INTEGER: 64
> End of MIB
> For systems which monitor SNMP agents (e.g. OpenNMS), this causes them to reject the agent because of the bad type.
> The bug lies in org.jboss.jmx.adaptor.snmp.agent.RequestHandlerImpl, which determines the type of the OID value by examining the type of the JMX attribute being monitored.  It has no way to generate a TimeTicks value, it can only handle Long, String, Integer and SnmpOID types.
> The JBoss wiki states that RFC-1213 is supported, but this is incorrect when the type for sysUpTime is wrong (http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossSNMPAdapterGetValues).  Also the attributes.xml file in xnmp-adaptor.sar quotes RFC-1213.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira