RE: NLB heartbeat clarification please.

Tech-Archive recommends: Fix windows errors by optimizing your registry

Jonny

The two nics as you mention below is the recommend way Microsoft suggests
you setup an NLB Cluster. Cluster Nic which houses the NLB VIP and the other
adapter is referred to as the Dedicated NIC. The Deficated Nic is used for
management and unique IP identification for that specific cluster node. In
other words the Dedicated NIC will have an IP Address that is different among
all of your NLB cluster Nodes. From the two NIC setup you have a few options:

1. Are the NICs going to be on the same subnet?

2. Are the NICs going to be on differnent subnets?

3. Are you going to use Unicast Mode?

4. Are you going to use Multicast Mode?


http://www.windowsitpro.com/Windows/Article/ArticleID/15724/15724.html

"Johnny Lundgren" wrote:

> Hello,
>
> I have done a lot of clustering with MSCS but nothing with the NLB protocol.
> What strikes me the most when reading manuals, books and MS Technet articles
> on this subject, is the confusion about what the NIC:s are for in each of
> the servers.
>
> Please clear the following out for me:
>
> If I have two NIC:s in each of the two servers that are going to be used in
> a NLB cluster, one adapter in each server is to be used as an
> cluster-adapter (VIP).
> The other adapter, on the other hand, I have found different explanations of
> the usage.
>
> One explanation is that it is a NIC on a private network where all the
> heartbeat traffic is routed (just as in MSCS).
> Explanation number two is that all the heartbeat traffic is going through
> the cluster adapter (and not the private adapter at all) and that the
> private adapter is a management adapter of which you can manage the nodes
> via NLB Manager.
>
> MS is also recommending not to use a crossover cable between the two servers
> since the private adapters need to know about the traffic on the public
> network.
> Confusion !
>
> This needs a clarification. Please be specific on how to set the NIC:s up
> and what they are really for.
>
> Regards
>
> Johnny Lundgren
>
>
>
.

Relevant Pages

  • RE: NLB heartbeat clarification please.
    ... Today I have an Oracle/Domino back-end cluster based on Win2k3 EE. ... question is how many public IP-addresses will I need (two servers - two NICs) ... > adapter is referred to as the Dedicated NIC. ...
    (microsoft.public.windows.server.clustering)
  • Re: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
    ... Windows Server 2008 Readiness Team ... cluster on a separate DLink card in multicast mode. ... I thought that the litmus test was that the router functions fine ... member of the NLB cluster, setup NLB on it, plug the NICs ...
    (microsoft.public.windows.server.clustering)
  • Re: Event IDs 1122 and 1123
    ... These errors are usually causes by NIC drivers or faulty network components ... latest/greatest drivers...especially if your using Broadcom NICs. ... > Myself and Simon went in on Friday to dissolve teaming on the cluster nics ... > the AD when the first node boots up. ...
    (microsoft.public.windows.server.clustering)
  • Re: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
    ... NIC for the Cluster ... separate adapter about 10Mbps to the database server. ... There should be no reason for the router to discard/ignore/forget ARP ... I have disabled one of the Broadcom NICs, (NIC1 which had an IP from ...
    (microsoft.public.windows.server.clustering)
  • Re: Heartbeat Network Adapter
    ... I guess you could configure the Backup LAN NICs as the HB NICs within ... Cluster Administrator. ... MVP - Windows Server - Clustering ... Network Configuration Best Practices for Windows 2000 ...
    (microsoft.public.windows.server.clustering)