Re: [Pacemaker] how to test network access and fail over accordingly?

2010-10-07 Thread Craig Hurley
Yesterday, the last few emails between Vadym and I were inadvertently not posted to this list. Here are those posts for anyone having similar issues. Regards, Craig. On 7 October 2010 15:20, Vadym Chepkov wrote: > no, default is 0 - it is not taken into consideration at all. > Resource stays in

Re: [Pacemaker] how to test network access and fail over accordingly?

2010-10-06 Thread Andrew Beekhof
On Wed, Oct 6, 2010 at 10:21 PM, Craig Hurley wrote: > I tried using ping instead of pingd and I added "number" to the > evaluation, I get the same results :/ > > primitive p_ping ocf:pacemaker:ping params host_list=172.20.0.254 > clone c_ping p_ping meta globally-unique=false > location loc_ping

Re: [Pacemaker] how to test network access and fail over accordingly?

2010-10-06 Thread Vadym Chepkov
On Oct 6, 2010, at 4:21 PM, Craig Hurley wrote: > I tried using ping instead of pingd and I added "number" to the > evaluation, I get the same results :/ > > primitive p_ping ocf:pacemaker:ping params host_list=172.20.0.254 > clone c_ping p_ping meta globally-unique=false > location loc_ping g_c

Re: [Pacemaker] how to test network access and fail over accordingly?

2010-10-06 Thread Craig Hurley
I tried using ping instead of pingd and I added "number" to the evaluation, I get the same results :/ primitive p_ping ocf:pacemaker:ping params host_list=172.20.0.254 clone c_ping p_ping meta globally-unique=false location loc_ping g_cluster_services rule -inf: not_defined p_ping or p_ping number

Re: [Pacemaker] how to test network access and fail over accordingly?

2010-10-06 Thread Vadym Chepkov
On Oct 6, 2010, at 3:43 AM, Jayakrishnan wrote: > > Hello, > > Guess the change:-- > location loc_pingd g_cluster_services rule -inf: not_defined pingd or pingd > number:lte 0 > > should work > > > ocf:pacemaker:ping is recommended as a replacement for pingd RA Both RA define node a

Re: [Pacemaker] how to test network access and fail over accordingly?

2010-10-06 Thread Jayakrishnan
Hello, Guess the change:-- location loc_pingd g_cluster_services rule -inf: not_defined pingd or pingdnumber:lte 0 should work -- Regards, Jayakrishnan. L Visit: www.foralllinux.blogspot.com www.jayakrishnan.bravehost.com On Wed, Oct 6, 2010 at 11:56 AM, Claus Denk wrote: > I am having

Re: [Pacemaker] how to test network access and fail over accordingly?

2010-10-05 Thread Claus Denk
I am having a similar problem, so let's wait for the experts, But in the meanwhile, try changing location loc_pingd g_cluster_services rule -inf: not_defined p_pingd or p_pingd lte 0 to location loc_pingd g_cluster_services rule -inf: not_defined pingd or pingd number:lte 0 and see what happ

[Pacemaker] how to test network access and fail over accordingly?

2010-10-05 Thread Craig Hurley
Hello, I have a 2 node cluster, running DRBD, heartbeat and pacemaker in active/passive mode. On both nodes, eth0 is connected to the main network, eth1 is used to connect the nodes directly to each other. The nodes share a virtual IP address on eth0. Pacemaker is also controlling a custom servi