Hi, I am examining routing AI of nox. My topology is A-------------------------B-------------------------------C---------------------------D | | -------------E---------------- B, C and E are connected in a triangle fashion. Open flow software is installed in B, C and E. Every interface of B, C and E (triangle fasion interfaces) are added as a datapath interface of opoenflow. B, C and E are connected with one NOX. open flow software is not installed in A and D. A and D are client and server. Routing entry is added in A and D to reach each other. I am sending ping message from A to D. I also examine the flow entries added by nox. So, first, it searches the path to D by flooding the ARP messages. then accurate flow entries comes in each switch. Let the path taken by by the packet is ABCD then if I break the link between B and C. then path should switch to ABECD after hard timeout expires. But in this case, it is not switching after hard timeout. But it waits for end node A to restart ARP request when its base reachable time expires. So it again search the path by flooding the packet. I was thinking that path is available in topology database. and should switch to other path on link failure condition. But this is not happening. So, lots of packets drops in this link failure condition. And also i observe many prints in nox when i do link down and link up. for example received Openflow error packet from dpid=0023208006bd: type=1, code=7, 24 bytes of data Does routing AI just depends on end nodes to restart the recovery on link failure condition. Thanks, Sachin
_______________________________________________ nox-dev mailing list [email protected] http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
