OPNsense Forum

English Forums => High availability => Topic started by: timo-fc on August 10, 2021, 12:12:07 pm

Title: CARP demotion level of -240 on backup
Post by: timo-fc on August 10, 2021, 12:12:07 pm

Hi,
after an update to the current Version (21.7.1) from some versions behind, I get some times a CARP demotion level of -240 on backup OPNSense.

On an error the demotion level is increased by 240. So far, so good but, if the demotion level is decreased it doesn't stop at 0 instead went down to -240. This causes the backup firewall to take over the carp IPs

Code: [Select]

vtnet0: deletion failed: 3
vtnet0: deletion failed: 3
vtnet0: deletion failed: 3
carp: 27@vtnet0: BACKUP -> INIT (hardware interface up)
carp: 27@vtnet0: INIT -> BACKUP (initialization complete)
vtnet2: deletion failed: 3
vtnet2: deletion failed: 3
vtnet2: deletion failed: 3
carp: 200@vtnet2: BACKUP -> INIT (hardware interface up)
carp: 200@vtnet2: INIT -> BACKUP (initialization complete)
pflog0: permanently promiscuous mode enabled
carp: demoted by -480 to 0 (sysctl)
carp: demoted by -240 to -240 (pfsync bulk fail)
carp: 24@vtnet0: BACKUP -> MASTER (preempting a slower master)
carp: 200@vtnet2: BACKUP -> MASTER (preempting a slower master)
carp: 17@vtnet0: BACKUP -> MASTER (preempting a slower master)

How can I fix this behavior or further investigate the cause?

Thanks

Title: Re: CARP demotion level of -240 on backup
Post by: timo-fc on August 24, 2021, 04:14:50 pm

Hi,
the problem seems to be fixed.
The solution was a new installation of the OPNSense and an import from the configuration backup.