Re: NLB IIS OWA by Jose
Jose
Thu Aug 31 09:06:15 CDT 2006
Thanks,
I discovered that the cluster is working properly the second node takes
the load when doing a drainstop. However when I run the httpcfg set
iplisten - i x.x.x.x command to specify the IP's then I can not connect
to OWA by putting the IP on the browser (Host not valid) error. How can
I make IIS listen on this IP's so that I can assign IP's to individual
sites since I need 3 sites on each OWA server to install SSL our
exchange server holds 3 domains.
Woodrow Windischman wrote:
> Hi Jose,
>
> Correct, NLB will happily try to use a non-existant application as long as
> that server is "live" in the farm. You also should make sure that the
> application is fully functional on each node independently before attaching
> to the cluster. Finally, you probably want "session" level affinity for OWA.
>
> NLB doesn't necessarily round-robin sessions, so you might see a number of
> sessions accumulate on one server before the other one kicks in at all, then
> the second will pick up a group of sessions before the first starts again.
> Last time I checked, Microsoft did not publish the algorithms used to
> determine which server picks up any given session.
>
> - Woody -
>
> "Jose" <jose_soto@hotmail.com> wrote in message
> news:1156791782.640956.67780@i42g2000cwa.googlegroups.com...
> > If I stop one of the websites then OWA does not work, I guess NLB is
> > not application aware i mean it doesnt detect if www service is
> > shutdown.
> >
> >
> > Jose wrote:
> > > If I drainstop it shows the other one as converge but user's can't get
> > > to OWA
> > >
> > >
> > > Woodrow Windischman wrote:
> > > > If you drainstop the one that's working, does the second take over? If
> this
> > > > isn't the behavior you want, you may need to adjust your affinity
> > > > settings...
> > > >
> > > > - Woody -
> > > >
> > > > "Jose" <jose_soto@hotmail.com> wrote in message
> > > > news:1156780970.507287.129750@m73g2000cwd.googlegroups.com...
> > > > > Hello,
> > > > >
> > > > > I setup NLB with 2 servers and 2 NICS on each server. The NIC's are
> > > > > configured as follow:
> > > > >
> > > > > Server 1
> > > > >
> > > > >
> > > > > Internal NIC (Heartbeat)
> > > > > IP 10.217.216.15
> > > > > Subnet Mask 255.255.255.0
> > > > > Default Gateway 10.217.216.1
> > > > >
> > > > >
> > > > > Server 2
> > > > > Internal NIC (Heartbeat)
> > > > > IP 10.217.216.16
> > > > > Subnet Mask 255.255.255.0
> > > > > Default Gateway 10.217.216.1
> > > > >
> > > > > NLB IP NIC
> > > > >
> > > > > Server 1
> > > > >
> > > > > Internal NIC (NLB NIC)
> > > > > IP 10.217.216.18
> > > > > Subnet Mask 255.255.255.0
> > > > > Default Gateway 10.217.216.1
> > > > >
> > > > > Server 2
> > > > >
> > > > > Internal NIC (Heartbeat)
> > > > > IP 10.217.216.19
> > > > > Subnet Mask 255.255.255.0
> > > > > Default Gateway 10.217.216.1
> > > > >
> > > > > The NLB IP is 10.217.216.17
> > > > >
> > > > > Now as you can see both NIC's the NLB and the management NICs are on
> > > > > the same subnet and both have default gateways. Now the NLB is
> working
> > > > > but it seems that only one server is holding on the load. Please
> help I
> > > > > dont know if these NICs need to be on different subnets and if they
> > > > > both need default gateways.
> > > > >
> >