Hi Liew,
I don't think it's the right behavior that a switch stops the packets from the hosts since the connection to the controller is lost. Because OpenFlow Spec 1.3.4 says that the switch must immediately enter either "fail secure mode" or "fail standalone mode", if all the connection to the controller is lost. In "fail secure mode", flow entries should continue to expire according to their timeouts. And the switch acts as a legacy Ethernet switch or router in "fail standalone mode". Please refer to the "6.3.3 Connection Interruption" in OpenFlow Spec 1.3.4. So, if you want to stop ping between the hosts, you have to implement your app in order to make the switches act so, or configure your switches. Thanks, Iwase On 2015年05月27日 02:29, Liew G.H. wrote: > Hi all! > I'm trying to test 2 Ryu controllers to connect to a custom mininet topology > (h1, s3) (s3, s4) (s4, h2) using the command: >>> sudo mn --custom topo-2sw-2host.py --topo mytopo --controller >>> remote,port=6633 --switch ovsk,protocols=OpenFlow13 > > Using the command to start 2 Ryu controllers on two different instances: >>> PYTHONPATH=. ./bin/ryu-manager --verbose ryu/app/simple_switch_13.py > > And connect the 2 Ryu controllers to the Mininet: >>> sudo ovs-vsctl set-controller s3 tcp:10.180.133.200:6633 >>> sudo ovs-vsctl set-controller s4 tcp:10.235.19.235:6633 > > The result, Mininet hosts h1 and h2 were able to ping each other. However, > when one of the Ryu controller is stopped (using Ctrl+z or Ctrl+c) and stop > the listening port 6633 (sudo fuser -k 6633/tcp), the Mininet hosts still > able to ping each other. By right, the hosts are unable to ping each other > since one of the controller is stopped. Even so, I tried stop both the Ryu > controllers and the Mininet hosts were still able to ping each other. > Below are the netstat of the Mininet instance before and after stopping the > Ryu controllers: > > a.) Before stopping Ryu > Active Internet connections (w/o servers) > Proto Recv-Q Send-Q Local Address Foreign Address State > tcp 0 432 ip-10-235-51-206.ec:ssh 175.145.212.28:54163 > ESTABLISHED > tcp 0 0 ip-10-235-51-206.ec:ssh 175.145.212.28:54137 > ESTABLISHED > tcp 0 0 ip-10-235-51-206.:54492 ip-10-180-133-200.:6633 > ESTABLISHED > tcp 0 0 ip-10-235-51-206.:40908 ip-10-235-19-235.e:6633 > ESTABLISHED > > b.) Stop 1 Ryu controller > Active Internet connections (w/o servers) > Proto Recv-Q Send-Q Local Address Foreign Address State > tcp 0 496 ip-10-235-51-206.ec:ssh 175.145.212.28:54163 > ESTABLISHED > tcp 0 0 ip-10-235-51-206.ec:ssh 175.145.212.28:54137 > ESTABLISHED > tcp 0 0 ip-10-235-51-206.:40908 ip-10-235-19-235.e:6633 > ESTABLISHED > > c.) Stop all Ryu controllers > Active Internet connections (w/o servers) > Proto Recv-Q Send-Q Local Address Foreign Address State > tcp 0 432 ip-10-235-51-206.ec:ssh 175.145.212.28:54163 > ESTABLISHED > tcp 0 0 ip-10-235-51-206.ec:ssh 175.145.212.28:54137 > ESTABLISHED > > #The Mininet are still able to ping each other: > mininet> pingall > *** Ping: testing ping reachability > h1 -> h2 > h2 -> h1 > *** Results: 0% dropped (2/2 received) > mininet> h1 ping h2 > PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. > 64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=0.053 ms > 64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.091 ms > 64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=0.080 ms > 64 bytes from 10.0.0.2: icmp_seq=4 ttl=64 time=0.074 ms > 64 bytes from 10.0.0.2: icmp_seq=5 ttl=64 time=0.077 ms > 64 bytes from 10.0.0.2: icmp_seq=6 ttl=64 time=0.079 ms > 64 bytes from 10.0.0.2: icmp_seq=7 ttl=64 time=0.080 ms > 64 bytes from 10.0.0.2: icmp_seq=8 ttl=64 time=0.079 ms > ^C > --- 10.0.0.2 ping statistics --- > 8 packets transmitted, 8 received, 0% packet loss, time 6998ms > rtt min/avg/max/mdev = 0.053/0.076/0.091/0.014 ms > > I'm sorry but I'm new to Ryu controller, may I ask is there any way to really > shut Ryu controller completely? > > Thanks, > Liew GH > > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > > > > _______________________________________________ > Ryu-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ryu-devel > ------------------------------------------------------------------------------ _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
