Normal Procedure for shutdown SQL Server

Dear Sir,
I have a cluster Active/Passive cluster setting, Win2003. I would like to
know the normal procedures for shuting down the SQL Server on both nodes. Is
that needed to disable the passive node before using SQL Manager to shutdown
SQL Server?Please kindly advise!
Many thanks!
From,
Henry
Hi
Do not use SQL Manager to do anything with clustered SQL servers.
You must use Cluster Administrator to take a group offline or bring it
online again.
If you use SQL Manager, you in effect cause a failover.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Henry" wrote:

> Dear Sir,
> I have a cluster Active/Passive cluster setting, Win2003. I would like to
> know the normal procedures for shuting down the SQL Server on both nodes. Is
> that needed to disable the passive node before using SQL Manager to shutdown
> SQL Server?Please kindly advise!
> Many thanks!
> From,
> Henry
>
sql

Non-Yielding on Scheduler 0.

I have a server with Windows 2003 Server with SQL Server 2000 Cluster Server.
What could cause the error listed below with SQL Server 2000.
Thanks
Process 174:0 (cb8) UMS Context 0x000006FBFE8C88B1 appears to be
non-yielding on Scheduler 6
Process 140:0 (700) UMS Context 0x000006FBFE8A7230 appears to be
non-yielding on Scheduler 0.
Hi Joe K,
I once had a similar problem with SQL Server, in my case it was caused by
the fact that we used highend SAN’s that allocated disk space to quickly.
(Imagine that, problems caused by disks being to fast instead of to slow)
The KB article related to this problem is
http://support.microsoft.com/kb/810885.
Unfortunately your post didn’t contain the actual error code so I can’t
verify if the problem described in the KB article is the one you are
experiencing. However if the KB article does describe the problem you are
facing installing SQL Server 2000 SP4 would probably solve it.
Let me know if this helps,
Kind regards Leon Krancher.
P.s. Most Servers I know that use a high-end storage device contain more
than 4Gb of ram. If this is also the case in your scenario you might also
want to take a look at http://support.microsoft.com/kb/899761. This KB
article describes a problem with AWE on SQL Servers with SP4 installed and
points to the additional fix that has to be installed to cure this.
"Joe K." wrote:

> I have a server with Windows 2003 Server with SQL Server 2000 Cluster Server.
> What could cause the error listed below with SQL Server 2000.
> Thanks
> Process 174:0 (cb8) UMS Context 0x000006FBFE8C88B1 appears to be
> non-yielding on Scheduler 6
> Process 140:0 (700) UMS Context 0x000006FBFE8A7230 appears to be
> non-yielding on Scheduler 0.
|||And it's fixed in SP4
Nik Marshall-Blank MCSD/MCDBA
"Leon" <Leon@.discussions.microsoft.com> wrote in message
news:92979375-B688-4CD1-9B67-3EE1EDAD273E@.microsoft.com...[vbcol=seagreen]
> Hi Joe K,
> I once had a similar problem with SQL Server, in my case it was caused by
> the fact that we used highend SAN's that allocated disk space to quickly.
> (Imagine that, problems caused by disks being to fast instead of to slow)
> The KB article related to this problem is
> http://support.microsoft.com/kb/810885.
> Unfortunately your post didn't contain the actual error code so I can't
> verify if the problem described in the KB article is the one you are
> experiencing. However if the KB article does describe the problem you are
> facing installing SQL Server 2000 SP4 would probably solve it.
> Let me know if this helps,
> Kind regards Leon Krancher.
> P.s. Most Servers I know that use a high-end storage device contain more
> than 4Gb of ram. If this is also the case in your scenario you might also
> want to take a look at http://support.microsoft.com/kb/899761. This KB
> article describes a problem with AWE on SQL Servers with SP4 installed and
> points to the additional fix that has to be installed to cure this.
>
> "Joe K." wrote:

Non-Yielding on Scheduler 0.

