Failover Peer Unreachable, any suggestions to eliminate?
-
https://docs.netgate.com/pfsense/en/latest/troubleshooting/ha-dhcp-failover.html
Failover Peer Unreachable
If one failover peer cannot contact the other peer when it starts up, it will stop itself from handing out leases intentionally. It does this as a fail safe to prevent itself from handing out conflicting lease data.
This can happen if, for example, both nodes suffer a power loss and only one recovers. Another common scenario is if one node suffers a hardware failure and the working node must be rebooted before the failed node can be repaired.
Correcting this can be tricky. The simplest way to correct it is to bring the other peer online if possible. If that is not possible, then the only way may be to remove the failover peer IP addresses from each DHCP interface configuration so the node no longer believes it should be part of a failover pool. When the other node recovers, the configuration can be put back in place.
I ran into this problem several times on 23.05 Plus. So, we're having a hot summer, and to minimize the spread of heat, I just periodically turn off the main firewall at night. Almost always I put it in CARP maintenance mode and turn it off. Several times after that, I found that the DHCP server does not distribute IP addresses, due to the Failover Peer Unreachable reason. Is there any correct method other than a temporary reconfiguration of the DHCP? It is not entirely clear what is the meaning of CARP, if such a situation is possible on a regular basis as described in documents and as a result we get a non-working network.
