No, I think the latter --controller just overrides the former. I don't actually think there's a decent way to do this in Mininet. In earlier versions, I think there was missing infrastructure. In Mininet 2, I think there's still some stuff missing and you could almost make it work except for a bug in how it formats the ovs-vsctl commandline.
So the way to do this is really to just invoke ovs-vsctl yourself manually. Let Mininet set up OVS and your topology. Then assuming you have switches s1 and s2, do something like: ovs-vsctl set-controller s1 tcp:192.168.129.57:6633 tcp:192.168.129.56:6633 ovs-vsctl set-controller s2 tcp:192.168.129.57:6633 tcp:192.168.129.56:6633 Hope that helps. (BTW, you might want to ask this on the mininet list.) -- Murphy On Apr 16, 2013, at 3:36 PM, Karthik Sharma wrote: > I am using a mininet topology with a remote controller. However I want to > specify another redundant controller as a fallback option. Can I do as follows > > mn --custom topo-1sw-2host.py --topo mytopo --controller=remote > --ip=192.168.129.56 --ip=192.168.129.57. > > Mininet seems to accept the above command.I want the controller > > 192.168.129.57 to take over when 192.168.129.56 goes offline. > > Does this work? > > Regards, > > Karthik. >
