Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Traps Not Associated With Node

Description

It is my understanding that when a trap comes in to OpenNMS from a particular IP address, it should be associated with a node if that IP address is in the system.

At this site the IP address 172.26.35.16 is associated with NodeID 1. But when traps come in it is not associated with the node at all.

Attached please find screenshots of the node page, the failing traps and the relevant logs.

Note that DNS is not working on this system. While I don't believe that would be a problem it is another data point. When I wrote this code 15+ years ago all I did was created a table in memory that mapped IP addresses to nodes.

 

Acceptance / Success Criteria

None

Attachments

3

Lucidchart Diagrams

Activity

Chandra Gorantla July 14, 2020 at 4:15 PM

  I think this may not be a bug. Let me know if you have more data points on this

Chandra Gorantla July 9, 2020 at 5:34 PM

  Looks like the node is on location imaprdapp*. But traps doesn't seems to be associated with any location. Are they directly sending traps to OpenNMS instead of Minion ? 

Chandra Gorantla July 9, 2020 at 3:06 PM

In usual case, node is always associated with trap events.  Since we use NodeCache instead of direct DB access for performance reasons, there is slight chance that cache didn't get updated in time.  Need to look more closely to see if there are any other corner cases. 

Not a Bug

Details

Assignee

Reporter

Labels

HB Backlog Status

Components

Fix versions

Affects versions

Priority

PagerDuty

Created July 7, 2020 at 8:49 PM
Updated August 4, 2020 at 5:01 PM
Resolved August 4, 2020 at 5:01 PM