Node not behaving in cluster

We had to do a system swap on a system -- moved the drives and RAID
controller to a new system (same type) and just hooked it all up and went to
town. Well, this isn't working very well. The drives (data and quorum) fail
over just fine, but NO other resources will. Many of them say that only the
other node is a valid owner and we can't add this system as a possible owner.
Some have both listed, but they won't start. Any ideas?
Mark
Did you follow the instructions in BOL under Maintaining a Failover Cluster
on how to replace a failed node? SQL can be very picky about changes to
underlying hardware. You may need to treat this as a failed node and
remove-replace it in SQL. Since the Cluster itself seems OK, you can
probably pick up and do just the SQL installation changes.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Mark Larma" <Mark Larma@.discussions.microsoft.com> wrote in message
news:46CFE332-8DCD-43AA-AC9A-90AF481133FA@.microsoft.com...
> We had to do a system swap on a system -- moved the drives and RAID
> controller to a new system (same type) and just hooked it all up and went
to
> town. Well, this isn't working very well. The drives (data and quorum)
fail
> over just fine, but NO other resources will. Many of them say that only
the
> other node is a valid owner and we can't add this system as a possible
owner.
> Some have both listed, but they won't start. Any ideas?
> Mark
|||When you say that no other resource will come on line are you talking about
just SQL Server resources othe other cluster resources as well.
Do you have a specific error messages in the sysemt and application log
when the resources fail to come on line?
Rand
This posting is provided "as is" with no warranties and confers no rights.

Node missing component

for some reason the SQL Reporting service didnt get installed on one of my
nodes... so i was simply just going to install it... apparently it isnt so
simple.
how do i go about adding the reporting services to a node?
Thanks
Justin
SQL Reporting Service is not cluster aware. You can install it by running
SQL setup CD and select the Reporting Service option.
Ayad Shammout
"Justin Rich" <jrich523@.yahoo.spam.com> wrote in message
news:Ofq4xo60HHA.4184@.TK2MSFTNGP06.phx.gbl...
> for some reason the SQL Reporting service didnt get installed on one of my
> nodes... so i was simply just going to install it... apparently it isnt so
> simple.
> how do i go about adding the reporting services to a node?
> Thanks
> Justin
>
|||For SQL 2000, it is a separate CD and install. For SQL 2005, go to
add/remove programs and change SQL 2005. Add the Reporting SErvices
component when you get the features list.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Ayad Shammout" <ashammout1@.hotmail.com> wrote in message
news:u2UZcS70HHA.5772@.TK2MSFTNGP02.phx.gbl...
> SQL Reporting Service is not cluster aware. You can install it by running
> SQL setup CD and select the Reporting Service option.
> Ayad Shammout
>
> "Justin Rich" <jrich523@.yahoo.spam.com> wrote in message
> news:Ofq4xo60HHA.4184@.TK2MSFTNGP06.phx.gbl...
>

Node Eviction

HI,
I need to evict one node from a two node, two instance SQL Cluster.
Beyond failing over all resources and ownership to the surviving cluster
node, is there any other configuration change I need to make in SQL server
before doing this? Thanks.
John
Nope. Can I ask why you need to evict the node?
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"JT" <Jthayer@.online.nospam> wrote in message
news:D40762AF-1D29-4E5A-AA66-EE7834434122@.microsoft.com...
> HI,
> I need to evict one node from a two node, two instance SQL Cluster.
> Beyond failing over all resources and ownership to the surviving cluster
> node, is there any other configuration change I need to make in SQL server
> before doing this? Thanks.
> --
> John
|||Thanks Rodney. To answer that question, look at my thread in Windows Server
Clustering regarding adding 64 bit nodes to 32 bit node cluster where you
were joking about making us look at MVP pictures. On a related note, there
is a KB out there about difficulties adding cluster nodes to Win2003 when
using NTLMv2 only, which is what I do. The article KB is 890761. It applies
to 32 bit and IA64 Windows 2003. Do you know if it applies to x64 Windows
2003? Thanks.
John
"JT" wrote:

> HI,
> I need to evict one node from a two node, two instance SQL Cluster.
> Beyond failing over all resources and ownership to the surviving cluster
> node, is there any other configuration change I need to make in SQL server
> before doing this? Thanks.
> --
> John
|||Yes, there is an essential step. You need to run the SQL install app and
remove SQL from the node before evicting the node. If you don't do this,
SQL will still have node configuration information and won't let you
reinstall later. You can do the removal after the node is evicted and
removed, but it will throw errors since it cannot update information on the
now-missing node. BOL has information under "maintaining a failover
cluster".
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"JT" <Jthayer@.online.nospam> wrote in message
news:D40762AF-1D29-4E5A-AA66-EE7834434122@.microsoft.com...
> HI,
> I need to evict one node from a two node, two instance SQL Cluster.
> Beyond failing over all resources and ownership to the surviving cluster
> node, is there any other configuration change I need to make in SQL server
> before doing this? Thanks.
> --
> John
|||Crap! I always forget that step! You rule Geoff!
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:O9kdHGRSGHA.5108@.TK2MSFTNGP11.phx.gbl...
> Yes, there is an essential step. You need to run the SQL install app and
> remove SQL from the node before evicting the node. If you don't do this,
> SQL will still have node configuration information and won't let you
> reinstall later. You can do the removal after the node is evicted and
> removed, but it will throw errors since it cannot update information on
> the now-missing node. BOL has information under "maintaining a failover
> cluster".
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "JT" <Jthayer@.online.nospam> wrote in message
> news:D40762AF-1D29-4E5A-AA66-EE7834434122@.microsoft.com...
>
|||I honestly don't know, you can always PSS and ask though.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"JT" <Jthayer@.online.nospam> wrote in message
news:630A1BF0-199E-4743-BB15-E99EA54E3687@.microsoft.com...[vbcol=seagreen]
> Thanks Rodney. To answer that question, look at my thread in Windows
> Server
> Clustering regarding adding 64 bit nodes to 32 bit node cluster where you
> were joking about making us look at MVP pictures. On a related note,
> there
> is a KB out there about difficulties adding cluster nodes to Win2003 when
> using NTLMv2 only, which is what I do. The article KB is 890761. It
> applies
> to 32 bit and IA64 Windows 2003. Do you know if it applies to x64 Windows
> 2003? Thanks.
> --
> John
>
> "JT" wrote:

