Re: [Pacemaker] Basic Clone IP configuration not starting automatically

2015-02-09 Thread Net Warrior
I solved the issue: I had to configure resrouce-stickness option to 0 and now whatever hosts I reboot the resources are back and stay like this: ClusterVIP:0 (ocf::heartbeat:IPaddr2): Started haproxy01 ClusterVIP:1 (ocf::heartbeat:IPaddr2): Started haproxy02 Rega

Re: [Pacemaker] Basic Clone IP configuration not starting automatically

2015-02-06 Thread Net Warrior
Hi Michael. I mean this, when I reboot the server., pacemaker starts automatically but I do no see the VIP in the eth0, sorry I used the word alias which may have lead to a confision. ip addr show 1: lo: mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00

Re: [Pacemaker] Basic Clone IP configuration not starting automatically

2015-02-05 Thread Michael Schwartzkopff
Am Donnerstag, 5. Februar 2015, 14:33:52 schrieb Net Warrior: > Hi there guys. (...) > If I do an sshd to the VIP I can see the round robin is woking and it > switches bettween hosts and I can see of course the alias created on the > eth0 iface. > > My problem is that when I reboot a server to tes

[Pacemaker] Basic Clone IP configuration not starting automatically

2015-02-05 Thread Net Warrior
Hi there guys. I'm new to pacemaker and I'm trying to accomplish an active/active cluster with a VIP ip address, I used the java frontend for the initial setup, I'm using LCMC-1.7.6.jar. This is what I've got: CentOS release 6.5 pacemaker-libs-1.1.10-14.el6_5.3.x86_64 pacemaker-cli-1.1.10-14.el6_