Both nodes have been restarted a few times since it started having issues, and yesterday they also rebooted as part of an update.

I have reached out to support as per your message.

This started roughly in August shortly after I spun up the instance, but I haven't had time to truly do any debugging until this week due to other obligations.

I should note that the free licensing has been assigned (not the trial) for a bit now. SR-IOV is disabled (and has been since the start), and they are now configured with static IPs (from the time it was first an issue with DHCP reservation) for the management side (with redundant switches and NICs)...

I have two CVM nodes, configured according to the Hyper-V Failover Cluster CVM documentation, everything was working great for about a week, but then, due to a network issue one of the appliances got a bad IP via DHCP (instead of it's assigned reservation), I resolved it by setting the IPs to static...