Hi Srini, Thanks very much, I will try. It's a good suggestion. xiefeng 2010/12/29 Srini Seetharaman <[email protected]>
> I'm not sure if this is a problem of spanning_tree module. The ping > may be stopped because the switch is holding onto flow table entries > with invalid output action, and thereby not generating the packet_in > to the controller (A pkt_in is needed for the routing module to send > updated flow_mods with the valid output). > > The routing module depends on the topology module to get updated > topology. This takes a long time because the link timeout value is > high. > > Even if the topology changes, the routing module will not revoke > existing invalid flow_mods. You will have to write the code for that. > The routing module needs to listen for port status change messages to > act immediately if there's a link failure. Please look at the > following thread for more info on that: > http://www.mail-archive.com/[email protected]/msg01963.html > > Srini. > > On Tue, Dec 28, 2010 at 9:27 AM, 谢峰 <[email protected]> wrote: > > Hi,all > > The spanning_tree component can break the loop in the network, select the > > shortest path for the flow. But when I cut the shortest path, the ping > > operation will stop, it represents that the nox doesn't > > select another path for me. So, how solve this problem: if I want to > change > > a new route immediately when the current path is down? > > thanks > > regards > > xiefeng > > _______________________________________________ > > nox-dev mailing list > > [email protected] > > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org > > > > > -- Feng Xie Ph.D. Candidate Network Security Lab, Research Institute of Information Technology Tsinghua National Laboratory for Information Science and Technology Dept. of Automation, Tsinghua Univ., Beijing, China, 100084. Tel.: +86-010-6277-2656 Email: [email protected]
_______________________________________________ nox-dev mailing list [email protected] http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
