Re: NLB with 2 NICs question

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



Yes, the heartbeat only travel over the public network meaning the adapter
that NLB is bound to. The heartbeat is an ethernet broadcast directed to
the primary cluster IP address and can not be routed...

We recommend 2 NICS with Unicast mode so that cluster hosts can communicate
between nodes. Please refer to KB "Unicast NLB nodes cannot communicate
over an NLB-enabled network adaptor in Windows Server 2003"
http://support.microsoft.com/?kbid=898867

--
Gary Jackman (MSFTE)
Network Load Balancing Tests


"Jay-nospam" <jaynospam@xxxxxxxxxxxxxx> wrote in message
news:X5qdncRkRuG5NF_enZ2dnUVZ_sudnZ2d@xxxxxxxxxxx
> On the Microsoft Network Load Balancing: Frequently Asked Questions for
> Windows 2000 and Windows 2003 Server, there is a question under NLB for
> High Availability that asks "Q. How Does NLB Detect a Server Failure?".
> The answer is "... each NLB Cluster host emits heartbeats to the other
> hosts in the cluster...."
> Does this heartbeat only travel over the public network? If so, why does
> Microsoft recommend 2 NICS with Unicast mode. I have read in several
> places that the 2nd NIC allows for Intracluster communication. What is
> this?
>
> Thanks,
>
> Jennifer
>
>
> "Chuck Timon [Microsoft]" <ctimon@xxxxxxxxxxxxxxxxxxxx> wrote in message
> news:eCDEdZTFGHA.1032@xxxxxxxxxxxxxxxxxxxxxxx
>> With NLB there is no such thing as heartbeat over a private network and
>> certainly not with a crossover cable.
>>
>> http://support.microsoft.com/default.aspx?scid=kb;[LN];242248
>>
>>
>> --
>> Chuck Timon, Jr.
>> Microsoft Corporation
>> Beta Engineer
>> This posting is provided "AS IS" with no
>> warranties, and confers no rights.
>>
>> "Jay-nospam" <jaynospam@xxxxxxxxxxxxxx> wrote in message
>> news:T_2dnTMOyZr7TCPenZ2dnUVZ_sydnZ2d@xxxxxxxxxxx
>>>I should have said that the NLB Cluster is configured for Unicast Mode. I
>>>also have the Affinity set to None.
>>>
>>> Thanks,
>>>
>>> Jennifer
>>>
>>> "Russ Kaufmann [MVP]" <russ@xxxxxxxxxxxxxxx> wrote in message
>>> news:OzdP8yvEGHA.648@xxxxxxxxxxxxxxxxxxxxxxx
>>>> "Jay-nospam" <jaynospam@xxxxxxxxxxxxxx> wrote in message
>>>> news:YpWdnb1Xj-NHJCPeRVn-tQ@xxxxxxxxxxx
>>>>> Hi,
>>>>>
>>>>> I have 2 Servers set up with NLB with 2 NIC on each server. On each
>>>>> server one NIC is connected to the LAN and uses one subnet,
>>>>> 255.255.255.128. It is called my Public Connection. The other NIC is
>>>>> connected to the other server in the cluster via a crossover cable and
>>>>> uses another subnet, 255.0.0.0. It is called my Private Connection.
>>>>>
>>>>> My Public NIC is 200.200.200.153/5 and my Private NIC is 10.0.0.1/3
>>>>>
>>>>> I am using Load Balancing to set up a Web Farm for a Web application
>>>>> so that I can increase the maximum number of users that the Web
>>>>> application can handle.
>>>>>
>>>>> When I run a stress test using the Virtual IP, the requests seem to be
>>>>> split almost evenly between my 2 servers.
>>>>>
>>>>> When I stop one server (using the Network Load Balancing Manager), all
>>>>> the requests seem to go to the other server and vice versa which is
>>>>> what I would expect.
>>>>>
>>>>> My question is, I see that all the network traffic is only on my
>>>>> Public NIC and nothing seems to happen on my Private NIC.
>>>>>
>>>>> I expected to see some heartbeat traffic on the Private NIC but when I
>>>>> look at the Status, no packets are being sent or received by this NIC.
>>>>>
>>>>> I have also made sure that my Private NIC is listed first in the order
>>>>> of connections in the Advanced Settings for Network Connections.
>>>>>
>>>>> Is there something else I should be doing so that the Private NIC is
>>>>> used?
>>>>
>>>> Configure with Unicast instead of Multicast.
>>>>
>>>>
>>>> --
>>>> Russ Kaufmann
>>>>
>>>> MVP - Windows Server - Clustering
>>>> http://www.clusterhelp.com - Cluster Website
>>>> http://msmvps.com/clusterhelp - Blog
>>>>
>>>>
>>>
>>>
>>
>>
>
>


.



Relevant Pages

  • Re: Convergance of one NLB cluster "takes out" other on same network segment.
    ... No, the heartbeat packets, which are emitted every second by each host, consume less than 1,500 bytes. ... Q. Do the Heartbeats Need to Go on a Back-End Network? ... In fact, in order to be able to detect connectivity failures on the load-balanced network adapter, NLB actually requires that heartbeats traverse the load-balanced network adapter. ... I am not sure yet how Cluster A ever affects Cluster B. Are you connected to a layer 2 or 3 switch? ...
    (microsoft.public.windows.server.clustering)
  • Re: simple question
    ... One on the dedicated network using 192 or whatever. ... NLB Manager say for convergence? ... Rod ... > the unicast mode, and created a dedicated address, i can't ping ISA2 in ...
    (microsoft.public.windows.server.clustering)
  • Re: Subnet error message
    ... as having a seperate network for NLB heaertbeats. ... After disabling the 'heartbeat' NIC, ... >> NLB does not have a heartbeat network (unless you are talking about NLB ...
    (microsoft.public.windows.server.clustering)
  • Re: Convergance of one NLB cluster "takes out" other on same network segment.
    ... Correct I forgot the word network when I said NLB does not have a Heartbeat. ... I am not sure yet how Cluster A ever affects Cluster B. Are you connected to a layer 2 or 3 switch? ...
    (microsoft.public.windows.server.clustering)
  • Re: Convergance of one NLB cluster "takes out" other on same network segment.
    ... Heartbeat. ... Q. Do the Heartbeats Need to Go on a Back-End Network? ... In fact, in order to be able to detect connectivity failures on the load-balanced network adapter, NLB actually requires that heartbeats traverse the load-balanced network adapter. ... I am not sure yet how Cluster A ever affects Cluster B. Are you connected to a layer 2 or 3 switch? ...
    (microsoft.public.windows.server.clustering)