<div>
Yes there is a heart beat network (basically a cross-over cable between the two nodes) that is setup up as mixed. <br />
<br />
The public network is also setup as mixed.
</div>


Yes there is a heart beat network (basically a cross-over cable between the two nodes) that is setup up as mixed.

The public network is also setup as mixed.

<div>
I realized the stupidity of my response and set the heart beat network as private.<br />
<br />
Think that could be what was causing the problem?
</div>


I realized the stupidity of my response and set the heart beat network as private.

Think that could be what was causing the problem?

<div>
Quite possible.<br />
Could review system event log ans cluster log to sure.<br />
<br />
If the public nic is pulled on the active node should see the classic cluster fail over to inactive node.<br />

</div>


Quite possible.
Could review system event log ans cluster log to sure.

If the public nic is pulled on the active node should see the classic cluster fail over to inactive node.


<div>
<div class="content wysiwyg-content">
On a couple of occasions my two node Active-Passive SQL 2005 Cluster has been completely down because both nodes believe itself to be the active node in the cluster, thus generating an IP conflict on the network.<br />
The only way for me to get the cluster started again is to just restart cluster service on both nodes, one at a time.<br />
<br />
It appears that on each occasion, the passive node looses network connection to the active node for a short period and starts th failover process.<br />
<br />
Any ideas what is going on and how to prevent this from happening?
</div>
</div>


On a couple of occasions my two node Active-Passive SQL 2005 Cluster has been completely down because both nodes believe itself to be the active node in the cluster, thus generating an IP conflict on the network.
The only way for me to get the cluster started again is to just restart cluster service on both nodes, one at a time.

It appears that on each occasion, the passive node looses network connection to the active node for a short period and starts th failover process.

Any ideas what is going on and how to prevent this from happening?

SQL 2005 Cluster both nodes believing it is the active node

Microsoft SQL Server 2005 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. It includes support for managing XML data and allows a database server to be exposed over web services using Tabular Data Stream (TDS) packets encapsulated within SOAP (protocol) requests.

Microsoft SQL Server 2005

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.