HA back and forth prio levels change backup does not remain master...



  • Hello,

    Banging our heads againts the wall over this...

    We have a Vmware redundant setup. If we put the master in CARP maintenance mode, we see the following:

    00:00:03.079240 IP xx.xx.xx.19 > 224.0.0.18: VRRPv2, Advertisement, vrid 1, prio 0, authtype none, intvl 5s, length 36
    00:00:03.056511 IP xx.xx.xx.19 > 224.0.0.18: VRRPv2, Advertisement, vrid 1, prio 0, authtype none, intvl 5s, length 36
    00:00:07.734300 IP xx.xx.xx.19 > 224.0.0.18: VRRPv2, Advertisement, vrid 1, prio 0, authtype none, intvl 5s, length 36
    Primary: master to backup:
    00:00:02.134324 IP xx.xx.xx.19 > 224.0.0.18: VRRPv2, Advertisement, vrid 1, prio 240, authtype none, intvl 5s, length 36
    Secondary:
    00:00:00.000222 IP xx.xx.xx.20 > 224.0.0.18: VRRPv2, Advertisement, vrid 1, prio 100, authtype none, intvl 5s, length 36
    Primary switches again....
    00:00:01.624149 IP xx.xx.xx.19 > 224.0.0.18: VRRPv2, Advertisement, vrid 1, prio 0, authtype none, intvl 5s, length 36
    00:00:04.997838 IP xx.xx.xx.19 > 224.0.0.18: VRRPv2, Advertisement, vrid 1, prio 0, authtype none, intvl 5s, length 36
    00:00:05.250706 IP xx.xx.xx.19 > 224.0.0.18: VRRPv2, Advertisement, vrid 1, prio 0, authtype none, intvl 5s, length 36
    And so on, this keeps on switching...

    What this does is letting the virtual ip's constantly switch between the two systems... If we leave maintenance mode, the primary is stable master and the backup stays backup... Also if we restart the master, the backup is relucant to go to master... Only if we turn of the master after some time (minutes) it will be master.

    What can we do? We run 2.4.5 latest...



  • Interesting,

    00:00:00.294065 IP xx.xx.xx.19 > 224.0.0.18: VRRPv2, Advertisement, vrid 1, prio 0, authtype none, intvl 5s, length 36
    00:00:00.715554 IP xx.xx.xx..19 > 224.0.0.18: VRRPv2, Advertisement, vrid 1, prio 0, authtype none, intvl 1s, length 36

    If i change the frequency, looks like the deamon stays alive an starts a new one and i see the old and new times, so maybe a prio0 stays broadcasting also during a failover?

    00:00:00.574783 IP xx.xx.xx..19 > 224.0.0.18: VRRPv2, Advertisement, vrid 1, prio 240, authtype none, intvl 1s, length 36
    00:00:01.965796 IP xx.xx.xx..19 > 224.0.0.18: VRRPv2, Advertisement, vrid 1, prio 240, authtype none, intvl 1s, length 36
    00:00:01.363018 IP xx.xx.xx..19 > 224.0.0.18: VRRPv2, Advertisement, vrid 1, prio 0, authtype none, intvl 1s, length 36
    00:00:00.583826 IP xx.xx.xx..19 > 224.0.0.18: VRRPv2, Advertisement, vrid 1, prio 240, authtype none, intvl 1s, length 36
    00:00:00.283089 IP xx.xx.xx..19 > 224.0.0.18: VRRPv2, Advertisement, vrid 1, prio 0, authtype none, intvl 1s, length 36
    00:00:00.845702 IP xx.xx.xx..19 > 224.0.0.18: VRRPv2, Advertisement, vrid 1, prio 0, authtype none, intvl 1s, length 36
    00:00:00.827872 IP xx.xx.xx..19 > 224.0.0.18: VRRPv2, Advertisement, vrid 1, prio 240, authtype none, intvl 1s, length 36

    Thats what its doing, so the backup is not responding... (this is when maintenance mode is clicked)


Log in to reply