I have the following enviroment:
Active Directory (3 DC's) 2012 R2 Level
5 Nodes Hyper-V Server 2012 R2 Cluster (SMB2 as storage) with two NAS Windows Storage Server 2012 R2 (not CSV)
Each node has two networks (Clients & Cluster, 192.168.x.x, and Cluster 10.2.1.x)
I'm having some random issues, sometimes one server get evicted, when i rejoin that server to the cluster the difficulties appears, even this issues sometimes happens without
any server gettin evicted.
I cannot live migrate vm's to that problematic server, if i do a Quick Migration, the vm's migrates, but when i try to start it there are two possibles results:
- The VM never get started
- The VM moves to another node and then get started
The Clustering are reporting the following errors:
- Cluster node desacluster02 has been evicted from the failover cluster. (EventID 1011, Task Category: Node Mgr)
- The Cluster service failed to bring clustered role 'example' completely online or offline. One or more resources may be in a failed state.
This may impact the availability of the clustered role. (EventID 1205, Task Category: Resource Control Manager)
- Cluster resource 'Virtual Machine Configuration 'example' of type 'Virtual Machine Configuration' in clustered role 'example' failed.
The error code was '0x574' ('The target account name is incorrect.'). (what?!)
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.
Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet. (EventID 1069, Task Category Resource Control Manager)
- Cluster resource 'Virtual Machine Configuration 'example' of type 'Virtual Machine Configuration' in clustered role 'example' failed.
The error code was '0x43' ('The network name cannot be found.'). (what?!)
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.
Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet. (EventID 1069, Task Category Resource Control Manager)
Procedures already done:
- I checked conectivity among the nodes, both networks, and it's ok
- I rejoined the node with the problems
- I verified Sysvol/DFSR replication, it's ok
- I verified the rights/permissions in the NAS servers shares (computers$, and users involved)
Thanks in advance!