Cluster Validation - Validate Network Communication failure HELP

hi,

i have 8 node cluster running , working treat when run cluster validation receive warning each host. have included top few lines of tests. warning repeated each node every other node in cluster.

warning:

node hyp01n02.domain.uk reachable node hyp01n01.domain.uk multiple communication paths, 1 or more of these paths experienced more 10% packet loss.

result	source interface name	source ip address	destination interface name	destination ip address	same cluster network	packet loss (%)
success	hyp01n01.domain.uk - iscsi1	10.100.1.11	hyp01n02.domain.uk - iscsi1	10.100.1.12	true	0
success	hyp01n01.domain.uk - iscsi1	10.100.1.11	hyp01n02.domain.uk - vethernet (management)	172.21.59.12	false	96
failure	hyp01n01.domain.uk - iscsi1	10.100.1.11	hyp01n02.domain.uk - iscsi2	10.100.2.12	false	100
failure	hyp01n01.domain.uk - iscsi1	10.100.1.11	hyp01n02.domain.uk - vethernet (migration)	172.21.59.131	false	100
failure	hyp01n01.domain.uk - iscsi1	10.100.1.11	hyp01n02.domain.uk - vethernet (cluster)	172.21.61.12	false	100
success	hyp01n01.domain.uk - iscsi2	10.100.2.11	hyp01n02.domain.uk- iscsi2	10.100.2.12	true	0
success	hyp01n01.domain.uk - iscsi2	10.100.2.11	hyp01n02.domain.uk - vethernet (management)	172.21.59.12	false	96

each node has:

iscsi1 vlan101 1x 10gb port , iscsi2 vlan 116 1x 10gb port configured mpio

trunk1 (4x 1gb nic) (address hash, lacp) on sits team vethernet (management) vlan 101 , vethernet (cluster) vlan 104

trunk10 (2x 10gb nic) (hyper-v port, lacp) on sits second team vm traffic , vethernet (migration) vlan 105

trunk1 , trunk10 configured lacp , locked down relevant vlans on switch on vnics. (don't know if best practise leave trunk open vlans if nics configured in hyper-v vlans or have both set are)

iscsi1 on vlan 101 , ip range of 10.100.1.x

iscsi2 on vlan 116 , ip range of 10.100.2.x

vethernet (management) on vlan 100 , on ip range 172.21.59.12

vethernet (cluster) , vethernet (migration) on there own vlans , ip ranges.

iscsi1 , iscsi2 has ip v4 , ip v6 left enabled , dns registration , netbios disabled.  have jumbo frames enabled.

each network can talk on relevant nic or vnic other hosts on same nic or vnic correct , not across networks shouldn't (migration) (cluster) etc correct.

(cluster) , (migration) allow cluster communications

(management) accepts cluster , client communications.

iscsi1 , iscsi2 set not allow cluster traffic.

binding order:

1.management
2.iscsi1
3.iscsi2
4.migration
5.cluster

cluster metric 900 , migration 1000.

still receive warning below , assume because how when testing, there seems tiny conection across vlans , ip ranges iscsi1 or iscsi2 vnic (management) shouldn't case. assume error because of highlighted line of table???

can suggest anything, driving me mad! things seem work need test complete correctly able sign clients environment off.

i'm surprised there (even if little) chat between iscsi , vethernet management according test though on different physicalnics, ip range vlans. also, trying  establish if warning warning or concerned about. networks broken are, there multiple paths between each node of many locked down cant talk.

concern although works fine , results read right, have never seen warning before in implementation when broken vlans, ip ranges , virtual or physical nics.

i have similar setup - keep management / heartbeat / livemigration , csv interfaces enabled while creating cluster. interface use hyperv data teamed 1 trunk , prefer have teaming created after creating cluster. if confident communication fine on management/heartbeat/livemigartion/csv interfaces, feel safe.

cheers !

---

optimism faith leads achievement. nothing can done without hope , confidence.


insidevirtualization.com

Windows Server  >  Hyper-V