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

We have a regression in the SNMP core API for get effective address (snmp-proxy)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: SNMP API
    • Security Level: Default (Default Security Scheme)
    • Labels:
    • Sprint:
      Horizon 2019 - May 22nd 2019

      Description

      At some point in refactoring the SNMP API, the support for the proxy-host attribute in the SNMP configuration quit working.  I could not find any reference to the method: org.opennms.netmgt.snmp.SnmpAgentConfig.getEffectiveAddress()

      Which returns the proxy host address vs the nodes "provisioned" address.

       

      NAT'd 1.1.1.1:50161->10.1.1.1:161 Example:

        <definition proxy-host="1.1.1.1" port="50161" write-community="writepwd" read-community="readpwd">
           <specific>169.254.1.1</specific>
        </definition>
      

       A node provisioned with the IP address 169.254.1.1 would have an SNMP proxy agent reachable at 1.1.1.1 on port 50161.

       

      I've seen another implementation of an actually SNMP Proxy agent that uses an overloaded community string and the definition would look like:

        <definition proxy-host="1.1.1.1" port="161" read-community="proxyReadString@hostReadString@10.1.1.1:161">
           <specific>169.254.1.1</specific>
        </definition>
      

       This used to work but seems to have slipped through our refactoring.

        Attachments

          Activity

            People

            • Assignee:
              patrick.schweizer Patrick Schweizer
              Reporter:
              david David Hustace
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: