[ClusterLabs] ping Resource Agent doesnt work

2018-07-19 Thread Confidential Company
I configured ping-RA via ocf:pacemaker. During testing the resource-agent works fine, it executes ping action to my gateway every 10 seconds and 3 attempts. But I noticed that even I disconnect the physical link of node where the resource resides, it doesnt failover to other node. *IP CONFIG:*

Re: [ClusterLabs] Weird Fencing Behavior

2018-07-18 Thread Confidential Company
? No defaults set >>>> Operations Defaults: >>>> ? No defaults set >>>> >>>> Cluster Properties: >>>> ? cluster-infrastructure: corosync >>>> ? cluster-name: ARCOSCLUSTER >>>> ? dc-version: 1.1.16-12.el7-94ff4df >>&

Re: [ClusterLabs] Weird Fencing Behavior

2018-07-17 Thread Confidential Company
> > Hi, > > > > On my two-node active/passive setup, I configured fencing via > > fence_vmware_soap. I configured pcmk_delay=0 on both nodes so I > expected > > that both nodes will be stonithed simultaenously. > > > > On my test scenario, Node1 has ClusterIP resource. When I > disconnect > >

[ClusterLabs] Weird Fencing Behavior

2018-07-17 Thread Confidential Company
> Hi, > > On my two-node active/passive setup, I configured fencing via > fence_vmware_soap. I configured pcmk_delay=0 on both nodes so I expected > that both nodes will be stonithed simultaenously. > > On my test scenario, Node1 has ClusterIP resource. When I disconnect > service/corosync link

[ClusterLabs] Weird Fencing Behavior?

2018-07-17 Thread Confidential Company
Hi, On my two-node active/passive setup, I configured fencing via fence_vmware_soap. I configured pcmk_delay=0 on both nodes so I expected that both nodes will be stonithed simultaenously. On my test scenario, Node1 has ClusterIP resource. When I disconnect service/corosync link physically,

[ClusterLabs] What triggers fencing?

2018-07-12 Thread Confidential Company
490...@redhat.com> Content-Type: text/plain; charset=utf-8 On 07/11/2018 04:11 PM, Ken Gaillot wrote: > On Wed, 2018-07-11 at 11:06 +0200, Klaus Wenninger wrote: >> On 07/11/2018 05:48 AM, Andrei Borzenkov wrote: >>> 11.07.2018 05:45, Confidential Company ?: >>>>

Re: [ClusterLabs] What triggers fencing?

2018-07-11 Thread Confidential Company
05:48 AM, Andrei Borzenkov wrote: > 11.07.2018 05:45, Confidential Company ?: >> Not true, the faster node will kill the slower node first. It is >> possible that through misconfiguration, both could die, but it's rare >> and easily avoided with a 'delay="15

Re: [ClusterLabs] What triggers fencing?

2018-07-10 Thread Confidential Company
>>>> On 07/09/2018 03:49 PM, Digimer wrote: > >>>>> On 2018-07-09 08:31 AM, Klaus Wenninger wrote: > >>>>>> On 07/09/2018 02:04 PM, Confidential Company wrote: > >>>>>>> Hi, > >>>>>>> > >>>>&g

[ClusterLabs] What triggers fencing?

2018-07-09 Thread Confidential Company
Hi, Any ideas what triggers fencing script or stonith? Given the setup below: 1. I have two nodes 2. Configured fencing on both nodes 3. Configured delay=15 and delay=30 on fence1(for Node1) and fence2(for Node2) respectively *What does it mean to configured delay in stonith? wait for 15

Re: [ClusterLabs] Resource-stickiness is not working

2018-06-05 Thread Confidential Company
On Sat, 2018-06-02 at 22:14 +0800, Confidential Company wrote: > On Fri, 2018-06-01 at 22:58 +0800, Confidential Company wrote: > > Hi, > >? > > I have two-node active/passive setup. My goal is to failover a > > resource once a Node goes down with minimal downtime a

[ClusterLabs] Resource-stickiness is not working

2018-06-02 Thread Confidential Company
On Fri, 2018-06-01 at 22:58 +0800, Confidential Company wrote: > Hi, > > I have two-node active/passive setup. My goal is to failover a > resource once a Node goes down with minimal downtime as possible. > Based on my testing, when Node1 goes down it failover to Node2. If > N

[ClusterLabs] Resource-stickiness is not working

2018-06-01 Thread Confidential Company
Hi, I have two-node active/passive setup. My goal is to failover a resource once a Node goes down with minimal downtime as possible. Based on my testing, when Node1 goes down it failover to Node2. If Node1 goes up after link reconnection (reconnect physical cable), resource failback to Node1 even

[ClusterLabs] ethmonitor is not working

2018-06-01 Thread Confidential Company
Hi, I have two node active/passive setup. This is my configuration: #service firewalld stop #vi /etc/hosts --> 192.168.2.121 (Node1) / 192.168.2.122 (Node2) - Private Network (Direct connect) #systemctl start pcsd.service #systemctl enable pcsd.service #passwd hacluster --> define pw

[ClusterLabs] ethmonitor RA agent error. How can I fix this? (RHEL)

2018-05-21 Thread Confidential Company
I have two Virtual machines with two network interfaces. See configuration below: *eth0 - service network *eth1 - heartbeat network *vi /etc/hosts - RhelA(ip of eth1) / RhelB(ip of eth1) *service firewalld stop *pcs resource create VirtualIP ocf:heartbeat:IPaddr2 ip=(virtual ip) cidr_netmas=32

[ClusterLabs] ethmonitor configuration

2018-05-17 Thread Confidential Company
Hi, 1. What are the configurations on ethmonitor if I want to setup a two nic (data and heartbeat), I have virtualIP resource, and this virtualIP should only run on a node the ethmonitor resource tells the ethernet device is up on? 2. What is the minimum monitoring interval of ethmonitor RA?

[ClusterLabs] Two-node cluster fencing

2018-05-13 Thread Confidential Company
5.2018 07:31, Confidential Company ?: > Hi, > > This is my setup: > > 1. I have Two vMware-ESXI hosts with one virtual machine (RHEL 7.4) on each. > 2. On my physical machine, I have four vmnic --> vmnic 0,1 for uplink going > to switchA and switchB --> vmnic 2,3 for heart

[ClusterLabs] Two-node cluster fencing

2018-05-11 Thread Confidential Company
Hi, This is my setup: 1. I have Two vMware-ESXI hosts with one virtual machine (RHEL 7.4) on each. 2. On my physical machine, I have four vmnic --> vmnic 0,1 for uplink going to switchA and switchB --> vmnic 2,3 for heartbeat corosync traffic (direct connect to other ESXI host) 3. I plan on