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
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?
Oh, with switch, I use the port_status_change event and clear flow
rules (and the archived Mac_source for the port).
2) There
Hi Srini,
1) The archived port would be the same port?
2) My point precisely. So, what does clearing the flow entries achieve here?
I contend that custom controllers might want to implement this
flushing on their own. The patch is probably most useful as a
component that other controllers can
PM
Subject: Re: [nox-dev] working of switch api on link failure
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?
Oh, with switch, I use the port_status_change event and clear
Seetharaman seeth...@stanford.edu
To: kk yap yap...@stanford.edu
Cc: sachin sharma sharon_sac...@yahoo.co.in; nox-dev@noxrepo.org
Sent: Mon, 6 December, 2010 9:43:43 PM
Subject: Re: [nox-dev] working of switch api on link failure
Pardon my laziness in not reading the patches. I am confused here
Sachin brought up a valid point that the switch and routing modules
are lacking on actions to take when a port or link goes down. Note
that the code available right now in NOX may cause packet loss if the
dst host moved to a new location and stays silent at the new location
(Ageing or host table
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
