Hi All,
Running into this very odd issue with my Failover Cluster.
I'm running two Server 2012 (Node A and Node B) machines on the same domain (DC is virtual on a separate Server 2012 box) utilising a VM providing iSCSI storage on one of the Host Machines (Node A).
The Cluster Validation test passes with warnings on SCSI 3 Reservations and Network adapters not in use, allows to me to create the cluster fine. But the issue comes down to one way Live Migration Node A to Node B, flawless, Node B to node A "fail". Quick Migration Node B to Node A, flawless.
The error comes up stating that the connection was actively refused, which lead me to this article on Shared Nothing Live Migrations
http://blogs.technet.com/b/roplatforms/archive/2012/10/16/shared-nothing-migration-fails-0x8007274c.aspx
Which pointed out that Live Migrations happen over Port 6600 and recommended using a "netstat -a" to view what ports are actively in use.
Port 6600 comes up on node B but not node A. Thus explaining the one way live migration.
I tried restarting the Hyper V Virtualisation Management Services in Services, tried setting Hyper V Management Service to Automatic Delayed, Destroyed and remade the cluster, Uninstalled and reinstalled Failover Cluster Manager, Uninstalled both Failover Cluster Manager and Hyper V reinstalled and nothing. For nothing will this port "Open". Tried manually setting a rule in Windows Firewall to open Port 6600 and nothing.
What the devil is going on here?