When I see rescan interval in the enlinkd configuration, I cringe because I'm thinking that enlinkd also responds to Provisiond's events to trigger it's own scans.
I think that enLinkd should only be scanning based on Provisiond's scanning activities and not on its own schedule. The reason I cringe is that it seems enlinkd will be scanning the node on two separate schedules. Thoughts? :David > Begin forwarded message: > > From: Cyrille Bollu <cyrille.bo...@gmail.com> > Subject: Re: [opennms-discuss] OpenNMS 19 enlinkd topology missing links > Juniper SRX troubleshooting > Date: June 20, 2017 at 2:32:44 AM EDT > To: General OpenNMS Discussion <opennms-disc...@lists.sourceforge.net> > Reply-To: General OpenNMS Discussion <opennms-disc...@lists.sourceforge.net> > > <?xml version="1.0" encoding="ISO-8859-1"?> > <enlinkd-configuration threads="5" > initial_sleep_time="60000" > rescan_interval="86400000" > use-cdp-discovery="true" > use-bridge-discovery="true" > use-lldp-discovery="true" > use-ospf-discovery="true" > use-isis-discovery="true" > />
signature.asc
Description: Message signed with OpenPGP
------------------------------------------------------------------------------ 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-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel
