Re: Discovery of deleted nodes

I've created issue NMS-10088 for this.





-
John Blackburn
Solution Architect - Cloud Services

ABB Enterprise Software Pty Ltd
Level 9, 757 Ann St
Fortitude Valley QLD 4006 Australia
Phone: +61 7 3303 3219
Mobile: +61 403 344 524
abb.com


-----Original Message-----
From: David Hustace [mailto:[email protected]] 
Sent: Saturday, 5 May 2018 12:16 AM
To: DiscussionList List <[email protected]>
Subject: Re: [opennms-discuss] Discovery of deleted nodes

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


> On May 4, 2018, at 09:58, Shane Dawalt <[email protected]> wrote:
>
> Expecting this was a code change after 16.0, I waded through the OpenNMS issues database and came across HZN-572 (18.0.0).  It's an IP filter put in place for the move to Camel.  It prevents pinging of already discovered addresses.  Prior to HZN-572, the database was used for filtering already discovered IPs.  This worked well, because when a node is deleted, it's ipinterface is deleted, which allowed the IP to be rediscovered.  Apparently, the new filter isn't aware of deleted IPs.

Shane,

According to that issue, HZN-572, the issue was resolved and should behave as expected.  Were you able to work around it if this is still an issue and if so, how?

Cheers,
David Hustace
The OpenNMS Group, Inc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss