How do I add a network connection to an existing Win2K3 cluster?

I have a Windows 2003 cluster already built. For some reason, the secondary
NIC for the private (heartbeat) network connection did not get added to the
cluster. I am trying to figure out how to add it in. It is not a cluster
resource, so I cannot add it that way. Does anyone have any suggestions?

I suppose, I need to figure out how to enable a network connection for
cluster use.

Thank you,

Racer-D

This is normal. The cluster should show this as a private communications
path but NOT with public virtual IP addresses on it.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP


"Racer-D" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
>I have a Windows 2003 cluster already built. For some reason, the secondary
> NIC for the private (heartbeat) network connection did not get added to
> the
> cluster. I am trying to figure out how to add it in. It is not a cluster
> resource, so I cannot add it that way. Does anyone have any suggestions?
>
> I suppose, I need to figure out how to enable a network connection for
> cluster use.
>
> Thank you,
>
> Racer-D
>
>

There should be two private network connections available in cluster
administrator. On each node I have 1 public network connection, and two
connections for the private network connections.

In cluster administrator I only see 1 public network connection and 1
private network connection.

I hope that clarifies the issue.

Thank you,

Racer-D

"Geoff N. Hiten" <(E-Mail Removed)> wrote in message
news:excPV%(E-Mail Removed)...
> This is normal. The cluster should show this as a private communications
> path but NOT with public virtual IP addresses on it.
>
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Racer-D" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>>I have a Windows 2003 cluster already built. For some reason, the
>>secondary
>> NIC for the private (heartbeat) network connection did not get added to
>> the
>> cluster. I am trying to figure out how to add it in. It is not a cluster
>> resource, so I cannot add it that way. Does anyone have any suggestions?
>>
>> I suppose, I need to figure out how to enable a network connection for
>> cluster use.
>>
>> Thank you,
>>
>> Racer-D
>>
>>
>
>

It is common practice to allow the public network to pass private messages.
More paths = better availability.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP


"Racer-D" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> There should be two private network connections available in cluster
> administrator. On each node I have 1 public network connection, and two
> connections for the private network connections.
>
> In cluster administrator I only see 1 public network connection and 1
> private network connection.
>
> I hope that clarifies the issue.
>
> Thank you,
>
> Racer-D
>
> "Geoff N. Hiten" <(E-Mail Removed)> wrote in message
> news:excPV%(E-Mail Removed)...
>> This is normal. The cluster should show this as a private communications
>> path but NOT with public virtual IP addresses on it.
>>
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>>
>> "Racer-D" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>>I have a Windows 2003 cluster already built. For some reason, the
>>>secondary
>>> NIC for the private (heartbeat) network connection did not get added to
>>> the
>>> cluster. I am trying to figure out how to add it in. It is not a cluster
>>> resource, so I cannot add it that way. Does anyone have any suggestions?
>>>
>>> I suppose, I need to figure out how to enable a network connection for
>>> cluster use.
>>>
>>> Thank you,
>>>
>>> Racer-D
>>>
>>>
>>
>>
>
>