CARP role doesn't switch properly after updating to 19.1.8

Started by bitmusician, May 23, 2019, 11:17:10 AM

Previous topic - Next topic

System log of master when you entering mnt mode please
WWW: www.routerperformance.net
Support plans: https://www.max-it.de/en/it-services/opnsense/
Commercial Plugins (German): https://opnsense.max-it.de/

I found a HA cluster running 19.1.7 live, I compared sysctl before, while and after mnt mode .. on master and slave, for 19.1.7, 19.1.10 and 19.7.2. It worked as expected on all version, no stucks, nothing.

I can upload all files if needed.
WWW: www.routerperformance.net
Support plans: https://www.max-it.de/en/it-services/opnsense/
Commercial Plugins (German): https://opnsense.max-it.de/

damn.. thats so strange - currently have no idea
Is that HA cluster virtualized on ESXi?

No, Hardware, old school :8
WWW: www.routerperformance.net
Support plans: https://www.max-it.de/en/it-services/opnsense/
Commercial Plugins (German): https://opnsense.max-it.de/

I've got the feeling that something did change with that whole
- ESXi
- Portgroup
- Net.ReversePathFwdCheckPromisc
- Promicious Mode
- LAG / no LAG
- LoadBalancing Hash based / Originating interface

But what I don't understand is what changed in that case with 19.1.8

In 19.1.7 maintenance mode was set some way of disable carp, with this you had a 3 times packet loss within migration time. In 19.1.8 this was changed to higher the demotion on the master to force a switch, which works without packet loss.

If your demotions are not even from the beginning it wont work, so 99% of the times it's a config error.
WWW: www.routerperformance.net
Support plans: https://www.max-it.de/en/it-services/opnsense/
Commercial Plugins (German): https://opnsense.max-it.de/

https://github.com/opnsense/core/issues/3671#issuecomment-525004560
WWW: www.routerperformance.net
Support plans: https://www.max-it.de/en/it-services/opnsense/
Commercial Plugins (German): https://opnsense.max-it.de/

All these fixes until 19.7.4_1 did the trick. Testing a little bit more today but now it's looking good!
And even the necessary reboot is fixed now :)