Error verifying the cluster networks

[Tim1]

Hi - I was wondering if someone can help please.
We are in the process of moving over to HyperV from VMWare.

I'm getting one error currently on the validation tool for the Validate Cluster Network Configuration which I cannot work out.

An error occurred while executing the test.
There was an error verifying the cluster networks.

Value cannot be null.
Parameter name: ifIdx

I'm wondering if this is related to the Remote NDIS Compatible Device as this will then disappear if I disable this, it will then pass, but then the Validate Network Communication will then come up with warnings for the iscsi ports,
* The communication path between network interface
'servername' - SLOT 1 Port 3 and network interface
'servername' - NIC4 is on a disabled network.

And these for the Management port:

* Unable to verify that all all adapters associated with SET Switch 'Switch1' on Node 'servername' are of the same RDMA Technology type, some adapters are reporting 'Device Default' or not reporting data at all.

* Node'servername' is reachable from Node 'servername' by only one pair of network interfaces. It is possible that this network path is a single point of failure for communication within the cluster. Please verify that this single path is highly available, or consider adding additional networks to the cluster.

I was wondering if anyone is able to help please, I'm stuck on this one error.

 

[cheezehead]

With multiple nodes and the NDIS adapters, manually assign the 169.254.0.x/24 IP addresses on the various NDIS adapters to be unique within a given cluster. This will take care of the duplicate IP issues.

If adapters are being used for remote SAN storage with multiple vlans, you will see some warnings about not being able to contact and that is ok in this case.

Install the latest network drivers which should take care of most of the RDMA warnings.

Unlike VMware, Hyper-V with failover clustering really wants two diverse paths for cluster communications. Beyond your normal in-band connection, often times copper 1G ports can be used as a secondary link. It will work without but gets to be a big problem if nodes can't communicate to each other.

I'm looking at using some of the SAN links for cluster communications as well given the new hosts have no copper ports and all ports are 25GB on the hosts.