Hello Vlamdir, you need to change settings in global settings, Go to your global settings in your cloudstack and search for "host", i m sure it will be your 1st management ip( x.x.x.1) , so remove this out and put the virtual ip ( Load balancer IP- x.x.x.3 ) in host section and then restart all cloudstack services on both of yours management server.
*Vivek Kumar* Virtualization and Cloud Consultant [image: http://www.indiqus.com/images/logo.jpg] <http://www.indiqus.com/> *I*ndi*Q*us Technologies Pvt Ltd A-98, LGF, C.R.Park, New Delhi - 110019 *O* +91 11 4055 1411 | *M* +91 7503460090 www.indiqus.com <http://www.indiqus.com/> On Sun, Dec 4, 2016 at 2:02 AM, Vladimir Melnik <[email protected]> wrote: > Dear colleagues, > > Would you be so kind as to share your experience of running multiple > servers? > > I have 2 management servers, they have different IP-addresses (x.x.x.1, > x.x.x.2) and there are also a common IP-address (x.x.x.3) that is being > provided by a load-balancer (haproxy). Also I have some hosts and some > system VMs, they all connect to x.x.x.1, because x.x.x.1 was the > management-server who was used to set-up the zone. > > It's easy to let the hosts know that they need to connect to x.x.x.3, as > this parameter is being set in agent.properties, but where to change it in > the system VMs? Grep haven't found x.x.x.1 anywhere but the log-files. > Moreover, if I destroy and create the system VMs, they'll keep establishing > connections to x.x.x.1. How to change their behaviour? > > Had I add "-m x.x.x.3" when I was running cloudstack-setup-database to > prevent that? It's a new setup, so it's still okay to reset it. :) > > Thanks to all for sharing clues and hints! > > -- > V.Melnik >
