December 17, 2013 at 11:50 am
Howdy,
I have a VM-based two node 2008 R2 MS cluster with a SQL 2008R2 failover cluster instance that was installed on both. During the process of adding a node on a different subnet (in a different datacenter location) to the cluster, one of the original nodes crashed and would not come back up. I then evicted that crashed node from the cluster using the Failover Cluster Manager. I've run a validation on the cluster and there is no error or reference to the evicted server name.
We have a tool that our storage vendor provides that will keep the data stores (LUNs) in the two datacenter locations in-synch. In trying to configure the tool to setup the mirror relationships between the two data stores, I receive a warning event in the System log that causes the storage vendor tool to not complete.
The warning event is 6037 for source LsaSrv:
"The program svchost.exe, with the assigned process ID 756, could not authenticate locally by using the target name RPCSS/EvictedServerName. The target name used is not valid. A target name should refer to one of the local computer names, for example, the DNS host name.
Try a different target name."
I can't find a reference to the EvictedServerName on any of the Services or Resources in the cluster, so I can't figure out what might still be trying to access that node.
My searching has not turned up anything helpful (that I can understand).
Does anybody have an idea on what might still be referencing that evicted node and\or how I might go about removing that reference?
...thanks
December 18, 2013 at 9:13 am
If I understaood you correctly (not guaranteed), I don't think you mentioned any details on HOW the vendor tool keeps those LUNs in sync. I would choose to believe that one might well have needed to configure said tool to know what servers were needing to share it, and that it might need to know how to access such LUNs from the point of view of each such user thereof. Could it possibly be a config issue now that there's an evicted node, such that said node will need to be taken out of the list of "users" ? Then again, I could just be mentally stretching without a clue as to what that tool does or how...
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
December 18, 2013 at 9:30 am
Your instincts serve you well. 🙂
So looking back at my motives for this post, I did not articulate this very well.
I was mostly sure it was a problem with their tool, so I was mainly looking for a way to tell the vendor that and not an issue with the eviction process in MS Clustering or the SQL Instances. Although I'm by no means a clustering guru, so I was wondering if there was some other "check" I should be doing on the MS side that someone else would know about.
It turns out that the issue was with their tool. There was a leftover registry entry that their tool maintained that listed the nodes in the cluster. Their uninstall process did not clean it up. We found and edited their registry entry to remove the evicted node. Now their tool is working more like it should.
...thanks!
December 18, 2013 at 9:55 am
Glad I could help. Now if you only knew just how little I know about the details of clustering... :hehe:
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply