Trap event parenting lacks bias toward SNMP primary interfaces

Description

From support ticket:

The case is following(with imaginary ip address):

1) We have node1 with ip address 10.10.10.10 which is primary interface on that node in OpenNMS
2) We have node2 with same ip address 10.10.10.10 which is not primary interface on that node in OpenNMS
3) Then SNMP trap arrives from node 1 and this trap is mapped to node 2 in OpenNMS with this 10.10.10.10 address which is not even primary interface.

So they way this should go in my opinion is that this should map to the node which has primary interface on this address. At least in our case. I also queried this interface address from the OpenNMS DB and select is returning first this wrong node ip interface, so is alarm just mapped based on which node address returns first?

Environment

See https://mynms.opennms.com/Ticket/Display.html?id=5269

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Jesse White October 11, 2017 at 5:44 PM

This behavior has been addressed as part of the first for .

fooker October 9, 2017 at 9:05 PM

I can. My fix for will implement the behavior described by op.

Jesse White October 5, 2017 at 7:28 PM
Edited

I think this is being address within the scope of . can you confirm?

Fixed

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

PagerDuty

Created October 5, 2017 at 2:36 PM
Updated October 11, 2017 at 5:44 PM
Resolved October 11, 2017 at 5:43 PM