What the controller does with the packet-in is up to the controller application. You'd need some application that understands you're trying to do discovery. I'd recommend asking around on your controller's mailing list.
--Justin On Feb 18, 2013, at 8:04 PM, vis reddy <[email protected]> wrote: > Justin > I did send the LLDP packets that are received to the controller as a flow > miss using packet in, the controller is sending an packet out with action > Type : output to switchport (0) > Len : 8 > Output port : Flood (all physical ports except input port and those disabled > by STP) > Max Bytes to send:65535 > #of Actions : 1 > > what does this mean and not sure why controller is not realizing the links > even after sending the lldp packets as packet in. > Thanks > Vishnu > > > From: Justin Pettit <[email protected]> > To: vis reddy <[email protected]> > Cc: "[email protected]" <[email protected]> > Sent: Friday, 15 February 2013 1:38 PM > Subject: Re: [ovs-discuss] how to report the links > > I'm not sure I understand the question. Depending on how you set up the flow > table, you can either explicitly send LLDP packets to the controller or let > them not hit any flow, which will send them to the controller. You don't > need to set any capabilities. > > --Justin > > > On Feb 15, 2013, at 11:48 AM, vis reddy <[email protected]> wrote: > > > Justin, > > should the switch indicate something in the capabilities/features/some > > other way when the session is established, if the controller can install a > > flow with the destination mac of lldp mac > > on the switch it would be good. Is this the way or if the switch directly > > send the lldp packets will the controller accepts it? > > Thanks > > Vishnu > > > > From: Justin Pettit <[email protected]> > > To: vis reddy <[email protected]> > > Cc: "[email protected]" <[email protected]> > > Sent: Wednesday, 13 February 2013 6:25 PM > > Subject: Re: [ovs-discuss] how to report the links > > > > As I mentioned, you could just send the LLDP packets to the controller > > itself. If you wanted to process them locally, you could store the > > information in the configuration database and have your controller get the > > information using the OVSDB protocol. > > > > --Justin > > > > > > On Feb 13, 2013, at 6:21 PM, vis reddy <[email protected]> wrote: > > > > > Thanks Justin, > > > How do we report a link connected to another switch, the switch has > > > detected all the neighbors by lldp. How should i send this info to the > > > controller. > > > Thanks > > > Vishnu > > > > > > From: Justin Pettit <[email protected]> > > > To: vis reddy <[email protected]> > > > Cc: "[email protected]" <[email protected]> > > > Sent: Wednesday, 13 February 2013 6:16 PM > > > Subject: Re: [ovs-discuss] how to report the links > > > > > > There's nothing built into OVS that will do this for you. I've seen > > > solutions like running LLDP in the end-host and sending those packets to > > > the controller, or having the controller generate and handle probes > > > itself. > > > > > > --Justin > > > > > > > > > On Feb 13, 2013, at 6:02 PM, vis reddy <[email protected]> wrote: > > > > > > > Hello All, > > > > Could you please help to understand the following, > > > > I am trying to figure out how to report the links to the controller, > > > > for example the switch has a physical connection to another switch on > > > > port P1 and a host on port P2 > > > > how should i report this to the controller, i do not see any message of > > > > this kinds. > > > > This is required as the controller will know the topology based on this. > > > > if there is already such a mechanism if some one point to the code it > > > > will be very helpful. > > > > Thanks lot > > > > > > > > _______________________________________________ > > > > discuss mailing list > > > > [email protected] > > > > http://openvswitch.org/mailman/listinfo/discuss > > > > > > > > > > > > > > > > > > _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
