Thanks for your reply. Indeed, it's better to install the LLDP flow in the l2_multi or topo_proactive other than in the discovery module, but it doesn't that matter. Without this flow, by default ,the LLDP packet still will be forwarded to the controller anyway.
On Fri, Jan 9, 2015 at 6:01 PM, Murphy McCauley <murphy.mccau...@gmail.com> wrote: > In the case of l2_multi, there isn't a point. But l2_multi isn't the only > component that uses discovery. Ones that don't clear the table don't have > this issue at all. And some that do clear the table (e.g., topo_proactive) > install the table entry themselves. > > As for what caused this... I think l2_multi predates discovery having the > option to install a table entry. > > Here's an untested patch which maybe is an improvement on the state of > affairs? > > -- Murphy > > > > On Jan 9, 2015, at 6:30 AM, tim huang <pds...@gmail.com> wrote: > > > Hi, > > > > I found in the discovery module, the controller will install a flow for > the LLDP packet to every switch, however, in the l2_multi module, the > controller will clear all flows when there is a link event for > re-calculating the path , which means the flow installed from discovery > module will only exist at very first beginning. What's the point of the > temporary flow installed by the discovery module? > > > > -- > > Thanks > > Tim > > > -- Thanks Tim