I have a server with Windows 2003 Server with SQL Server 2000 Cluster Server
.
What could cause the error listed below with SQL Server 2000.
Thanks
Process 174:0 (cb8) UMS Context 0x000006FBFE8C88B1 appears to be
non-yielding on Scheduler 6
Process 140:0 (700) UMS Context 0x000006FBFE8A7230 appears to be
non-yielding on Scheduler 0.Hi Joe K,
I once had a similar problem with SQL Server, in my case it was caused by
the fact that we used highend SAN’s that allocated disk space to quickly.
(Imagine that, problems caused by disks being to fast instead of to slow)
The KB article related to this problem is
http://support.microsoft.com/kb/810885.
Unfortunately your post didn’t contain the actual error code so I can’t
verify if the problem described in the KB article is the one you are
experiencing. However if the KB article does describe the problem you are
facing installing SQL Server 2000 SP4 would probably solve it.
Let me know if this helps,
Kind regards Leon Krancher.
P.s. Most Servers I know that use a high-end storage device contain more
than 4Gb of ram. If this is also the case in your scenario you might also
want to take a look at http://support.microsoft.com/kb/899761. This KB
article describes a problem with AWE on SQL Servers with SP4 installed and
points to the additional fix that has to be installed to cure this.
"Joe K." wrote:

> I have a server with Windows 2003 Server with SQL Server 2000 Cluster Serv
er.
> What could cause the error listed below with SQL Server 2000.
> Thanks
> Process 174:0 (cb8) UMS Context 0x000006FBFE8C88B1 appears to be
> non-yielding on Scheduler 6
> Process 140:0 (700) UMS Context 0x000006FBFE8A7230 appears to be
> non-yielding on Scheduler 0.|||And it's fixed in SP4
Nik Marshall-Blank MCSD/MCDBA
"Leon" <Leon@.discussions.microsoft.com> wrote in message
news:92979375-B688-4CD1-9B67-3EE1EDAD273E@.microsoft.com...[vbcol=seagreen]
> Hi Joe K,
> I once had a similar problem with SQL Server, in my case it was caused by
> the fact that we used highend SAN's that allocated disk space to quickly.
> (Imagine that, problems caused by disks being to fast instead of to slow)
> The KB article related to this problem is
> http://support.microsoft.com/kb/810885.
> Unfortunately your post didn't contain the actual error code so I can't
> verify if the problem described in the KB article is the one you are
> experiencing. However if the KB article does describe the problem you are
> facing installing SQL Server 2000 SP4 would probably solve it.
> Let me know if this helps,
> Kind regards Leon Krancher.
> P.s. Most Servers I know that use a high-end storage device contain more
> than 4Gb of ram. If this is also the case in your scenario you might also
> want to take a look at http://support.microsoft.com/kb/899761. This KB
> article describes a problem with AWE on SQL Servers with SP4 installed and
> points to the additional fix that has to be installed to cure this.
>
> "Joe K." wrote:
>

Non-Yielding on Scheduler 0.

I have a server with Windows 2003 Server with SQL Server 2000 Cluster Server.
What could cause the error listed below with SQL Server 2000.
Thanks
Process 174:0 (cb8) UMS Context 0x000006FBFE8C88B1 appears to be
non-yielding on Scheduler 6
Process 140:0 (700) UMS Context 0x000006FBFE8A7230 appears to be
non-yielding on Scheduler 0.Hi Joe K,
I once had a similar problem with SQL Server, in my case it was caused by
the fact that we used highend SANâ's that allocated disk space to quickly.
(Imagine that, problems caused by disks being to fast instead of to slow)
The KB article related to this problem is
http://support.microsoft.com/kb/810885.
Unfortunately your post didnâ't contain the actual error code so I canâ't
verify if the problem described in the KB article is the one you are
experiencing. However if the KB article does describe the problem you are
facing installing SQL Server 2000 SP4 would probably solve it.
Let me know if this helps,
Kind regards Leon Krancher.
P.s. Most Servers I know that use a high-end storage device contain more
than 4Gb of ram. If this is also the case in your scenario you might also
want to take a look at http://support.microsoft.com/kb/899761. This KB
article describes a problem with AWE on SQL Servers with SP4 installed and
points to the additional fix that has to be installed to cure this.
"Joe K." wrote:
> I have a server with Windows 2003 Server with SQL Server 2000 Cluster Server.
> What could cause the error listed below with SQL Server 2000.
> Thanks
> Process 174:0 (cb8) UMS Context 0x000006FBFE8C88B1 appears to be
> non-yielding on Scheduler 6
> Process 140:0 (700) UMS Context 0x000006FBFE8A7230 appears to be
> non-yielding on Scheduler 0.|||And it's fixed in SP4
--
Nik Marshall-Blank MCSD/MCDBA
"Leon" <Leon@.discussions.microsoft.com> wrote in message
news:92979375-B688-4CD1-9B67-3EE1EDAD273E@.microsoft.com...
> Hi Joe K,
> I once had a similar problem with SQL Server, in my case it was caused by
> the fact that we used highend SAN's that allocated disk space to quickly.
> (Imagine that, problems caused by disks being to fast instead of to slow)
> The KB article related to this problem is
> http://support.microsoft.com/kb/810885.
> Unfortunately your post didn't contain the actual error code so I can't
> verify if the problem described in the KB article is the one you are
> experiencing. However if the KB article does describe the problem you are
> facing installing SQL Server 2000 SP4 would probably solve it.
> Let me know if this helps,
> Kind regards Leon Krancher.
> P.s. Most Servers I know that use a high-end storage device contain more
> than 4Gb of ram. If this is also the case in your scenario you might also
> want to take a look at http://support.microsoft.com/kb/899761. This KB
> article describes a problem with AWE on SQL Servers with SP4 installed and
> points to the additional fix that has to be installed to cure this.
>
> "Joe K." wrote:
>> I have a server with Windows 2003 Server with SQL Server 2000 Cluster
>> Server.
>> What could cause the error listed below with SQL Server 2000.
>> Thanks
>> Process 174:0 (cb8) UMS Context 0x000006FBFE8C88B1 appears to be
>> non-yielding on Scheduler 6
>> Process 140:0 (700) UMS Context 0x000006FBFE8A7230 appears to be
>> non-yielding on Scheduler 0.sql

non-logged operations

SQL 7.0 SP1 on NT 4 SP6a Cluster.
We have a DB with the option "select into/bulk copy" set to true.
When non-logged operations happens, the backup of the transaction log fail, so we do a differential backup instead and everything is ok.
My questions are:

UPGRADING to SQL 2K,

1 Do we have to choose the "Bulk-Logged" recovery model?
and if so,
2 Do we still need to run differential backup because backup of t-log will fail as on SQL 7.0?
Can somebody help me with this?
TIA.
Franco
:cool:In BULK_LOGGED recovery mode certain bulk operations are only minimally logged increasing performance and decreasing log size. Performing builk operations do not require you to process backup, since they are actually logged thoughout BCM page. For every datafile there is one BCM page where one bit correspond to extent modification by minimally logged operation. When you perform tran log backup, sql scans BCM and backups these extents. As a result you are getting larger tranlog backups then in FULL mode.

HTH,
OBRP

Non sharing data cluster

Hi:

I'm trying to setup a MS Cluster but I don't know if it is feasible to
configure it in the way I think.

I have two machines with win2k server and MSSQL-2000 one of them is
currently performing as the production database and the other one is
the backup. The secondary one is keeping updated via the "Log
Shipping" technic.

We almost covered all the other possible failures of the other
components (ie: network, power, application servers, etc), the data is
maintaned in a raid which is ok but we want to cover also the
possibility of that failure too (yes, you can call us paranoids!! ).

