3 Replies Latest reply on Aug 26, 2010 4:18 PM by SamuelB

NodeID Field Out of Synch Between Node and Trap Tables

thunter99 Jun 30, 2009 11:57 AM

I'd like to ask for some verification on how Traps work before writing code to keep the Nodes.NodeID and Trap.NodeID fields in synch.

It appears that the Trap.NodeID field has a value of 0 and is not updated to match the Nodes.NodeID field when the device is discovered (or re-added) AFTER traps have been received for that device (IP).

The impact is that any reports that have JOINs with Trap table have gaps, for example trying to associate Traps with Nodes.Caption or Nodes custom properties.

I can understand that a Trap.NodeID value would not not exist when there is no corresponding Nodes.NodeID value but it seems that the application should keep these in synch or alternatively auto-add a Nodes record if a trap is received from an unknown device.

Re: NodeID Field Out of Synch Between Node and Trap Tables

denny.lecompte Jul 1, 2009 8:51 PM (in response to thunter99)

We don't currently update existing traps when a node is added. We'll take that as a feature request.
Like Show 0 Likes(0)

Actions
Re: NodeID Field Out of Synch Between Node and Trap Tables

SamuelB Aug 26, 2010 3:50 PM (in response to thunter99)

This seems more like a bug than a feature request. Is this how Orion NPM works by design? If so, what are the steps required to update the Trap.NodeID field going forward once the node is added to Orion NPM?
Like Show 0 Likes(0)

Actions
- Re: NodeID Field Out of Synch Between Node and Trap Tables
  
  SamuelB Aug 26, 2010 4:18 PM (in response to SamuelB)
  
  This also appears to be the behavior for the Syslog.NodeID field as well. What are my options for having this field automatically update going foward now that the node has been added to NPM?
  
  Like Show 0 Likes(0)
  
  Actions

Go to original post