Heartbeat Network Adapter

How do I go about setting this up? I am very confused by this piece of the
cluster set up? Do I define this in the Cluster Admin or actually create two
new network adapters (one on each server in the cluser) in my Network
Connections? There are only two servers in this cluster if that makes a
difference.

Jeff,

In a two node cluster you will need a nic dedicated for the heartbeat and
connected directly from one server to the other using a crossover cable.
Typically you using an address like 10.1.1.1 for one server and then 10.1.1.2
for the other. If you are going Win2k3 with more than 2 nodes then you need
a hub with normal network cables. If you only have two nics then one must be
used for the heartbeat. The problem with this is now you have a single point
of failure if you do not have redundant nics. Hope that helps.
--
Mark


"Jeff M" wrote:

> How do I go about setting this up? I am very confused by this piece of the
> cluster set up? Do I define this in the Cluster Admin or actually create two
> new network adapters (one on each server in the cluser) in my Network
> Connections? There are only two servers in this cluster if that makes a
> difference.

Right now we have two nics in each server. One production LAN and the second
being for the backup LAN. Sounds like I need to get a third NIC card for
each box and a crossover cable to solve this problem.

"MarkFox" wrote:

> Jeff,
>
> In a two node cluster you will need a nic dedicated for the heartbeat and
> connected directly from one server to the other using a crossover cable.
> Typically you using an address like 10.1.1.1 for one server and then 10.1.1.2
> for the other. If you are going Win2k3 with more than 2 nodes then you need
> a hub with normal network cables. If you only have two nics then one must be
> used for the heartbeat. The problem with this is now you have a single point
> of failure if you do not have redundant nics. Hope that helps.
> --
> Mark
>
>
> "Jeff M" wrote:
>
> > How do I go about setting this up? I am very confused by this piece of the
> > cluster set up? Do I define this in the Cluster Admin or actually create two
> > new network adapters (one on each server in the cluser) in my Network
> > Connections? There are only two servers in this cluster if that makes a
> > difference.

Absolutely. Follow this article for more info on Clustering networking
requirements / design:

Server Clusters: Network Configuration Best Practices for Windows 2000 and
Windows Server 2003
http://www.microsoft.com/technet/pro.../clstntbp.mspx

Hope this helps,
--Ryan

--
--
Ryan Sokolowski
MVP - Windows Server - Clustering
MCSE, CCNA, CCDA, BCFP

"A troubleshooter's best tool is the Event Viewer and understanding the
events and messages contained therein."

This posting is provided "AS IS" with no warranties, and confers no rights.

"Jeff M" <> wrote in message
news:0DCE545D-AA67-4B26-9B9B-...
> Right now we have two nics in each server. One production LAN and the
> second
> being for the backup LAN. Sounds like I need to get a third NIC card for
> each box and a crossover cable to solve this problem.
>
> "MarkFox" wrote:
>
>> Jeff,
>>
>> In a two node cluster you will need a nic dedicated for the heartbeat and
>> connected directly from one server to the other using a crossover cable.
>> Typically you using an address like 10.1.1.1 for one server and then
>> 10.1.1.2
>> for the other. If you are going Win2k3 with more than 2 nodes then you
>> need
>> a hub with normal network cables. If you only have two nics then one
>> must be
>> used for the heartbeat. The problem with this is now you have a single
>> point
>> of failure if you do not have redundant nics. Hope that helps.
>> --
>> Mark
>>
>>
>> "Jeff M" wrote:
>>
>> > How do I go about setting this up? I am very confused by this piece of
>> > the
>> > cluster set up? Do I define this in the Cluster Admin or actually
>> > create two
>> > new network adapters (one on each server in the cluser) in my Network
>> > Connections? There are only two servers in this cluster if that makes
>> > a
>> > difference.

Thanks for the reply Ryan. Ok how about this one then. Both of my new
servers are HP DL360's with both of there internal PCI slots taken up by
fibre cards. That leaves no slot for a dedicated NIC as the heartbeat. By
default will one of the other NICS just take over as a heartbeat in addition
to functioning as either the prod network or backup lan?

"Ryan Sokolowski (MVP)" wrote:

> Absolutely. Follow this article for more info on Clustering networking
> requirements / design:
>
> Server Clusters: Network Configuration Best Practices for Windows 2000 and
> Windows Server 2003
> http://www.microsoft.com/technet/pro.../clstntbp.mspx
>
> Hope this helps,
> --Ryan
>
> --
> --
> Ryan Sokolowski
> MVP - Windows Server - Clustering
> MCSE, CCNA, CCDA, BCFP
>
> "A troubleshooter's best tool is the Event Viewer and understanding the
> events and messages contained therein."
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Jeff M" <> wrote in message
> news:0DCE545D-AA67-4B26-9B9B-...
> > Right now we have two nics in each server. One production LAN and the
> > second
> > being for the backup LAN. Sounds like I need to get a third NIC card for
> > each box and a crossover cable to solve this problem.
> >
> > "MarkFox" wrote:
> >
> >> Jeff,
> >>
> >> In a two node cluster you will need a nic dedicated for the heartbeat and
> >> connected directly from one server to the other using a crossover cable.
> >> Typically you using an address like 10.1.1.1 for one server and then
> >> 10.1.1.2
> >> for the other. If you are going Win2k3 with more than 2 nodes then you
> >> need
> >> a hub with normal network cables. If you only have two nics then one
> >> must be
> >> used for the heartbeat. The problem with this is now you have a single
> >> point
> >> of failure if you do not have redundant nics. Hope that helps.
> >> --
> >> Mark
> >>
> >>
> >> "Jeff M" wrote:
> >>
> >> > How do I go about setting this up? I am very confused by this piece of
> >> > the
> >> > cluster set up? Do I define this in the Cluster Admin or actually
> >> > create two
> >> > new network adapters (one on each server in the cluser) in my Network
> >> > Connections? There are only two servers in this cluster if that makes
> >> > a
> >> > difference.
>
>
>

I guess you could configure the Backup LAN NICs as the HB NICs within
Cluster Administrator. Make sure to follow the steps carefully to ensure
that you're actually using the NICs you think you are for each distinct
purpose. Never leave anything as "by default" when doing clustering - it's
too important to just be cavalier with it.

Glad to hear you're using multipath Fibre Channel (P.S. - this is why you
might have wanted to use a DL380 instead - extra PCI slots.)

--
--
Ryan Sokolowski
MVP - Windows Server - Clustering
MCSE, CCNA, CCDA, BCFP

"A troubleshooter's best tool is the Event Viewer and understanding the
events and messages contained therein."

This posting is provided "AS IS" with no warranties, and confers no rights.

"Jeff M" <> wrote in message
news:5F2103B6-D6B3-4397-8169-...
> Thanks for the reply Ryan. Ok how about this one then. Both of my new
> servers are HP DL360's with both of there internal PCI slots taken up by
> fibre cards. That leaves no slot for a dedicated NIC as the heartbeat.
> By
> default will one of the other NICS just take over as a heartbeat in
> addition
> to functioning as either the prod network or backup lan?
>
> "Ryan Sokolowski (MVP)" wrote:
>
>> Absolutely. Follow this article for more info on Clustering networking
>> requirements / design:
>>
>> Server Clusters: Network Configuration Best Practices for Windows 2000
>> and
>> Windows Server 2003
>> http://www.microsoft.com/technet/pro.../clstntbp.mspx
>>
>> Hope this helps,
>> --Ryan
>>
>> --
>> --
>> Ryan Sokolowski
>> MVP - Windows Server - Clustering
>> MCSE, CCNA, CCDA, BCFP
>>
>> "A troubleshooter's best tool is the Event Viewer and understanding the
>> events and messages contained therein."
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Jeff M" <> wrote in message
>> news:0DCE545D-AA67-4B26-9B9B-...
>> > Right now we have two nics in each server. One production LAN and the
>> > second
>> > being for the backup LAN. Sounds like I need to get a third NIC card
>> > for
>> > each box and a crossover cable to solve this problem.
>> >
>> > "MarkFox" wrote:
>> >
>> >> Jeff,
>> >>
>> >> In a two node cluster you will need a nic dedicated for the heartbeat
>> >> and
>> >> connected directly from one server to the other using a crossover
>> >> cable.
>> >> Typically you using an address like 10.1.1.1 for one server and then
>> >> 10.1.1.2
>> >> for the other. If you are going Win2k3 with more than 2 nodes then
>> >> you
>> >> need
>> >> a hub with normal network cables. If you only have two nics then one
>> >> must be
>> >> used for the heartbeat. The problem with this is now you have a
>> >> single
>> >> point
>> >> of failure if you do not have redundant nics. Hope that helps.
>> >> --
>> >> Mark
>> >>
>> >>
>> >> "Jeff M" wrote:
>> >>
>> >> > How do I go about setting this up? I am very confused by this piece
>> >> > of
>> >> > the
>> >> > cluster set up? Do I define this in the Cluster Admin or actually
>> >> > create two
>> >> > new network adapters (one on each server in the cluser) in my
>> >> > Network
>> >> > Connections? There are only two servers in this cluster if that
>> >> > makes
>> >> > a
>> >> > difference.
>>
>>
>>

