"Consider adding additional networks or network interfaces to the cluster" warning, although having redundant network connections

Dear all,

I would like to submit to your attention a warning that I can't fix in our two-node Windows Server 2012 Failover cluster :

We have 6 "NICs" per node:

- 2 NICs for iSCSI (PT0/1; 10.0.0.x and 10.0.2.x; intracluster communication not allowed)

- 2 teamed NICs and its relative vSwitch for intradomain communication (CIGS; internal allowed, clients can connect through this network);

- 1 teamed NIC (for possible further deployment) connected to the other node with a crossover cable for intracluster communication (Cluster; 192.168.1.x, IPv6 enabled; internal allowed, clientscannot connect through this network);

- 1 teamed NIC and its relative vSwitch for heartbeat and Hyper-V replica traffic towards a 3rd hypervisor which is not clustered (HB; 192.168.2.x, IPv6 enabled; internal allowed, clients can connect through this network).

Name    State Role AutoMetric Metric
----    ----- ---- ---------- ------
CIGS       Up    3      False  21000
Cluster    Up    1      False   1000
HB          Up    3      False   1100
iSCSI_0   Up    0      False   1200
iSCSI_2   Up    0      False   1300

According to cluster validation, the output states that, in current configuration, we have a single point of failure. Actually, AFAICT, we granted communication to the cluster to all the networks but the iSCSI one, although the validation report states that Cluster and Heartbeat networks are disable... all pings requests ended up properly.

Thanks for your kind attention, please find the validation report enclosed:

Description: Validate that servers can communicate, with acceptable latency, on all networks.
Analyzing connectivity results ...
Node HYPERV3.xxx and Node HYPERV1.xxx are connected by one or more communication paths that use disabled networks. These paths will not be used for cluster communication and will be ignored. This is because interfaces on these networks are connected to an iSCSI target. Consider adding additional networks to the cluster, or change the role of one or more cluster networks after the cluster has been created to ensure redundancy of cluster communication.
The communication path between network interface HYPERV1.xxx - PT1 and network interface HYPERV3.xxx - PT1 is on a disabled network.
The communication path between network interface HYPERV1.xxx - PT0 and network interface HYPERV3.xxx - PT0 is on a disabled network.
The communication path between network interface HYPERV1.xxx - Cluster and network interface HYPERV3.xxx -Cluster is on a disabled network.
The communication path between network interface HYPERV1.xxx - vEthernet (vSwitch_HB) and network interface HYPERV3.xxx - vEthernet (vSwitch_HB)is on a disabled network.
Node HYPERV3.xxx is reachable from Node HYPERV1.xxx by multiple communication paths, but each path
includes network interface HYPERV1.xxx - vEthernet (vSwitch_HB). This network interface may be a single point of
failure for communication within the cluster. Please verify that this network interface is highly available or consider adding additional networks or network interfaces to the cluster.