Yes it is; from every perspective.

Zoltan

>-----Original Message-----
>From: Shuva Jyoti Kar
>Sent: Friday, September 27, 2013 10:20 AM
>To: Zoltán Lajos Kis; openflow-discuss@lists.stanford.edu
>Subject: RE: openflow-discuss Digest, Vol 59, Issue 28
>
>But is it Pkt out/Pkt in , from the controller perspective  ?
>
>Shuva
>
>-----Original Message-----
>From: Zoltán Lajos Kis
>Sent: Friday, September 27, 2013 1:43 PM
>To: Shuva Jyoti Kar; openflow-discuss@lists.stanford.edu
>Subject: RE: openflow-discuss Digest, Vol 59, Issue 28
>
>Here is a brief description: http://blogs.ixiacom.com/ixia-blog/discovery-in-
>openflow-networks-at-onf-plugfest/
>
>The only mistake here is that there should be a separate packet_out/lldp
>message per switch and per port. If the controller were to do it as described
>here (one packet_out/lldp for all ports), it wouldn't be able to tell which 
>actual
>ports are connected.
>
>Regards,
>Zoltan.
>
>>-----Original Message-----
>>From: openflow-discuss-boun...@lists.stanford.edu [mailto:openflow-
>>discuss-boun...@lists.stanford.edu] On Behalf Of Shuva Jyoti Kar
>>Sent: Friday, September 27, 2013 10:01 AM
>>To: openflow-discuss@lists.stanford.edu
>>Subject: Re: [openflow-discuss] openflow-discuss Digest, Vol 59, Issue
>>28
>>
>>Hi,
>>
>>Could someone explaain how the Topolgy is discovered using LLDP?
>>
>>Shuva
>>
>>-----Original Message-----
>>From: openflow-discuss-boun...@lists.stanford.edu [mailto:openflow-
>>discuss-boun...@lists.stanford.edu] On Behalf Of openflow-discuss-
>>requ...@lists.stanford.edu
>>Sent: Friday, September 27, 2013 12:31 AM
>>To: openflow-discuss@lists.stanford.edu
>>Subject: openflow-discuss Digest, Vol 59, Issue 28
>>
>>Send openflow-discuss mailing list submissions to
>>      openflow-discuss@lists.stanford.edu
>>
>>To subscribe or unsubscribe via the World Wide Web, visit
>>      https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>>or, via email, send a message with subject or body 'help' to
>>      openflow-discuss-requ...@lists.stanford.edu
>>
>>You can reach the person managing the list at
>>      openflow-discuss-ow...@lists.stanford.edu
>>
>>When replying, please edit your Subject line so it is more specific than "Re:
>>Contents of openflow-discuss digest..."
>>
>>
>>Today's Topics:
>>
>>   1. Re: Ovs controller and NOX controller (Windhya Rankothge)
>>   2. Re: Ovs controller and NOX controller (Windhya Rankothge)
>>   3. Openflow controller discovery (Windhya Rankothge)
>>   4. Re: Openflow controller discovery (shiva m)
>>
>>
>>----------------------------------------------------------------------
>>
>>Message: 1
>>Date: Thu, 26 Sep 2013 09:54:55 +0200
>>From: Windhya Rankothge <windys...@gmail.com>
>>To: Ben Pfaff <b...@nicira.com>
>>Cc: "openflow-discuss@lists.stanford.edu"
>>      <openflow-discuss@lists.stanford.edu>
>>Subject: Re: [openflow-discuss] Ovs controller and NOX controller
>>Message-ID:
>>      <CADWQY-c-
>>9Ee=sw5X+DELVRZriN=5b08ezep0ui+qrkg9irw...@mail.gmail.com>
>>Content-Type: text/plain; charset="iso-8859-1"
>>
>>Thanks alot for the clarification..
>>
>>
>>On Mon, Sep 23, 2013 at 6:32 PM, Ben Pfaff <b...@nicira.com> wrote:
>>
>>> On Mon, Sep 23, 2013 at 04:19:52PM +0200, Windhya Rankothge wrote:
>>> > I have read about ovs controller and NOX controller, and I learnt
>>> > that
>>> ovs
>>> > controller is a reference controller while NOX is a remote controller..
>>> >
>>> > I would like to know the difference between reference controller
>>> > and
>>> remote
>>> > controller..
>>>
>>> ovs-controller is only useful for testing and debugging a switch.  It
>>> isn't anything you would want to deploy.
>>>
>>> NOX applications can be useful in production.
>>>
>>
>>
>>
>>--
>>Best Regards,
>>
>>Windhya Rankothge..... (WINDY)
>>-------------- next part -------------- An HTML attachment was
>>scrubbed...
>>URL: <http://mailman.stanford.edu/pipermail/openflow-
>>discuss/attachments/20130926/1622ef6e/attachment-0001.html>
>>
>>------------------------------
>>
>>Message: 2
>>Date: Thu, 26 Sep 2013 09:55:03 +0200
>>From: Windhya Rankothge <windys...@gmail.com>
>>To: Justin Pettit <jpet...@cs.stanford.edu>
>>Cc: "openflow-discuss@lists.stanford.edu"
>>      <openflow-discuss@lists.stanford.edu>
>>Subject: Re: [openflow-discuss] Ovs controller and NOX controller
>>Message-ID:
>>      <CADWQY-d9wb=nqecRpP4Z9LN2fxhPgR+m63uP-uqRq3P--
>>1c...@mail.gmail.com>
>>Content-Type: text/plain; charset="iso-8859-1"
>>
>>Thanks alot for the clarification..
>>
>>
>>On Mon, Sep 23, 2013 at 5:50 PM, Justin Pettit
>><jpet...@cs.stanford.edu>wrote:
>>
>>> Both controllers can be used remotely.  The one that comes with OVS
>>> is intended to test the OpenFlow connection in OVS; it just acts as a
>>> learning switch.  NOX is a framework for building network
>>> applications and is probably closer to what you want.
>>>
>>> Hope that helps.
>>>
>>> --Justin
>>>
>>>
>>> On Sep 23, 2013, at 7:19 AM, Windhya Rankothge
><windys...@gmail.com>
>>> wrote:
>>>
>>> >
>>> > Hi all,
>>> >
>>> > I have read about ovs controller and NOX controller, and I learnt
>>> > that
>>> ovs controller is a reference controller while NOX is a remote controller..
>>> >
>>> > I would like to know the difference between reference controller
>>> > and
>>> remote controller..
>>> >
>>> > Highly appreciate your thoughts..
>>> >
>>> > Best Regards,
>>> >
>>> > Windhya Rankothge
>>> > _______________________________________________
>>> > openflow-discuss mailing list
>>> > openflow-discuss@lists.stanford.edu
>>> > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>>>
>>>
>>
>>
>>--
>>Best Regards,
>>
>>Windhya Rankothge..... (WINDY)
>>-------------- next part -------------- An HTML attachment was
>>scrubbed...
>>URL: <http://mailman.stanford.edu/pipermail/openflow-
>>discuss/attachments/20130926/b1cfcdee/attachment-0001.html>
>>
>>------------------------------
>>
>>Message: 3
>>Date: Thu, 26 Sep 2013 12:44:00 +0200
>>From: Windhya Rankothge <windys...@gmail.com>
>>To: "openflow-discuss@lists.stanford.edu"
>>      <openflow-discuss@lists.stanford.edu>
>>Subject: [openflow-discuss] Openflow controller discovery
>>Message-ID:
>>      <CADWQY-fq6coWwqemjDjZRGziRv--
>>4hhnexcwhjemppuz5wc...@mail.gmail.com>
>>Content-Type: text/plain; charset="iso-8859-1"
>>
>>Hi all,
>>
>>As I have read, in openflow topology discovery,  controller sends the
>>LLDP packet to all the connected switches via a packet_out message to
>>discover openflow switches connected to it..
>>
>>If it is a distributed controller environment, i would like to know,
>>how controllers discover each other ?
>>Does this handles by openflow it self ?
>>
>>Highly appreciate your thoughts..
>>
>>
>>Best Regards,
>>
>>Windhya Rankothge.....
>>-------------- next part -------------- An HTML attachment was
>>scrubbed...
>>URL: <http://mailman.stanford.edu/pipermail/openflow-
>>discuss/attachments/20130926/9786cc20/attachment-0001.html>
>>
>>------------------------------
>>
>>Message: 4
>>Date: Thu, 26 Sep 2013 17:07:42 +0530
>>From: shiva m <anjane...@gmail.com>
>>To: Windhya Rankothge <windys...@gmail.com>
>>Cc: "openflow-discuss@lists.stanford.edu"
>>      <openflow-discuss@lists.stanford.edu>
>>Subject: Re: [openflow-discuss] Openflow controller discovery
>>Message-ID:
>>      <CAGm0vUpqgsdwrvBJ2XdfqdkotxLQpMt0PJxfqy=Jq4kkvnV_kQ@ma
>>il.gmail.com>
>>Content-Type: text/plain; charset="iso-8859-1"
>>
>>Hi,
>>
>>As i understand, there are no distributed controllers, you can connect
>>to one or more controllers. Some controllers support active/standby
>>model but as i understand there is no distributed controller support in
>openflow controllers.
>>There may be SDN controllers which supports distributed controllers to
>>create virtual networks.
>>
>>Thanks & Regards,
>>Shiva
>>
>>
>>On Thu, Sep 26, 2013 at 4:14 PM, Windhya Rankothge
>><windys...@gmail.com>wrote:
>>
>>> Hi all,
>>>
>>> As I have read, in openflow topology discovery,  controller sends the
>>> LLDP packet to all the connected switches via a packet_out message to
>>> discover openflow switches connected to it..
>>>
>>> If it is a distributed controller environment, i would like to know,
>>> how controllers discover each other ?
>>> Does this handles by openflow it self ?
>>>
>>> Highly appreciate your thoughts..
>>>
>>>
>>> Best Regards,
>>>
>>> Windhya Rankothge.....
>>>
>>> _______________________________________________
>>> openflow-discuss mailing list
>>> openflow-discuss@lists.stanford.edu
>>> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>>>
>>>
>>-------------- next part -------------- An HTML attachment was
>>scrubbed...
>>URL: <http://mailman.stanford.edu/pipermail/openflow-
>>discuss/attachments/20130926/53f984b8/attachment-0001.html>
>>
>>------------------------------
>>
>>_______________________________________________
>>openflow-discuss mailing list
>>openflow-discuss@lists.stanford.edu
>>https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>>
>>
>>End of openflow-discuss Digest, Vol 59, Issue 28
>>************************************************
>>_______________________________________________
>>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

Reply via email to