Application Server 3  4  5 and 6
  1. Application Server 3 4 5 and 6
  2. JBAS-4227

[SnmpAgentService] MIB2SystemGroup violates RFC-1213

    Details

    • Type: Bug Bug
    • Status: Closed Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: JBossAS-4.2.3.GA
    • Fix Version/s: 6.0.0.M1
    • Component/s: SNMP adapter
    • Security Level: Public (Everyone can see)
    • Labels:
      None
    • Similar Issues:
      Show 9 results 

      Description

      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@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.

        Issue Links

          Activity

          Hide
          Dimitris Andreadis
          added a comment -

          Tobias, do you want to look into this?

          Show
          Dimitris Andreadis
          added a comment - Tobias, do you want to look into this?
          Hide
          Dimitris Andreadis
          added a comment -

          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...

          Show
          Dimitris Andreadis
          added a comment - 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...
          Hide
          Scott Marlow
          added a comment -

          This is also fixed for 4.x via our JBoss Enterprise Application Platform 4.x (see linked issues associated with this JIRA).

          Show
          Scott Marlow
          added a comment - This is also fixed for 4.x via our JBoss Enterprise Application Platform 4.x (see linked issues associated with this JIRA).

            People

            • Assignee:
              Scott Marlow
              Reporter:
              Kenny MacLeod
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: