Re: Discovery of deleted nodes

   So ... I reset my etc space to default and reran OpenNMS, once again 
testing discovery of a deleted IP address.  It behaved the same way.  
Clearly, it isn't a configuration-based problem.

   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.

   So list - my question has been answered.

   Shane

On 05/03/2018 02:05 PM, Shane Dawalt wrote:
>
> I am currently running OpenNMS 16.0.  I want to move to 21.0.5. I am 
> simply doing a new install of 21.0.5 on a separate server and 
> rediscovering network devices.  The new server is Centos 7.4.
>
> Discovery and SNMP are working on the 21.0.5 server.  But I am having 
> trouble rediscovering a node that I have deleted.  I am unable to find 
> a discussion of this behavior through web searches - which makes me 
> think that I have done something wrong.
>
> Discovery is set to look for a range of 3 IP addresses. Discovery 
> initial delay is 30 seconds, and rediscovery is 60 seconds. log4j2 is 
> set to debug level for discovery.
>
> To test this, I delete the node and then confirm it is deleted by 
> verifying that its corresponding rows are deleted in the node and 
> ipinterface tables of the opennms database.  Once verified, I begin 
> watching the discovery.log file.  I see Discovery begin its operation 
> every 60 seconds.  It pings only the undiscovered IP address.  It 
> doesn't attempt to ping the two previously discovered addresses 
> (including the address of the node I have deleted).  The only way I 
> can get the deleted node to be rediscovered is to restart OpenNMS.  
> Even restarting the discovery process doesn't help. Does this seem 
> right?  What am I missing?  Or what have I done?
>
>   Shane
>
>
> ------------------------------------------------------------------------------ 
>
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> https://urldefense.proofpoint.com/v2/url?u=http-3A__sdm.link_slashdot&d=DwIGaQ&c=3buyMx9JlH1z22L_G5pM28wz_Ru6WjhVHwo-vpeS0Gk&r=NzA6nby4G4IMBRa4Q_-c-SF8A4k8PpEAC5q8tD4Wfl0&m=ISAWs4w5OnU3eEcaRFNTNr-RD6O_TCJoTjqSRMIlcuo&s=rasPECbfpcJQuuoenD-_I-eI6iVOcn4CuIKV-zZsBUM&e= 
> _______________________________________________
> Please read the OpenNMS Mailing List FAQ:
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.opennms.org_index.php_Mailing-5FList-5FFAQ&d=DwIGaQ&c=3buyMx9JlH1z22L_G5pM28wz_Ru6WjhVHwo-vpeS0Gk&r=NzA6nby4G4IMBRa4Q_-c-SF8A4k8PpEAC5q8tD4Wfl0&m=ISAWs4w5OnU3eEcaRFNTNr-RD6O_TCJoTjqSRMIlcuo&s=oDnq6h6pi1ZeHHt8zIYgJOWYZ89SF3Xwe7fnvM-jCPM&e= 
>
> opennms-discuss mailing list
>
> To *unsubscribe* or change your subscription options, see the bottom 
> of this page:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_opennms-2Ddiscuss&d=DwIGaQ&c=3buyMx9JlH1z22L_G5pM28wz_Ru6WjhVHwo-vpeS0Gk&r=NzA6nby4G4IMBRa4Q_-c-SF8A4k8PpEAC5q8tD4Wfl0&m=ISAWs4w5OnU3eEcaRFNTNr-RD6O_TCJoTjqSRMIlcuo&s=prmc56eGsBm-V_VGyxlFDj8EyGxBhIImsLDYO0loaa4&e= 



------------------------------------------------------------------------------
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