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

Minion requires location-specific definitions in SNMP config

    Details

    • Sprint:
      Horizon - June 28th

      Description

      If I set SNMP parameters for a given address or range and do not specify a location, I expect all Minions to fall back to those parameters unless serving a monitoring-location for which a location-specific definition exists. Instead, if no definition exists for the area served, Minion uses the global default (what's in the top-level <snmp-config> element of snmp-config.xml).

      For example, on a system where no location-tied SNMP config definitions exist, I get the expected config when requesting it with no location specified:

      opennms> snmp:show-config 172.22.160.199
      Address: 172.22.160.199
      ProxyForAddress: null
      Port: 161
      Timeout: 1800
      Retries: 1800
      MaxVarsPerPdu: 10
      MaxRepetitions: 2
      MaxRequestSize: 65535
      Version: v2c
      ReadCommunity: TheActualRightOne
      WriteCommunity: private
      

      But when requesting SNMP config for a location that exists, I don't get what I expect:

      opennms> snmp:show-config -l USNN 172.22.160.199
      Address: 172.22.160.199
      ProxyForAddress: null
      Port: 161
      Timeout: 1800
      Retries: 1800
      MaxVarsPerPdu: 10
      MaxRepetitions: 2
      MaxRequestSize: 65535
      Version: v2c
      ReadCommunity: public
      WriteCommunity: private
      

        Attachments

          Activity

            People

            • Assignee:
              j-white Jesse White
              Reporter:
              jeffg Jeff Gehlbach
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: