Site outage. pfSense VM offline after pool master reboot
-
We downed our pool master (no VMs) for testing and the router VM (pfSense) lost internet connectivity.
When we restarted the master the router VM still has no internet connectivity.
All VMs,including the router are online in XO.
From the pfSense console I can ping VMs on the LAN however there is internet connectivity.
Everything looks fine so I am at a loss as to what the issue is.
-
When I try to manually configure the management interface as eth0 i get this:
The NIC appears to be there and connected:
-
This problem has since been resolved.
The issue related to running pfSense as a VM when using an additional IP form OVH Cloud.
When using an OVH additional IP on pfSense the MAC address of the additional IP needs to be entered in the WAN configuration.
When we restored this pfSense VM from CR and then migrated it to our production host the MAC address had been changed in XO. Once the correct MAC address was reentered into pfSense everything worked again.
This is a real gotcha when running pfSense as a VM using CR on a host that is not part of the main pool. -
I am very concerned that the pfSense VM went offline yesterday when the pool master was shutdown even through the pfSense VM was running on the slave.
If I can get an understanding of how this happened I can better mitigate it from happening again.
I have just reread this to ensure I understand the master/slave relationship:
https://xcp-ng.org/forum/topic/6986/pool-master-down-restart-makes-the-whole-pool-invisible-to-xo-till-master-is-online-again/9?_=1764739019505Can anyone suggest a reason as to why the pfsense VM went offline when the master was down?
As the router role is crucial and there are a number of moving parts to ensure it works as a VM I am seriously considering running it as a standalone server.