Hyper-V Cluster, nodes and IPs - problems

Question

Hi,

We have a hyper-v cluster with just 2 nodes and about 10 VMs. One shared disk with machines, a quorum, etc. A simple one.

We had to upgrade nodes to windows server 2022 because of security auditory, disabling first NICS team and breaking cluster.

Recreate the cluster, with other name, same IP.

Now we have many problems with comunication between nodes, with Veeam Backup...

• Sometimes i receive error about 'network segregation' that i don't know what exactly is and where may i review settings.
• Now i get this error in events (sorry; is in spanish): "El rol en clúster 'CAUNHClupj8v12k' superó su umbral de conmutación por error" I don't even now nothing about this 'clusters rol 'CAUNHClupj8v12k'. Of course it is not a VM
• And: in ipconfig, in one of the two nodes, apears the same IP direction as cluster: Adaptador de Ethernet vEthernet (LAN MVS): Sufijo DNS específico para la conexión. . : corp.neinorhomes.com Descripción . . . . . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter Dirección física. . . . . . . . . . . . . : D8-9D-67-25-72-44 DHCP habilitado . . . . . . . . . . . . . : no Configuración automática habilitada . . . : sí Dirección IPv4. . . . . . . . . . . . . . : 10.48.8.52(Preferido) Ok. Is Node's IP. Correct Máscara de subred . . . . . . . . . . . . : 255.255.255.0 Dirección IPv4. . . . . . . . . . . . . . : 10.48.8.50(Preferido) This is Cluster's IP. Why here? Máscara de subred . . . . . . . . . . . . : 255.255.255.0 Puerta de enlace predeterminada . . . . . : 10.48.8.1 Servidores DNS. . . . . . . . . . . . . . : 10.200.7.101

                                     *`10.48.8.24`*
  

  NetBIOS sobre TCP/IP. . . . . . . . . . . : habilitado

Does someone figure out where the problem comes from?

Thanks in advance

Regards.

Answer 1

Hey,

Cluster IP resource will reside on one of the node (owner of the resource). That is a normal behavior of the cluster. It can be moved to the other node by moving cluster core resources, if you right click on the cluster.

Might be helpful: https://learn.microsoft.com/en-us/troubleshoot/windows-server/high-availability/cluster-information-ip-address-failover

I would recommend you run cluster validation report and check if you have errors there. Do you have any additional errors in Event logs.

In addition, the following guide might help with verifying configuration. https://www.starwindsoftware.com/resource-library/starwind-virtual-san-for-hyper-v-2-node-hyperconverged-scenario-with-windows-server-2016/

Cheers,

Alex Bykovskyi

StarWind Software

Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Answer 2

Hello,

 

Thank you for posting in Q&A forum.

I can see there are several problems you are facing with after the rebuild. Please kindly follow below steps and see if issue can be mitigated:

1.Please avoid configure duplicate IP address for node and cluster. Otherwise the network communication can be impacted.

2.The network segregation error might indicates there are some network divison errors.

3.Please kindly go to Event Viewer and check log "Applications and Services Logs" -> "Microsoft" -> "Windows" -> "FailoverClustering". Please kindly share your observation if there's any information.

4.Check if there's any log under %SystemRoot%\Cluster\Reports on cluster node (Cluster.log and file with .etl extensions) .

Hope this answer can help you well.

 

Best regards，

Jill Zhou

Answer 3

Hi, Jill

Thanks for answering.

1.- No IP configured by us. If i see in connection IPV4 properties, there is just one; but ipconfig still showing cluster IP id addition to his own one

2.- I'd love to remove segregation. My question is, how? Is in switch? in windows? don't know nothing about this.

3.- Now, jet, Cluster is not showing error or critical events at all. Others like:

[RCM] [GIM] Máquina virtual: UNKNOWN (0n33562717 0x200205d ) obj: (0n2 RESOURCE_TYPE) flags: ...., code: (0n2071 0x817) access: (0n1 R) Control Call Returned with Error 1.

old ones:
[RES] Container: Control code with id = 33554445 has no handler, returing 1

Answer 4

Hey,

You are seeing cluster IP by running ipconfig. It can be checked in Failover Cluster Manager. It can be moved to the other node by right click on a Cluster name -> More options.

Might be helpful: https://learn.microsoft.com/en-us/troubleshoot/windows-server/high-availability/cluster-information-ip-address-failover

Do you have any additional errors in Event logs? I would recommend to run cluster validation report and see if it reports any errors with your configuration. https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/jj134244(v=ws.11)

In addition, the following guide might help with verifying the configuration.
https://www.starwindsoftware.com/resource-library/starwind-virtual-san-for-hyper-v-2-node-compute-and-storage-separated-scenario-with-windows-server-2016/

Cheers,

Alex Bykovskyi

StarWind Software

Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.