DHCP Server failover_peerip is not synchronized on 2.2 with CARP
On 2.1.x and before, the failover_peerip is synchronized and adjusted for use by the secondary. On 2.2 the value is blank on the secondary after sync. The other settings synchronize as expected.
#4 Updated by Jim Pingle over 4 years ago
I upgraded my test VM and tried it again, it still works. If I remove the failover IP, it becomes blank on the secondary. If I add it back in, it adjusts and synchronizes accordingly. You may have a configuration issue, not a bug. The field did synchronize on earlier versions.
You place the IP of the secondary system in the settings on the primary, during the sync, the primary puts its own IP in there and places those settings on the secondary, so they each point to one another.