Hi Ben and Justin, Thanks for the reply. Yes I have a set of controllers IPs, which would take control in case of primary controller failure. Maybe setting more than one would fit. How could I do it, I tried separating with comma like "ovs-vsctl set-controller br0 tcp:xxx.xxx.xxx.xxx:6633,tcp:yyy.yyy.yyy.yyy:6633". But just the first controller is contacted, even when I shut the first down the second is not contacted. I didn't found googling.
Regards., -- Jesus, Wanderson We don't currently allow setting the controller based on name mostly due to > in-band control rules. We effectively would need to whitelist all DNS > traffic when a switch is connected in-band, which means controller writers > wouldn't be able to write DNS flows (at least to the configured DNS > server). Is there a set of controller IPs? If so, then you could > configure more than one. > > --Justin > > > On Dec 7, 2012, at 9:06 AM, Wanderson Paim <[email protected]> > wrote: > > > Hi, > > > > I'm trying a loadbalancer implementation with DNS and I need to set the > controller of the vswitch as a domain name instead of its IP address. > > > > Example: > > ovs-vsctl set-controller br0 tcp:controllerx:6633 > > > > Such "controllerx" has the appropriate IP reference of the controller at > the DNS Server. I also tried setting it at /etc/hosts. I always got the > same error shown at "ovs-vsctl list controller": > > ... > > status : last_error="Address family not supported by protocol" > > ... > > > > Is there any way to use controller name instead of IP address in the > "ovs-vsctl set-controller" command? If not is there an alternative? > > > > Regards., > > > > -- > > Jesus, Wanderson > > > > _______________________________________________ > > discuss mailing list > > [email protected] > > http://openvswitch.org/mailman/listinfo/discuss > >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
