Thanks for the tips on the constraint rules.
I currently have two separate constraint for each ethmonitor - I did not
realise that you could have a constraint rule that can combine multiple
ethmonitors.
Based on your suggestion, I have now used one constraint, as such:
score=-INFINITY
I have tried both ifdown and using vmware to disconnect the interface from
the VM.
It is likely a constraint issue, as I don't have much experience with
corosync/pacemaker.
On Thu, 15 Aug 2019 at 14:01, Jan Pokorný wrote:
> On 15/08/19 10:59 +0100, solarmon wrote:
> > I have a two node cluster
On Thu, 2019-08-15 at 10:59 +0100, solarmon wrote:
> Hi,
>
> I have a two node cluster setup where each node is multi-homed over
> two separate external interfaces - net4 and net5 - that can have
> traffic load balanced between them.
>
> I have created multiple virtual ip resources (grouped
On 15/08/19 10:59 +0100, solarmon wrote:
> I have a two node cluster setup where each node is multi-homed over two
> separate external interfaces - net4 and net5 - that can have traffic load
> balanced between them.
>
> I have created multiple virtual ip resources (grouped together) that should
>
Hi,
I have a two node cluster setup where each node is multi-homed over two
separate external interfaces - net4 and net5 - that can have traffic load
balanced between them.
I have created multiple virtual ip resources (grouped together) that should
only be active on only one of the two nodes.
I
