Dear Murphy, Got it. I'll try to cancel the timer...:-) Thank you very much for your prompt reply!
Best Regards, Zhiyang Su ------------------------------------------------------------------------ *From:* Murphy McCauley <murphy.mccau...@gmail.com> *To:* Zhiyang Su <suzhiy...@gmail.com> *Cc:* pox-dev <pox-dev@lists.noxrepo.org> *Sent:* Tuesday, March 04, 2014 1:56PM *Subject:* Re: [pox-dev] How to unregister a component? There's no super-elegant way to do this right now without a bit of code tweaking. There's actually a prototype in this vein... the idea was basically to use LLDP to discover topology initially, then use port status changes to detect downed links. This is probably coming to mainline someday, but I don't know when. Stopping the sending of LLDP should be pretty easy (if a bit of a hack), I think. You just need to cancel the timer which does the sending, which should be something like... openflow.discovery._sender._timer.cancel() This doesn't stop links from timing out, though. This may not be a problem if you just listen to link up events and ignore link down events. If you do want to cancel this, though, it's too bad, since a reference to the appropriate timer (in Discovery) isn't saved anywhere. That'd be easy enough to fix, though. -- Murphy On Mar 3, 2014, at 7:41 PM, Zhiyang Su <suzhiy...@gmail.com> wrote: > Dear All, > I'd like to register openflow.discovery module to detect links and build > the topology in the beginning. However, as I believe that the links and > switches never fail, I don't want the module sending LLDP messages to > the network after convergence. > > Is there any way to "unregister" the discovery module or stop the module > sending LLDP messages? > > Thanks! > > Best Regards, > Zhiyang Su >
