I have set up CARP and HAST with ZFS according to the following guides:
http://forums.freebsd.org/showthread.php?t=29639
http://www.freebsd.org/doc/handbook/disks-hast.html
Two Servers: A & B.
I start out with server A having the HAST role set to primary.
The problem is that on boot, devd doesn't execute the action for the CARP LINK_UP event. I'm not sure if this is by design, if it's a bug, or if something is set up incorrectly (in the guides above). Any way, the preferred mode of operation should be:
When server A comes back: server B remains as primary, and server A becomes a secondary.
I have tried with enabling and disabling preemption (net.inet.carp.preempt). My setup is exactly what is shown in the guides above.
http://forums.freebsd.org/showthread.php?t=29639
http://www.freebsd.org/doc/handbook/disks-hast.html
Two Servers: A & B.
I start out with server A having the HAST role set to primary.
- The fail over works as expected when I test it by bringing the CARP interface down and up on the either server.
- If I reboot server A: server B switches the HAST role to primary and imports the ZFS pools.
- However, when server A comes back up: server B exports the ZFS pools and switches the HAST role to secondary, but server A never sets its HAST role to primary.
The problem is that on boot, devd doesn't execute the action for the CARP LINK_UP event. I'm not sure if this is by design, if it's a bug, or if something is set up incorrectly (in the guides above). Any way, the preferred mode of operation should be:
When server A comes back: server B remains as primary, and server A becomes a secondary.
I have tried with enabling and disabling preemption (net.inet.carp.preempt). My setup is exactly what is shown in the guides above.