I agree wiht you on the DL380 for its addtl' slots. Yea, the fibre is pretty
cool. Our backbone runs on it across our campus. I will take a look at
configuring the backup nics as HB's within cluster administrator. I had one
addtil' question from another post. Is there any way to export info
regarding RESOURCES from my existing cluster to the new cluster I am working
on?

"Ryan Sokolowski (MVP)" wrote:

> I guess you could configure the Backup LAN NICs as the HB NICs within
> Cluster Administrator. Make sure to follow the steps carefully to ensure
> that you're actually using the NICs you think you are for each distinct
> purpose. Never leave anything as "by default" when doing clustering - it's
> too important to just be cavalier with it.
>
> Glad to hear you're using multipath Fibre Channel (P.S. - this is why you
> might have wanted to use a DL380 instead - extra PCI slots.)
>
> --
> --
> Ryan Sokolowski
> MVP - Windows Server - Clustering
> MCSE, CCNA, CCDA, BCFP
>
> "A troubleshooter's best tool is the Event Viewer and understanding the
> events and messages contained therein."
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Jeff M" <> wrote in message
> news:5F2103B6-D6B3-4397-8169-...
> > Thanks for the reply Ryan. Ok how about this one then. Both of my new
> > servers are HP DL360's with both of there internal PCI slots taken up by
> > fibre cards. That leaves no slot for a dedicated NIC as the heartbeat.
> > By
> > default will one of the other NICS just take over as a heartbeat in
> > addition
> > to functioning as either the prod network or backup lan?
> >
> > "Ryan Sokolowski (MVP)" wrote:
> >
> >> Absolutely. Follow this article for more info on Clustering networking
> >> requirements / design:
> >>
> >> Server Clusters: Network Configuration Best Practices for Windows 2000
> >> and
> >> Windows Server 2003
> >> http://www.microsoft.com/technet/pro.../clstntbp.mspx
> >>
> >> Hope this helps,
> >> --Ryan
> >>
> >> --
> >> --
> >> Ryan Sokolowski
> >> MVP - Windows Server - Clustering
> >> MCSE, CCNA, CCDA, BCFP
> >>
> >> "A troubleshooter's best tool is the Event Viewer and understanding the
> >> events and messages contained therein."
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "Jeff M" <> wrote in message
> >> news:0DCE545D-AA67-4B26-9B9B-...
> >> > Right now we have two nics in each server. One production LAN and the
> >> > second
> >> > being for the backup LAN. Sounds like I need to get a third NIC card
> >> > for
> >> > each box and a crossover cable to solve this problem.
> >> >
> >> > "MarkFox" wrote:
> >> >
> >> >> Jeff,
> >> >>
> >> >> In a two node cluster you will need a nic dedicated for the heartbeat
> >> >> and
> >> >> connected directly from one server to the other using a crossover
> >> >> cable.
> >> >> Typically you using an address like 10.1.1.1 for one server and then
> >> >> 10.1.1.2
> >> >> for the other. If you are going Win2k3 with more than 2 nodes then
> >> >> you
> >> >> need
> >> >> a hub with normal network cables. If you only have two nics then one
> >> >> must be
> >> >> used for the heartbeat. The problem with this is now you have a
> >> >> single
> >> >> point
> >> >> of failure if you do not have redundant nics. Hope that helps.
> >> >> --
> >> >> Mark
> >> >>
> >> >>
> >> >> "Jeff M" wrote:
> >> >>
> >> >> > How do I go about setting this up? I am very confused by this piece
> >> >> > of
> >> >> > the
> >> >> > cluster set up? Do I define this in the Cluster Admin or actually
> >> >> > create two
> >> >> > new network adapters (one on each server in the cluser) in my
> >> >> > Network
> >> >> > Connections? There are only two servers in this cluster if that
> >> >> > makes
> >> >> > a
> >> >> > difference.
> >>
> >>
> >>
>
>
>

