On Mon, Jan 22, 2018 at 10:09 PM, brainheadz wrote:
> Hello Andrei,
>
> yes this fixes the issue. But is there a way to automate this process
> without a manual intervention?
>
Normally adding and removing this constraint is manual process by
design. Do you mean this constraint appears again with
Hello Andrei,
yes this fixes the issue. But is there a way to automate this process
without a manual intervention?
Node1 fails.
Node2 takes over the vip_bad and ipsrcaddr.
Node1 is back online.
vip_bad and ipsrcaddr are moved back to Node1.
Node2 sets the correct default_gw and it's own sourc
22.01.2018 20:54, brainheadz пишет:
> Hello,
>
> I've got 2 public IP's and 2 Hosts.
>
> Each IP is assigned to one host. The interfaces are not configured by the
> system, I am using pacemaker to do this.
>
> fw-managed-01: 100.200.123.166/29
> fw-managed-02: 100.200.123.165/29
>
> gateway: 10
Hello,
I've got 2 public IP's and 2 Hosts.
Each IP is assigned to one host. The interfaces are not configured by the
system, I am using pacemaker to do this.
fw-managed-01: 100.200.123.166/29
fw-managed-02: 100.200.123.165/29
gateway: 100.200.123.161
I am trying to get some form of active/pass
