Re: Can see all interfaces with NLB when adding a host

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Yes, read and followed both of those documents and just re-read them at your
suggestion.

The NICs are set to "Automatic metric". Should they be? Maybe I missed
that in the document.

"Mike Rosado [MSFT]" wrote:

> Hello,
>
> Did you use the following articles in configuring Network Load Balance?
>
> 323431 How To Set Up TCP/IP for Network Load Balancing in Windows Server 2003
> http://support.microsoft.com/?id=323431
>
> 323437 How To Configure Network Load Balancing Parameters in Windows Server 2003
> http://support.microsoft.com/?id=323437
>
> Did you setup the Metric on each of the NICs or are they setup using Automatic Metric?
>
> --
> Hope this helps,
> Mike Rosado
> Windows 2000 MCSE + MCDBA
> Microsoft Enterprise Platform Support
> Windows NT/2000/2003 Cluster Technologies
>
> ====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> <http://www.microsoft.com/info/cpyright.htm>
>
> -----Original Message-----
> > From: <dungeoncrawl@xxxxxxxxxxxxxxxxxxxxxxxxx>
> > Subject: Re: Can see all interfaces with NLB when adding a host
> > Date: Thu, 7 Apr 2005 14:01:28 -0700
> >
> > Ryan,
> > Unfortunately, that didn't help. I'm seeing the EXACT same behavior
> > even though I've changed the management interfaces to 192.168.1.191 and .192
> > respectively. When I try to add the second node by point to 192.168.1.192,
> > it comes back with ONLY the 192.168.1.192 interface as an option to add to
> > the cluster. What happens to the 172.16.254.92 Interface?
> >
> > "Ryan Sokolowski [Avanade]" wrote:
> >
> > > First of all, I would definitely recommend separating the MGMT and Cluster
> > > NICs out onto separate IP Subnets. Move the MGMT NICS to a 192.168.1.x
> > > range and see if that solves your issues...if not, let us know and I can
> > > attach more detailed steps to set-up 2 NIC NLB clusters...
> > >
> > > I would suspect that the issues lies with both NICs being on the same subnet
> > > and being able to see each other (and both having a default gateway on their
> > > network)...
> > >
> > > Hope this helps,
> > >
> > > --
> > > Ryan Sokolowski
> > > MCSE, CCNA, CCDA, BCFP
> > > Avanade
> > > http://www.Avanade.com
> > >
> > > "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.
> > >
> > > "dungeoncrawl" <dungeoncrawl@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > news:378E0766-6753-47AC-92B8-CA1EB7A0669E@xxxxxxxxxxxxxxxx
> > > > I'm setting up my first NLB cluster and can't get a system to show me both
> > > > NICs when trying to add it to the cluster. I have 2 systems with 2 NICs
> > > > with
> > > > static IP addresses as follows:
> > > >
> > > > Server A
> > > > NIC 1: 172.16.254.81 For cluster
> > > > NIC 2: 172.16.254.91 For mgt access
> > > >
> > > > Server B
> > > > NIC 1: 172.16.254.82 For cluster
> > > > NIC 2: 172.16.254.92 For mgt access.
> > > >
> > > > When I create my cluster (VIP = 172.16.254.75, unicast mode), I point it
> > > > to
> > > > the mgt interface on server A. When it comes up, I can see both NICs and
> > > > I
> > > > choose NIC 2 to be part of the cluster and it works fine.
> > > >
> > > > However, when I then try to add a host, I shoose the mgt interface for
> > > > Server B and I ONLY SEE NIC2 available. I had wanted to see NIC1 since it
> > > > was really the system I wanted to add to the cluster.
> > > >
> > > > If I clear the cluster and start over but choose Server B first, I can see
> > > > both NICs just fine. But when I then go to add Server A to the
> > > > cluster...what do you know I can only see one NIC...the mgt NIC. Any
> > > > ideas?
> > >
> > >
> > >
> >
>
>
>
.



Relevant Pages

  • Re: NLB Heartbeat/private network
    ... Configure Network Load Balancing (NLB) with Two Network Adapters ... Configure the NLB Cluster properties according to your parameters, ... Both machines have 2 NICs. ...
    (microsoft.public.windows.server.clustering)
  • Re: NLB Terminal Servers
    ... 323431 How To Set Up TCP/IP for Network Load Balancing in Windows Server ... Windows NT/2000/2003 Cluster Technologies ... > Subject: Re: NLB Terminal Servers ...
    (microsoft.public.windows.server.clustering)
  • RE: How to configure Network Load Balancing using Two Node?
    ... Cluster Services and Network Load Balance work together on the ... If you are looking to setup NLB correctly on Windows Server 2003, ... 323437 How To Configure Network Load Balancing Parameters in Windows Server ...
    (microsoft.public.windows.server.clustering)
  • Re: How to configure Network Load Balancing using Two Node?
    ... MVP - Windows Server - Clustering ... > 323431 How To Set Up TCP/IP for Network Load Balancing in Windows Server ... > Guide to Creating and Configuring a Server Cluster under Windows Server ...
    (microsoft.public.windows.server.clustering)
  • Re: Print Server CLustering
    ... article ID 258750 to ensure the NICs are setup correctly, ... 258750 Recommended private "Heartbeat" configuration on a cluster server ... 309186 How cluster reserves a disk and brings a disk online ... 818878 Managing Disk Ownership in a Windows Server 2003 Cluster ...
    (microsoft.public.windows.server.clustering)