none
Clustering problem

    Question

  • Hello all,

     Getting the below error message when trying to establish a Hyper-V cluster between 2 servers.  I am using Windows Server 2016 Datacenter with Server Core.  The Hyper-V role is installed.  I use another physical server to graphically manage these 2 servers. By intentional design, I have 1 physical NIC being utilized by the operating system and a 2nd NIC (which is teamed)  configured as a vSwitch for virtual machines.  On my 2 servers I disabled the Windows Firewall for domain, public, and private profiles. My network is using a /24 subnet mask on these 2 servers for all NIC's.  There is a VLAN configured at the physical switch for all ports involved and within Hyper-V the same VLAN is configured for the vSwitches.    Both servers are listening on UDP 3343.  I do not have Internet access inside the network my Hyper-V servers reside on, so I cannot readily upload logs or error messages.  They have to be typed in by hand.  I cannot easily apply patches at the moment either.  

    Only error message I have from the cluster validation wizard:

    Network interfaces server1.domain.tld – vEthernet (vSwitch) and server2.domain.tld – vEthernet (vSwitch) are on the same cluster network, yet 10.x.x.x is not reachable from 10.x.x.x using UDP on port 3343. 

    Network interfaces server1.domain.tld – vEthernet (vSwitch) and server2.domain.tld – Host are on the same cluster network, yet 10.x.x.x is not reachable from 10.x.x.x using UDP on port 3343. 

    Network interfaces server2.domain.tld – vEthernet (vSwitch) and server1.domain.tld – Host are on the same cluster network, yet 10.x.x.x is not reachable from 10.x.x.x using UDP on port 3343. 

    Network interfaces server2.domain.tld – vEthernet (vSwitch) and server1.domain.tld – vEthernet (vSwitch) are on the same cluster network, yet 10.x.x.x is not reachable from 10.x.x.x using UDP on port 3343.

    I am working with our network person concerning possible switch issues.  So other than possible network issues, does anyone have any suggestions what this might be?

    Please do not reply with criticism of any kind, only helpful "professional" comments.  Do not include any suggestions for better design of my Hyper-V configuration, its not changing.    

      

    Thursday, March 8, 2018 1:08 AM

Answers

  • I corrected my own problem.  Virtual switch related problem.  Cluster would not create while the virtual switch was enabled. 
    • Marked as answer by DBS_1 Wednesday, July 11, 2018 8:27 PM
    Wednesday, July 11, 2018 8:27 PM

All replies

  • Hello, 

    I would recommend checking the switch with your network administrator as you already mention. Maybe you have some ACL's configured on the switch itself which is blocking the traffic between this two hosts. What about other network traffic like ping, share, etc.? Does that work between this two hosts? 


    MCSE, MCSA, MS, MCP, MCTS, System Engineer

    Thursday, March 8, 2018 6:39 AM
  • Hello Matej,

      Other basic networking functionality works between the 2 servers just fine.  I did not know I was having a problem until I ran the cluster validation wizard.  Once I have more time, I was planning to hook up my 2 servers to an older switch that does not have ACL's so I can test the connectivity.  

    Thursday, March 8, 2018 4:57 PM
  • I corrected my own problem.  Virtual switch related problem.  Cluster would not create while the virtual switch was enabled. 
    • Marked as answer by DBS_1 Wednesday, July 11, 2018 8:27 PM
    Wednesday, July 11, 2018 8:27 PM