The thing is we want to create a cluster that do not share the data,
but each machine of the cluster have thei own set of the same data.

My intention is to configure the cluster to detect a failure of one
machine and initiate the failover to the remaing one using the
appropiate scripts related to the promotion of a secondary server
keeped updateusing "log shipping".

Have anyone some experience with that kind of solution ??

Thanks in advance

Leonardo"Leonardo C" <lcomunia@.hotmail.com> wrote in message
news:fcc135d.0406150953.6fecf39a@.posting.google.co m...
> Hi:
> I'm trying to setup a MS Cluster but I don't know if it is feasible to
> configure it in the way I think.
> I have two machines with win2k server and MSSQL-2000 one of them is
> currently performing as the production database and the other one is
> the backup. The secondary one is keeping updated via the "Log
> Shipping" technic.
> We almost covered all the other possible failures of the other
> components (ie: network, power, application servers, etc), the data is
> maintaned in a raid which is ok but we want to cover also the
> possibility of that failure too (yes, you can call us paranoids!! ).
> The thing is we want to create a cluster that do not share the data,
> but each machine of the cluster have thei own set of the same data.
> My intention is to configure the cluster to detect a failure of one
> machine and initiate the failover to the remaing one using the
> appropiate scripts related to the promotion of a secondary server
> keeped updateusing "log shipping".
> Have anyone some experience with that kind of solution ??
> Thanks in advance
> Leonardo

I don't believe that's possible with a true cluster - in a cluster, if one
node goes down, its resources are immediately taken over by another node. A
cluster is intended for when you need absolute minimum downtime, but if you
can take the time to apply log shipping scripts, then I guess for you some
downtime is acceptable. In that case, why not just continue to use log
shipping?

But I must admit that I've never used clustering myself, so you might want
to post in microsoft.public.sqlserver.clustering to see if you can get some
more specific comments.

Simon|||Hi Simon:

Thanks for your response. Yes a minimum downtime is acceptable but as Log
Shipping needs a manual intervention a cluster can be the piece to automate
that part.
I'm forwarding this post to the Microsoft groups too, I'm not getting the
other one mentioned by you.

Maybe somebody knows how to automate this, without needing a Cluster.

"Simon Hayes" <sql@.hayes.ch> wrote in message
news:40cf3cc6$1_3@.news.bluewin.ch...
> "Leonardo C" <lcomunia@.hotmail.com> wrote in message
> news:fcc135d.0406150953.6fecf39a@.posting.google.co m...
> > Hi:
> > I'm trying to setup a MS Cluster but I don't know if it is feasible to
> > configure it in the way I think.
> > I have two machines with win2k server and MSSQL-2000 one of them is
> > currently performing as the production database and the other one is
> > the backup. The secondary one is keeping updated via the "Log
> > Shipping" technic.
> > We almost covered all the other possible failures of the other
> > components (ie: network, power, application servers, etc), the data is
> > maintaned in a raid which is ok but we want to cover also the
> > possibility of that failure too (yes, you can call us paranoids!! ).
> > The thing is we want to create a cluster that do not share the data,
> > but each machine of the cluster have thei own set of the same data.
> > My intention is to configure the cluster to detect a failure of one
> > machine and initiate the failover to the remaing one using the
> > appropiate scripts related to the promotion of a secondary server
> > keeped updateusing "log shipping".
> > Have anyone some experience with that kind of solution ??
> > Thanks in advance
> > Leonardo
> I don't believe that's possible with a true cluster - in a cluster, if one
> node goes down, its resources are immediately taken over by another node.
A
> cluster is intended for when you need absolute minimum downtime, but if
you
> can take the time to apply log shipping scripts, then I guess for you some
> downtime is acceptable. In that case, why not just continue to use log
> shipping?
> But I must admit that I've never used clustering myself, so you might want
> to post in microsoft.public.sqlserver.clustering to see if you can get
some
> more specific comments.
> Simon

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 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
>
>