Hyper V 2022 Cluster will not validate the Network

Question

Hi

I have set this up three times and I still cannot get the validation wizard to validate the network configuration. I have followed all the instructions that I could find and it is still giving me this issue. This is how I have it set up.

Two Phycial NICS VSNIC1 VSNIC2

Created a "SETTeam" Vswitch with these VitualAdapters: "SETNIC2" and "SETNiC3"

Set Affinity between "SetNIC2 and VSNIC1" and "SetNIC3 and VSNIC2"

Created a "HOSTMgmt" vnic to manage all the host

SETNIC2, SETNIC3, and HOSTMGMT all have an IP address in the same vlan applied

I can send a copy configuration commands I used since I created a configuration document.

Here is the errors that I am still trying to resolve

Network interfaces firsthost - SETTeam and secondhost - SETTeam are on the same cluster network, yet address fe80::f6bd:ed54:40a7:70ab%18 is not reachable from fe80::373d:d93d:90da:e7c5%19 using UDP on port 3343.

Network interfaces firsthost - SETTeam and ThirdHost - SETTeam are on the same cluster network, yet address fe80::e9c6:bce0:a736:aa3b%15 is not reachable from fe80::373d:d93d:90da:e7c5%19 using UDP on port 3343.

Network interfaces secondhost - SETTeam and firsthost - SETTeam are on the same cluster network, yet address fe80::373d:d93d:90da:e7c5%19 is not reachable from fe80::f6bd:ed54:40a7:70ab%18 using UDP on port 3343.

Network interfaces secondhost - SETTeam and ThirdHost - SETTeam are on the same cluster network, yet address fe80::e9c6:bce0:a736:aa3b%15 is not reachable from fe80::f6bd:ed54:40a7:70ab%18 using UDP on port 3343.

Network interfaces ThirdHost - SETTeam and IPL-Host-02 - SETTeam are on the same cluster network, yet address fe80::f6bd:ed54:40a7:70ab%18 is not reachable from fe80::e9c6:bce0:a736:aa3b%15 using UDP on port 3343.

Network interfaces ThirdHost - SETTeam and firsthost - SETTeam are on the same cluster network, yet address fe80::373d:d93d:90da:e7c5%19 is not reachable from fe80::e9c6:bce0:a736:aa3b%15 using UDP on port 3343.

Answer 1

Hello there,

Attempt to start the cluster service on all nodes in the cluster so that nodes with the latest copy of the cluster configuration data can first form the cluster. This node will then be able to join the cluster and will automatically obtain the updated cluster configuration data. You can find the logs and resolution here cross-verify your log and try out the possible resolution for it.
Failover Clustering system log events https://learn.microsoft.com/en-us/windows-server/failover-clustering/system-events

-------------------------------------------------------------------------------------------------------------------------------

--If the reply is helpful, please Upvote and Accept it as an answer–