this is only one of the many problems you can have wtih the limited chassis
of the DL360....Poor choice for cluster nodes.

"Jeff M" wrote:

> I agree wiht you on the DL380 for its addtl' slots. Yea, the fibre is pretty
> cool. Our backbone runs on it across our campus. I will take a look at
> configuring the backup nics as HB's within cluster administrator. I had one
> addtil' question from another post. Is there any way to export info
> regarding RESOURCES from my existing cluster to the new cluster I am working
> on?
>
> "Ryan Sokolowski (MVP)" wrote:
>
> > I guess you could configure the Backup LAN NICs as the HB NICs within
> > Cluster Administrator. Make sure to follow the steps carefully to ensure
> > that you're actually using the NICs you think you are for each distinct
> > purpose. Never leave anything as "by default" when doing clustering - it's
> > too important to just be cavalier with it.
> >
> > Glad to hear you're using multipath Fibre Channel (P.S. - this is why you
> > might have wanted to use a DL380 instead - extra PCI slots.)
> >
> > --
> > --
> > Ryan Sokolowski
> > MVP - Windows Server - Clustering
> > MCSE, CCNA, CCDA, BCFP
> >
> > "A troubleshooter's best tool is the Event Viewer and understanding the
> > events and messages contained therein."
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> > "Jeff M" <> wrote in message
> > news:5F2103B6-D6B3-4397-8169-...
> > > Thanks for the reply Ryan. Ok how about this one then. Both of my new
> > > servers are HP DL360's with both of there internal PCI slots taken up by
> > > fibre cards. That leaves no slot for a dedicated NIC as the heartbeat.
> > > By
> > > default will one of the other NICS just take over as a heartbeat in
> > > addition
> > > to functioning as either the prod network or backup lan?
> > >
> > > "Ryan Sokolowski (MVP)" wrote:
> > >
> > >> Absolutely. Follow this article for more info on Clustering networking
> > >> requirements / design:
> > >>
> > >> Server Clusters: Network Configuration Best Practices for Windows 2000
> > >> and
> > >> Windows Server 2003
> > >> http://www.microsoft.com/technet/pro.../clstntbp.mspx
> > >>
> > >> Hope this helps,
> > >> --Ryan
> > >>
> > >> --
> > >> --
> > >> Ryan Sokolowski
> > >> MVP - Windows Server - Clustering
> > >> MCSE, CCNA, CCDA, BCFP
> > >>
> > >> "A troubleshooter's best tool is the Event Viewer and understanding the
> > >> events and messages contained therein."
> > >>
> > >> This posting is provided "AS IS" with no warranties, and confers no
> > >> rights.
> > >>
> > >> "Jeff M" <> wrote in message
> > >> news:0DCE545D-AA67-4B26-9B9B-...
> > >> > Right now we have two nics in each server. One production LAN and the
> > >> > second
> > >> > being for the backup LAN. Sounds like I need to get a third NIC card
> > >> > for
> > >> > each box and a crossover cable to solve this problem.
> > >> >
> > >> > "MarkFox" wrote:
> > >> >
> > >> >> Jeff,
> > >> >>
> > >> >> In a two node cluster you will need a nic dedicated for the heartbeat
> > >> >> and
> > >> >> connected directly from one server to the other using a crossover
> > >> >> cable.
> > >> >> Typically you using an address like 10.1.1.1 for one server and then
> > >> >> 10.1.1.2
> > >> >> for the other. If you are going Win2k3 with more than 2 nodes then
> > >> >> you
> > >> >> need
> > >> >> a hub with normal network cables. If you only have two nics then one
> > >> >> must be
> > >> >> used for the heartbeat. The problem with this is now you have a
> > >> >> single
> > >> >> point
> > >> >> of failure if you do not have redundant nics. Hope that helps.
> > >> >> --
> > >> >> Mark
> > >> >>
> > >> >>
> > >> >> "Jeff M" wrote:
> > >> >>
> > >> >> > How do I go about setting this up? I am very confused by this piece
> > >> >> > of
> > >> >> > the
> > >> >> > cluster set up? Do I define this in the Cluster Admin or actually
> > >> >> > create two
> > >> >> > new network adapters (one on each server in the cluser) in my
> > >> >> > Network
> > >> >> > Connections? There are only two servers in this cluster if that
> > >> >> > makes
> > >> >> > a
> > >> >> > difference.
> > >>
> > >>
> > >>
> >
> >
> >

