Hi,

Pardon my laziness in not reading the patches.  I am confused here.  Two points:
1) Switch does not depend on topology or discovery, so how do you get
link failure?

2) There is no spanning tree implementation in NOX (distributed by
default), i.e., you cannot have a redundant network with NOX.  So, how
can you possibly hope to find the host on a different route when a
link failure occurs?  On that note, why does handling link failure
even matters?

Regards
KK

On 6 December 2010 12:14, Srini Seetharaman <seeth...@stanford.edu> wrote:
> Hi Sachin
> You raise a good point. There is no code that performs the needed
> cleanup on link failure. I've attached two patch files that shud work
> for the switch module and the routing module. This will clear the flow
> rules on the switch for that out_port that went down, and also clear
> any learned MAC address (in case of the switch module).
>
> The code is not necessarily optimized. But, it has been tested to work
> fine with HP switches in a small lab setup. Please let us know whether
> this solves your problem.
>
> NOX-Admins - Please accept this patch if you find it worthwhile.
>
> Thanks
> Srini.
>
> On Fri, Nov 26, 2010 at 7:09 AM, sachin sharma
> <sharon_sac...@yahoo.co.in> wrote:
>> Hi,
>> I have gone through the switch api of code at nox
>> (/home/user/newnox/src/nox/coreapps/switch/switch.cc)  but i do not find any
>> action of switch on link failure.
>>
>>  when i run nox with this switch api then flow entries are getting added in
>> openvswitch. But when I make one of outgoing link down. then after some
>> time, older flow entry gets vanishes and new flow entry is getting added in
>> my flow table with available port. But new entry addition time is greater
>> than flow expired time ( in my case it is 50 seconds).
>>
>> But I am not able to find the code in nox which does this action on link
>> failure.  Can anyone explain me that which part of code at nox is called
>> when nox detects link failure on any datapath port.
>>
>> Thank You!
>> Sachin Sharma
>>
>>
>>
>>
>> _______________________________________________
>> nox-dev mailing list
>> nox-dev@noxrepo.org
>> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>>
>>
>
> _______________________________________________
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>
>

_______________________________________________
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

Reply via email to