K
Ken Wallewein
I have a two-server 2016 failover cluster that is up and running, but is giving me validation errors. It seems to be related to a cluster name resource I can't identify. It kind of looks like it could be related to Cluster Aware Updating, but the CAU verify function runs just fine.
The actual cluster name is kmCL2. Here is the warning I'm getting.
Prior to getting this error, cluster verification and event logs were continuing to report DCOM errors that DCOM was unable to communicate with CAUkmCL2cca.abc.xyz with any of the configured protocols. There was no DNS name configured for it, BTW. Since I saw no need for such a cluster name, I enabled AD undelete functionality and deleted entries related to it. Now it looks like the cluster really thinks that resource name should exist -- but I still have no idea why.
When I check the network name resource of the actual cluster, it looks nothing like this.
I could presumably undelete those AD entries I deleted, but before I do that, I would like to know why it wants them or whether they should actually be something else, like kmCL2.
And for that matter, what does that error message mean, about "Offline the cluster network name resource and run the repair action on it"? How do I offline a "cluster name resource"? Does that mean shutting down the cluster? I don't see any way to run a repair on the real cluster name.
I can't find decent documentation on this stuff at all. Help or clarification would be much appreciated!
I want to live in Theory. Everything works there.
Continue reading...
The actual cluster name is kmCL2. Here is the warning I'm getting.
Validating network name resource CAUkmCL2cca for Active Directory issues.
The cluster network name resource 'CAUkmCL2cca' has issues in the Active Directory. The account could have been disabled or deleted. It could also be because of a bad password. This might result in a degradation of functionality dependent on the cluster network name. Offline the cluster network name resource and run the repair action on it.
Prior to getting this error, cluster verification and event logs were continuing to report DCOM errors that DCOM was unable to communicate with CAUkmCL2cca.abc.xyz with any of the configured protocols. There was no DNS name configured for it, BTW. Since I saw no need for such a cluster name, I enabled AD undelete functionality and deleted entries related to it. Now it looks like the cluster really thinks that resource name should exist -- but I still have no idea why.
When I check the network name resource of the actual cluster, it looks nothing like this.
I could presumably undelete those AD entries I deleted, but before I do that, I would like to know why it wants them or whether they should actually be something else, like kmCL2.
And for that matter, what does that error message mean, about "Offline the cluster network name resource and run the repair action on it"? How do I offline a "cluster name resource"? Does that mean shutting down the cluster? I don't see any way to run a repair on the real cluster name.
I can't find decent documentation on this stuff at all. Help or clarification would be much appreciated!
I want to live in Theory. Everything works there.
Continue reading...