Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-6108

Can't use SNMPv3 with NoAuth-NoPriv

    XMLWordPrintable

    Details

      Description

      This issue is at the root of the following commercial support ticket:
      https://mynms.opennms.com/Ticket/Display.html?id=2415

      Using a configuration like the following:

      <definition version="v3" security-name="topsecret" context-name="VF:2">

      OpenNMS is going to force some default values for the following SNMPv3 settings when building the SNMPv3 PDU Requests:

      • auth-protocol
      • auth-passprase
      • privacy-protocol
      • privacy-passphrase

      For this reason, the final request is built on a wrong way, because the remote agent expect to use only the security-name.

      SNMP4J expects to receive null for optional parameters if they are not required. Actually, it is possible to execute an snmpwalk using SNMP4J as follow:

      /opt/opennms/bin/snmp-request -Ow -v 3 -u opennmsuser -n VF:2 100.0.0.1 1.3.6.1.2.1.4.20
      Using SNMP4J from: /opt/opennms/lib/snmp4j-1.11.1.jar

      1.3.6.1.2.1.4.20.1.1.10.11.12.58 = 10.11.12.58
      1.3.6.1.2.1.4.20.1.1.10.11.12.59 = 10.11.12.59
      1.3.6.1.2.1.4.20.1.1.127.0.0.1 = 127.0.0.1
      1.3.6.1.2.1.4.20.1.2.10.11.12.58 = 805306369
      1.3.6.1.2.1.4.20.1.2.10.11.12.59 = 805306375
      1.3.6.1.2.1.4.20.1.2.127.0.0.1 = 805306370
      1.3.6.1.2.1.4.20.1.3.10.11.12.58 = 255.255.255.0
      1.3.6.1.2.1.4.20.1.3.10.11.12.59 = 255.255.255.0
      1.3.6.1.2.1.4.20.1.3.127.0.0.1 = 255.255.0.0
      1.3.6.1.2.1.4.20.1.4.10.11.12.58 = 1
      1.3.6.1.2.1.4.20.1.4.10.11.12.59 = 1
      1.3.6.1.2.1.4.20.1.4.127.0.0.1 = 0

      Because the above query is working fine, we can discard any problems with SNMP4J, so the problem is related with how the SNMPv3 settings are parsed, processed and/or passed to SNMP4J, when building the SNMPv3 PDU requests.

        Attachments

          Activity

            People

            • Assignee:
              agalue Alejandro Galue
              Reporter:
              agalue Alejandro Galue
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: