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

Add full trapoid for Snmp V1

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: Meridian-2019.1.22
    • Fix Version/s: 28.1.1
    • Component/s: None
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None
    • Story Points:
      3
    • Sprint:
      Horizon 2021 - Sep 29 - Oct 13
    • Acceptance / Success Criteria:
      Hide

      Sending SNMP traps like :
      snmptrap -v1 -c public 127.0.0.1 .1.3.6.1.4.1.9.9.276 127.0.0.1 6 1 '' should result in trapoid as .1.3.6.1.4.1.9.9.276.0.1

      Show
      Sending SNMP traps like : snmptrap -v1 -c public 127.0.0.1 .1.3.6.1.4.1.9.9.276 127.0.0.1 6 1 '' should result in trapoid as .1.3.6.1.4.1.9.9.276.0.1

      Description

      As part of NMS-13422 , we have added support for trapoid when sub-id(0) is part of oid. But this doesn't work for V1.

      For SNMP V1, we need to consider following and create full trapoid.
      Conversion defined in RFC2576

      (2) If the SNMPv1 generic-trap parameter is 'enterpriseSpecific(6)',
      the SNMPv2 snmpTrapOID parameter SHALL be the concatentation of
      the SNMPv1 enterprise parameter and two additional sub-
      identifiers, '0', and the SNMPv1 specific-trap parameter.

      (3) If the SNMPv1 generic-trap parameter is not '
      enterpriseSpecific(6)', the SNMPv2 snmpTrapOID parameter SHALL
      be the corresponding trap as defined in section 2 of RFC1907
      [12]:

      generic-trap parameter snmpTrapOID.0
      ====================== =============
      0 1.3.6.1.6.3.1.1.5.1 (coldStart)
      1 1.3.6.1.6.3.1.1.5.2 (warmStart)
      2 1.3.6.1.6.3.1.1.5.3 (linkDown)
      3 1.3.6.1.6.3.1.1.5.4 (linkUp)
      4 1.3.6.1.6.3.1.1.5.5 (authenticationFailure)
      5 1.3.6.1.6.3.1.1.5.6 (egpNeighborLoss)

      The %trapoid% parameter will be pulled directly from snmpTrapOID parameter in the SNMP v2c/v3 Notification and will be created from an SNMP v1 Trap PDU using the algorithm defined in the above RFC. This will uniquely identify Trap based events.

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration