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 "
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:
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)
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.
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.
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.
ble1
6 Operator
•
14354 Posts
•
56186 Points
657
0
Posted March 1st, 2006 07:00