Hi Ben, I've manged to figure out what the problem is. For some reason ovs-appctl did not log all information -- after setting the verbose flag and the log-file path, I noticed that ovs-vswitchd had been running out of file descriptors. Increasing the maximum number of open FDs fixed the problem.
Thanks for your help! On Sat, May 12, 2012 at 1:19 PM, Ben Pfaff <b...@nicira.com> wrote: > On Fri, May 11, 2012 at 09:35:57PM -0700, Vjekoslav Brajkovic wrote: >> I'm running into a problem that should not be happening. According to >> the ovs-dpctl manpage, a single machine may host up to 256 datapaths >> (numbered 0 to 255). >> >> I'm successively creating a switch and specifying the same controller >> for each of them. In a nutshell: >> >> for n in nodes: # length(nodes) = 100 >> command_create = 'ovs-vsctl add-br sw%s' %(n) >> execute(command_create) >> command_set = 'ovs-vsctl set-controller sw%s tcp:127.0.0.1' %(n) >> execute(command_set) >> >> Syslog does not report anything out of ordinary (ovs-appctl vlog/set >> ANY:ANY:dbg): >> >> ... >> [84876.575065] device sw70 entered promiscuous mode >> [84878.019359] device sw79 entered promiscuous mode >> [84879.115090] device sw78 entered promiscuous mode >> >> >> However, on the controller side, only 50 switches end up registering >> with the controller no matter what I do. If I remove one of the >> connected switches, a new (51th) switch instantiates a connection >> towards the controller. > > There's no 50-datapath limit. There's not even really a 256-datapath > limit. > > What version of OVS are you using? _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
