How to implement two mutual exclusive VIPs about keepalived HOT 4 CLOSED

It is the similar with vrrp_sync_group that one track_script supports 2 binding VIPs that are always on one machine.
While what we need is the one track_script supports 2 binding VIPs that are always on different machines.

from keepalived.

The following configuration outline may meet your needs. You haven't stated what you want to happen if one machine fails; with the configuration below the other machine will have both VIPs.

On machine A:

vrrp_vip1 {
    virtual_router_id 1
    priority 100
    virtual_ipaddress {
      VIP1
    }
   .
   .
   .
}

vrrp_vip2 {
    virtual_router_id 2
    priority 50
    virtual_ipaddress {
      VIP2
    }
   .
   .
   .
}

and on machine B:

vrrp_vip1 {
    virtual_router_id 1
    priority 50
    virtual_ipaddress {
      VIP1
    }
   .
   .
   .
}

vrrp_vip2 {
    virtual_router_id 2
    priority 100
    virtual_ipaddress {
      VIP2
    }
   .
   .
   .
}

If both machines are operating normally, machine A will have VIP1 and machine B will have VIP2. If either machine fails, then the other machine will have both VIPs; I am not clear if that is what you want.

from keepalived.

@pqarmitage
Thanks for your quick help.
If both machines are operating normally, it is what I need.

How can we get that there is no VIP2 on the machine A when the machine B fails?
Thanks again

from keepalived.

I think your solution is not to use VRRP at all but simply manually configure the relevant addresses on machine A and machine B.

from keepalived.