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

SNMP detector should use snmp profiles

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 25.1.0
    • Fix Version/s: 25.1.2
    • Component/s: None
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None
    • Sprint:
      Horizon 2019 - November 27th, Horizon 2019 - December 11th

      Description

      Currently the SNMP detector only uses configuration from the default SNMP config and definitions. It should be possible to use SNMP profiles to find a matching config.

      Key points from a chat this morning:

      • SNMP detector should optionally use SNMP profiles in the same way that Provisiond's SNMP scan already does
        • The default should be not to use SNMP profiles
      • SNMP detector's parameterized configuration, if any, should override the corresponding elements of an SNMP profile
        • For example, if an SNMP profile specifies a timeout of 1800ms with 3 retries, but the detector is configured with parameters timeout=500 and retries=0, it should use a 500ms timeout with zero retries
        • Not sure what to do in cases where this overriding creates a nonsensical set of parameters, such as a profile specifying SNMPv3 with security level authPriv being overridden by a detector configuration specifying SNMPv1 but no community string. Maybe it's fine to declare that, for now, only timeout and retries can be overridden in this way.
      • If the SNMP detector is configured to use SNMP profiles, persisting the eventual fitted profile should be optional
        • Persisting of the fitted profile can slide in the event it turns out to be too hard

        Attachments

          Activity

            People

            Assignee:
            cgorantla Chandra Gorantla
            Reporter:
            cgorantla Chandra Gorantla
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: