Node Alias Problems on Autostart SE with SQL

Question

We have implemented a cluster but seem to be hitting problems regarding node alias's. OS W2k3 SP1

One is logged with the help desk, the problem being, when failing over a resource to the other node,the node alias refuses to deport and so the resource group does not failover. It only fails over when we shut the server down so it is forced to fail.

Secondly we have noticed that we are getting erros in the event log which says, " Unable to refresh WINS registrations for Node Alias "

Anybody else had similar problems?

ble1 · Answer

Is this also Win2k3 SP1? And final question - did you had this before SP1?

csellner · Answer

Hi, and thanks for the reply. This is a brand new installation, and yes, Win2K3 SP1. The backbone NIC was configured as support recommended, which is the bare minimum of network support:

TCP/IP advanced properties
"disable NETBIOS over TCP/IP"
Deselect "enable LMHosts Lookup"

NIC properties
Set speed and duplex to Full Duplex

----------------------------------
This doesn't seem to be causing a problem that I can tell. It's just that this warning message is being generated every half hour in some cases, and in other cases, multiple times all at once, and on both nodes. Both nodes are in agreement that the problem only exists with the host name of secondary cluster server. I'll ignore it if it doesn't indicate a future problem since it's just a warning, but I was curious to know what causes it if anyone knows?

(full warning message:
CSBSAA (Agent)

WARN: Unable to refresh WINS registrations for Node Alias on node yangtze)

Thanks,

csellner · Answer

We have a new cluster that is generating the same error that you're getting in the second part of your question:

"Unable to refresh WINS registrations" - did anyone ever explain this?

(Windows 2003 server, SQL 2000, Co-Standby AAdvanced 5.1.2 with A_AAM_512P1, A_HF_512_76173 and A_WIN_HF_512_74900 patches and hotfixes)

Thank you,

dgregory3 · Answer

Will there be a service pack or hotfix to solve this problem as we are still getting the error.

ble1 · Answer

No idea as I have no clue what current status is with investigation, but if this would be confirmed as a MS issue then the ball would be in their playground.

ble1 · Answer

There are many ppl with this problem and it all
started after going to SP1. Official statement can
be given by support, but in short it has something to
do with workstation registration service and
apparently this happened after SP1. Not sure what is
the current status, but if you open this as case you
might find more.

csellner · Answer

There are many ppl with this problem and it all
started after going to SP1. Official statement can
be given by support, but in short it has something to
do with workstation registration service and
apparently this happened after SP1. Not sure what is
the current status, but if you open this as case you
might find more.

I appreciate the response. Glad to know it isn't an isolated issue. I'll open a case as informational, but I don't want to spend time trying to resolve it if there isn't a resolution already. UNLESS it is a clue about a future problem.

Thanks again.

Replication Manager

Node Alias Problems on Autostart SE with SQL

Was this post helpful?