pfSense

I noticed this when a CARP member had no CARP status. I was told that this can happen if the VIP address isn't applied to a member.

I saw this recently on a pfSense VM, and confirmed that the member which had a blank CARP status didn't have VIP IP applied to it. In this case, it was the backup unit. I was able to fix it by editing the virtual IP address, and then clicking 'save'. Then the IP properly applied. I was told that this issue sometimes appears after a software upgrade. Indeed, that jives, because I had recently upgraded the VM.

I saw it on:
2.5.1-RELEASE