Aaron:

With the exception of HPs, most openflow switches make you manually
configure your dpid as part of the OpenFlow setup.  Normally this is
were the error occurs: that the person who set them up accidentally
assigned two switches the same dpid.

Ben's point is that nox actually (or at least used to) ignores the top
two bytes of the dpid (for historical reasons), so it's possible that
you don't have identical dpids, but dpids that only differ in the
bytes that nox ignores.

- Rob
.



On Thu, Jul 14, 2011 at 3:14 PM, Aaron Rosen <[email protected]> wrote:
> Hi Srini,
>
> I'm actually using destiny with last commit
> 2ae77a972bb99f35ba3da397b98c2857f41c7f78 .
>
> Though I'm running with a patch that Murphy gave me to to handle an
> LLDP  issue that I was having supposedly because  FV encodes large
> DPIDs differently (though I'm not really to sure about the details
> here).
>
> Murphy, do you think this is related to that patch I got from you a while ago?
>
> Thanks,
>
> Aaron
>
> On Thu, Jul 14, 2011 at 6:07 PM, Srini Seetharaman
> <[email protected]> wrote:
>> I believe NOX-Zaku still has issues in the discovery module with handling
>> 64-bit DPID. That must be your issue. Maybe James can confirm.
>> What is the commit tag of the NOX-zaku release you're using?
>>
>> On Thu, Jul 14, 2011 at 3:04 PM, Ben Pfaff <[email protected]> wrote:
>>>
>>> On Thu, Jul 14, 2011 at 06:02:36PM -0400, Aaron Rosen wrote:
>>> > Also, is it possible for two hardware switches to have the same dpid ?
>>> > (Assuming that the manufacture didn't make duplicates. The hp switch
>>> > here is making the dpid (vlan + mac) I believe ) .
>>>
>>> Sounds like a familiar problem, is it the one here?
>>>        http://noxrepo.org/pipermail/nox-dev/2010-June/006210.html
>>> _______________________________________________
>>> openflow-discuss mailing list
>>> [email protected]
>>> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>>
>>
>
>
>
> --
> Aaron O. Rosen
> Masters Student - Network Communication
> 306B Fluor Daniel
> _______________________________________________
> openflow-discuss mailing list
> [email protected]
> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>
_______________________________________________
openflow-discuss mailing list
[email protected]
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss

Reply via email to