Thanks Jasen for the judgement of the chassis that I got stuck with. In a
perfect world I would not have ordered those either. But regardless I have
to make it work which is what I am doing.

"Jasen" wrote:

> this is only one of the many problems you can have wtih the limited chassis
> of the DL360....Poor choice for cluster nodes.
>
> "Jeff M" wrote:
>
> > I agree wiht you on the DL380 for its addtl' slots. Yea, the fibre is pretty
> > cool. Our backbone runs on it across our campus. I will take a look at
> > configuring the backup nics as HB's within cluster administrator. I had one
> > addtil' question from another post. Is there any way to export info
> > regarding RESOURCES from my existing cluster to the new cluster I am working
> > on?
> >
> > "Ryan Sokolowski (MVP)" wrote:
> >
> > > I guess you could configure the Backup LAN NICs as the HB NICs within
> > > Cluster Administrator. Make sure to follow the steps carefully to ensure
> > > that you're actually using the NICs you think you are for each distinct
> > > purpose. Never leave anything as "by default" when doing clustering - it's
> > > too important to just be cavalier with it.
> > >
> > > Glad to hear you're using multipath Fibre Channel (P.S. - this is why you
> > > might have wanted to use a DL380 instead - extra PCI slots.)
> > >
> > > --
> > > --
> > > Ryan Sokolowski
> > > MVP - Windows Server - Clustering
> > > MCSE, CCNA, CCDA, BCFP
> > >
> > > "A troubleshooter's best tool is the Event Viewer and understanding the
> > > events and messages contained therein."
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > >
> > > "Jeff M" <> wrote in message
> > > news:5F2103B6-D6B3-4397-8169-...
> > > > Thanks for the reply Ryan. Ok how about this one then. Both of my new
> > > > servers are HP DL360's with both of there internal PCI slots taken up by
> > > > fibre cards. That leaves no slot for a dedicated NIC as the heartbeat.
> > > > By
> > > > default will one of the other NICS just take over as a heartbeat in
> > > > addition
> > > > to functioning as either the prod network or backup lan?
> > > >
> > > > "Ryan Sokolowski (MVP)" wrote:
> > > >
> > > >> Absolutely. Follow this article for more info on Clustering networking
> > > >> requirements / design:
> > > >>
> > > >> Server Clusters: Network Configuration Best Practices for Windows 2000
> > > >> and
> > > >> Windows Server 2003
> > > >> http://www.microsoft.com/technet/pro.../clstntbp.mspx
> > > >>
> > > >> Hope this helps,
> > > >> --Ryan
> > > >>
> > > >> --
> > > >> --
> > > >> Ryan Sokolowski
> > > >> MVP - Windows Server - Clustering
> > > >> MCSE, CCNA, CCDA, BCFP
> > > >>
> > > >> "A troubleshooter's best tool is the Event Viewer and understanding the
> > > >> events and messages contained therein."
> > > >>
> > > >> This posting is provided "AS IS" with no warranties, and confers no
> > > >> rights.
> > > >>
> > > >> "Jeff M" <> wrote in message
> > > >> news:0DCE545D-AA67-4B26-9B9B-...
> > > >> > Right now we have two nics in each server. One production LAN and the
> > > >> > second
> > > >> > being for the backup LAN. Sounds like I need to get a third NIC card
> > > >> > for
> > > >> > each box and a crossover cable to solve this problem.
> > > >> >
> > > >> > "MarkFox" wrote:
> > > >> >
> > > >> >> Jeff,
> > > >> >>
> > > >> >> In a two node cluster you will need a nic dedicated for the heartbeat
> > > >> >> and
> > > >> >> connected directly from one server to the other using a crossover
> > > >> >> cable.
> > > >> >> Typically you using an address like 10.1.1.1 for one server and then
> > > >> >> 10.1.1.2
> > > >> >> for the other. If you are going Win2k3 with more than 2 nodes then
> > > >> >> you
> > > >> >> need
> > > >> >> a hub with normal network cables. If you only have two nics then one
> > > >> >> must be
> > > >> >> used for the heartbeat. The problem with this is now you have a
> > > >> >> single
> > > >> >> point
> > > >> >> of failure if you do not have redundant nics. Hope that helps.
> > > >> >> --
> > > >> >> Mark
> > > >> >>
> > > >> >>
> > > >> >> "Jeff M" wrote:
> > > >> >>
> > > >> >> > How do I go about setting this up? I am very confused by this piece
> > > >> >> > of
> > > >> >> > the
> > > >> >> > cluster set up? Do I define this in the Cluster Admin or actually
> > > >> >> > create two
> > > >> >> > new network adapters (one on each server in the cluser) in my
> > > >> >> > Network
> > > >> >> > Connections? There are only two servers in this cluster if that
> > > >> >> > makes
> > > >> >> > a
> > > >> >> > difference.
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >

