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
discovery_install_flow_change.patch
Description: Binary data
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
