Home
Help
Search
Login
Register
OPNsense Forum
»
English Forums
»
High availability
»
Current CARP demotion level = 0 to both FW is it correct ? SOLVED
« previous
next »
Print
Pages: [
1
]
Author
Topic: Current CARP demotion level = 0 to both FW is it correct ? SOLVED (Read 4784 times)
andrema2
Jr. Member
Posts: 96
Karma: 3
Current CARP demotion level = 0 to both FW is it correct ? SOLVED
«
on:
July 26, 2021, 04:50:17 am »
Hi,
I have two FW running OPNsense 21.1.8_1-amd64.
Both Master and Backup have Current CARP demotion level = 0. I thought one should be with 240.
I tried to set it to sysctl net.inet.carp.demotion=240 but then at the Virtual IP status it says CARP has detected a problem and this unit has been demoted to BACKUP status. Which it already had. Now the CARP demotion is 240.
If I reboot it, it changes again to 0. The CARP seems to be working. As soon as I reboot the MASTER the BACKUP assumes as MASTER. When the Master returns, it does become the MASTER, but both keep with 0 as CARP Demotion.
Also, at this moment I have 4 pfsync nodes at the MASTER and 5 at the BACKUP. I also don't know if it's a problems
Thanks for your help and advice
«
Last Edit: July 27, 2021, 03:52:22 am by andrema2
»
Logged
mimugmail
Hero Member
Posts: 6767
Karma: 494
Re: Current CARP demotion level = 0 to both FW is it correct ?
«
Reply #1 on:
July 26, 2021, 06:06:17 am »
Both should have 0 and the skew decides which is master. Only when you force maintenance mode or have an interface event it gets +240
Logged
WWW:
www.routerperformance.net
Support plans:
https://www.max-it.de/en/it-services/opnsense/
Commercial Plugins (German):
https://opnsense.max-it.de/
andrema2
Jr. Member
Posts: 96
Karma: 3
Re: Current CARP demotion level = 0 to both FW is it correct ?
«
Reply #2 on:
July 27, 2021, 03:51:16 am »
Thanks
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
English Forums
»
High availability
»
Current CARP demotion level = 0 to both FW is it correct ? SOLVED