CARP and Hyper-V
-
So I set up a working Cluster of PFSense machines on a Hyper-V cluster.
It's all working and I thought I'd share my findings.For those having issues, I followed this guide:
https://doc.pfsense.org/index.php/Configuring_pfSense_Hardware_Redundancy_(CARP)For Hyper-V, all you have to do is allowing mac address spoofing and you're good to go.
For GUI:
Go to the PFSense VM settings.
Then under, the desired HA interface, go to Advanced Features.
Select "Enable Mac address spoofing"Powershell command:
Set-VMNetworkAdapter -MacAddressSpoofing "On"Any way we could get that added to what is currently in that carp guide?
Like they did for KVM and ESXi. -
I'll bet that this was my issue. I'll try that when I get the chance and report back here. Thanks.
-
Why do you want to use CARP in a CLUSTER?
Hyper-V (or VMWare,… you name it) are already designed to do failover scenarios.
VMWare even can do hot standby. -
The clustered hypervisor would protect against node failure by transferring the VM to another running node, but it would not protect against software failure from within the VM. If, for some reason, a CARP'd pfSense instance were to freeze/fail, in this scenario the failover CARP pfSense node should take over. Frankly, I'm not sure which is the more likely scenario: a failing hypervisor node or a failing pfsense instance.
In my particular configuration, I'm not clustering my Hyper-V nodes but instead as stand-alone nodes.