Ryan, do you have a doc that shows the steps for the config of my backup nics
to act as heartbeat as well? I don't want to take a misstep in doing this.
Thanks

"Ryan Sokolowski (MVP)" wrote:

> I guess you could configure the Backup LAN NICs as the HB NICs within
> Cluster Administrator. Make sure to follow the steps carefully to ensure
> that you're actually using the NICs you think you are for each distinct
> purpose. Never leave anything as "by default" when doing clustering - it's
> too important to just be cavalier with it.
>
> Glad to hear you're using multipath Fibre Channel (P.S. - this is why you
> might have wanted to use a DL380 instead - extra PCI slots.)
>
> --
> --
> Ryan Sokolowski
> MVP - Windows Server - Clustering
> MCSE, CCNA, CCDA, BCFP
>
> "A troubleshooter's best tool is the Event Viewer and understanding the
> events and messages contained therein."
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Jeff M" <> wrote in message
> news:5F2103B6-D6B3-4397-8169-...
> > Thanks for the reply Ryan. Ok how about this one then. Both of my new
> > servers are HP DL360's with both of there internal PCI slots taken up by
> > fibre cards. That leaves no slot for a dedicated NIC as the heartbeat.
> > By
> > default will one of the other NICS just take over as a heartbeat in
> > addition
> > to functioning as either the prod network or backup lan?
> >
> > "Ryan Sokolowski (MVP)" wrote:
> >
> >> Absolutely. Follow this article for more info on Clustering networking
> >> requirements / design:
> >>
> >> Server Clusters: Network Configuration Best Practices for Windows 2000
> >> and
> >> Windows Server 2003
> >> http://www.microsoft.com/technet/pro.../clstntbp.mspx
> >>
> >> Hope this helps,
> >> --Ryan
> >>
> >> --
> >> --
> >> Ryan Sokolowski
> >> MVP - Windows Server - Clustering
> >> MCSE, CCNA, CCDA, BCFP
> >>
> >> "A troubleshooter's best tool is the Event Viewer and understanding the
> >> events and messages contained therein."
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "Jeff M" <> wrote in message
> >> news:0DCE545D-AA67-4B26-9B9B-...
> >> > Right now we have two nics in each server. One production LAN and the
> >> > second
> >> > being for the backup LAN. Sounds like I need to get a third NIC card
> >> > for
> >> > each box and a crossover cable to solve this problem.
> >> >
> >> > "MarkFox" wrote:
> >> >
> >> >> Jeff,
> >> >>
> >> >> In a two node cluster you will need a nic dedicated for the heartbeat
> >> >> and
> >> >> connected directly from one server to the other using a crossover
> >> >> cable.
> >> >> Typically you using an address like 10.1.1.1 for one server and then
> >> >> 10.1.1.2
> >> >> for the other. If you are going Win2k3 with more than 2 nodes then
> >> >> you
> >> >> need
> >> >> a hub with normal network cables. If you only have two nics then one
> >> >> must be
> >> >> used for the heartbeat. The problem with this is now you have a
> >> >> single
> >> >> point
> >> >> of failure if you do not have redundant nics. Hope that helps.
> >> >> --
> >> >> Mark
> >> >>
> >> >>
> >> >> "Jeff M" wrote:
> >> >>
> >> >> > How do I go about setting this up? I am very confused by this piece
> >> >> > of
> >> >> > the
> >> >> > cluster set up? Do I define this in the Cluster Admin or actually
> >> >> > create two
> >> >> > new network adapters (one on each server in the cluser) in my
> >> >> > Network
> >> >> > Connections? There are only two servers in this cluster if that
> >> >> > makes
> >> >> > a
> >> >> > difference.
> >>
> >>
> >>
>
>
>