[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opennms-buglist
Subject:    [Buglist] [JIRA] (NMS-5110) New-suspect event flood possible in trapd
From:       jira () opennms ! org (Tarus Balog (JIRA))
Date:       2011-12-20 16:18:30
Message-ID: 899491994.567.1324397910582.JavaMail.jira () mail1 ! opennms ! com
[Download RAW message or body]

Tarus Balog created NMS-5110:
--------------------------------

             Summary: New-suspect event flood possible in trapd
                 Key: NMS-5110
                 URL: http://issues.opennms.org/browse/NMS-5110
             Project: OpenNMS
          Issue Type: Bug
          Components: Trapd
    Affects Versions: 1.8.16
            Reporter: Tarus Balog
            Assignee: Matt Brozowski
            Priority: Minor


I thought this was fixed, but apparently it is still an issue.

If new-suspect-on-traps is set to true in the trapd configuration file, it is \
possible to create a number of duplicate nodes if multiple traps from an unknown \
interface occur at the same time. Currently, when a trap comes it, it checks a table \
of known IP addresses to see if the trap should be generated. That table is generated \
from existing devices. However, if OpenNMS receives, say, three traps from an unknown \
IP in a short amount of time, it will generate three newSuspect events causing three \
nodes to be added.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: \
http://issues.opennms.org/secure/ContactAdministrators!default.jspa For more \
information on JIRA, see: http://www.atlassian.com/software/jira

        


[prev in list] [next in list] [prev in thread] [next in thread]