On Sat, 2018-05-12 at 12:51 -0600, Casey & Gina Shobe wrote:
> Without fencing, if the primary is powered off abruptly (e.g. if one
> of your ESX servers crashes), the standby will not become primary,
> and you will need to promote it manually. We had exactly this
> scenario happen last week with
Message: 2
Date: Sun, 13 May 2018 10:20:36 +0300
From: Andrei Borzenkov <arvidj...@gmail.com>
To: users@clusterlabs.org
Subject: Re: [ClusterLabs] Two-node cluster fencing
Message-ID: <f61a61bc-f618-bdb1-ee1a-bc5e856c8...@gmail.com>
Content-Type: text/plain; charset=utf-8
12.0
12.05.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 heartbeat corosync
Without fencing, if the primary is powered off abruptly (e.g. if one of your
ESX servers crashes), the standby will not become primary, and you will need to
promote it manually. We had exactly this scenario happen last week with a
2-node cluster. Without fencing, you don't have high
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