Node Cluster - Fails on Network Resources

I am running a 2-node cluster for SQL Server. After powering down both
servers (passive then active), one of the nodes did not successfully join the
cluster. This node shows exclamation marks on the Network Interfaces in
Cluster Administrator. These nics are functioning correctly outside of the
cluster. The cluster log on the failed node indicates that these network
interfaces are functioning each time it tries to join the cluster. The
active node's cluster log indicates that these resources are not functioning
and removes the other node from being active.
If anyone has any ideas on how to solve this problem, your input would be
greatly appreciated.
Thanks,
Debbie
Is the NIC you have exclamation mark on Public or Private network?
Ayad
"Debbie" <Debbie@.discussions.microsoft.com> wrote in message
news:1CC9F5E6-46E3-482A-913C-B8C57692BDB2@.microsoft.com...
> I am running a 2-node cluster for SQL Server. After powering down both
> servers (passive then active), one of the nodes did not successfully join
the
> cluster. This node shows exclamation marks on the Network Interfaces in
> Cluster Administrator. These nics are functioning correctly outside of
the
> cluster. The cluster log on the failed node indicates that these network
> interfaces are functioning each time it tries to join the cluster. The
> active node's cluster log indicates that these resources are not
functioning
> and removes the other node from being active.
> If anyone has any ideas on how to solve this problem, your input would be
> greatly appreciated.
> Thanks,
> Debbie
>
|||There are three NICs, the heartbeat (crossover), private (for backups) and
our intranet. All three have the exclamation mark.
"Ayad" wrote:

> Is the NIC you have exclamation mark on Public or Private network?
> Ayad
> "Debbie" <Debbie@.discussions.microsoft.com> wrote in message
> news:1CC9F5E6-46E3-482A-913C-B8C57692BDB2@.microsoft.com...
> the
> the
> functioning
>
>
|||Check your IP settings and make sure you are using the correct subnet mask
address and network segment for each port and match each port with the other
node's port.
Was it working before or this is a new install?
Ayad
"Debbie" <Debbie@.discussions.microsoft.com> wrote in message
news:89B546EC-247D-464E-A149-6952D4AC5EC7@.microsoft.com...[vbcol=seagreen]
> There are three NICs, the heartbeat (crossover), private (for backups) and
> our intranet. All three have the exclamation mark.
> "Ayad" wrote:
join[vbcol=seagreen]
in[vbcol=seagreen]
of[vbcol=seagreen]
network[vbcol=seagreen]
The[vbcol=seagreen]
be[vbcol=seagreen]
|||Ayad,
This is not a new install. It was working before. We had to power down all
of the servers for a generator hook-up to be installed. When bringing the
cluster back up, this server failed and has failed ever since with these NIC
resource errors.
The subnets look good on the NICs.
Thanks,
Debbie
"Ayad" wrote:

> Check your IP settings and make sure you are using the correct subnet mask
> address and network segment for each port and match each port with the other
> node's port.
> Was it working before or this is a new install?
> Ayad
> "Debbie" <Debbie@.discussions.microsoft.com> wrote in message
> news:89B546EC-247D-464E-A149-6952D4AC5EC7@.microsoft.com...
> join
> in
> of
> network
> The
> be
>
>
|||Debbie,
Try Shutdown that node (server hard reboot) and power it ON again and see if
it clears your NIC issue.
Ayad
"Debbie" <Debbie@.discussions.microsoft.com> wrote in message
news:9AA7AFAC-5A77-4A71-B901-9CB4E99462ED@.microsoft.com...
> Ayad,
> This is not a new install. It was working before. We had to power down
all
> of the servers for a generator hook-up to be installed. When bringing the
> cluster back up, this server failed and has failed ever since with these
NIC[vbcol=seagreen]
> resource errors.
> The subnets look good on the NICs.
> Thanks,
> Debbie
> "Ayad" wrote:
mask[vbcol=seagreen]
other[vbcol=seagreen]
and[vbcol=seagreen]
both[vbcol=seagreen]
successfully[vbcol=seagreen]
Interfaces[vbcol=seagreen]
outside[vbcol=seagreen]
would[vbcol=seagreen]
|||Ayad,
The hard reboot did not clear up the problem. I am thinking of removing
this node from the cluster and then readding it to the cluster to see if that
clears up the problem.
Thanks,
Debbie
"Ayad" wrote:

> Debbie,
> Try Shutdown that node (server hard reboot) and power it ON again and see if
> it clears your NIC issue.
> Ayad
> "Debbie" <Debbie@.discussions.microsoft.com> wrote in message
> news:9AA7AFAC-5A77-4A71-B901-9CB4E99462ED@.microsoft.com...
> all
> NIC
> mask
> other
> and
> both
> successfully
> Interfaces
> outside
> would
>
>