Thank You, that clears few questions. So,the controller instructs a switch SW1 packet-out (LLDP payload) on port p1 , as soon as it learns about this same LLDP packet as an unknown packet (say from SW2 p2) through a packet-in message, the controller establishes that SW1 p1 is connected to Sw2 p2 right?
Also, when I say 'same LLDP packet', I am thinking that SW2 should forward the LLDP packet of SW1 as received from SW1 and not of itself i.e SW2. Cheers! Durga On Wed, May 21, 2014 at 6:09 AM, Wes Felter <w...@felter.org> wrote: > On 5/19/14, 10:13 PM, durga wrote: > > 6. Switch -> Controller ( Packet_In message < Neighbour Solicitation >> (LLDP) reason (no matching action)>) >> 7. Controller -> Switch ( Packet_Out message <Neighbour >> Solicitation(LLDP)> action :Flood) >> > > Steps 6 and 7 are in the wrong order. The controller needs to send the > LLDP before other switches will receive it. > > Questions: >> 1. Is LLDP ON by default ? >> > > OpenFlow doesn't know anything about LLDP. > > 2. Is LLDP is not ON by default, how is the switch instructed to trigger >> the same? >> > > Switches don't send LLDP. A controller can use packet out to send LLDPs. > > 3. Once LLDP packet is on wire,is the rule [2] intrinsically defaulted >> in the switch? >> > > Generally yes. It depends on what version of OpenFlow you're using. > > In general, a controller does not need to install any flows to perform > LLDP discovery. The controller can just use packet out and packet in > messages. > > -- > Wes Felter > IBM Research - Austin > > _______________________________________________ > openflow-discuss mailing list > openflow-discuss@lists.stanford.edu > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss >
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
