|
|
|
date: Fri, 1 Feb 2008 10:38:01 -0800,
group: microsoft.public.exchange.clustering
back
Re: NLB + CAS \ HT Server IP question.
1. Set up your servers using just 1 NIC. Configure it with each server's IP
address, register those IPs with DNS, configure a DNS Server and a Gateway.
2. Configure the 2nd NIC. The 2nd NIC will ONLY be used for NLB. Each of
these NICs will have an IP address of your production network segment, but
you don't need to register these IPs with DNS, neither you need to configure
DNS Server or Gateway for this 2nd NIC.
3. Each 2nd NIC on each server will share a virtual IP address (the NLB IP
address). This is the IP you must register with DNS.
The concept here is a little bit different from clustering, it's not an
heartbeat, it's a dedicated NIC for NLB.
And please remember that you should only load-balance ports 80 and 443!
--
Rui Silva
MVP Windows Server System - Exchange Server
Blog "subject: exchange", http://msmvps.com/ehlo
"QChang" wrote in message
news:A3DE75C1-BA2B-44C0-88B8-F68BD1341B6E@microsoft.com...
> Hi All,
>
> I am new to the concept of NLB so pardon me for my ignorance.
>
> After reading Henrik Walther's excellent articles on the NLB I would like
> to
> setup NLB with Unicast and dual NICs for the two Exchange 2007 CAS / HT
> servers that we have. However, I am confused about the IP ranges and
> traffic
> flow on the 2 NICs.
>
> Server 1
>
> So on NIC1 ( Public )
> IP :10.0.0.100 ( Server 2 - 10.0.0.101 )
> SM : 255.255.0.0
> GW : 10.0.0.1
>
> NIC 2 ( NLB )
> IP : 192.168.100.100 ( Server 2 - 192.168.100.101 )
> SM : 255.255.0.0
> no GW or DNS
>
> NLB Cluster DNS entry (192.168.100.200 )
>
> From what I have gathered from the articles ( and please correct me if I
> am
> wrong ) I would need to register a DNS entry for the NLB Cluster. I think
> I
> would also need to have the firewall NAT to the NLB Cluster IP but there's
> where I can't get my head around this.
>
> I know traffic is suppose to traverse thru the NLB cluster but does the
> traffic need to go thru a gateway or does it behave more like a Virtual IP
> with heartbeat functions ?
>
> If I only have 2 servers to NLB would it be sufficient to use a crossover
> cable between the 2 servers or am I completely wrong and need to have the
> traffic be routable ( on it's own seperate network with a gateway )
>
>
> Would the correct answer be ...
>
> 1) Firewall ( 10.0.0.1 ) --> Public IP ( 10.0.0.100 ) <> NLB Clu (
> 192.168.100.200 ) ( own segment but no gateway )
>
> or
>
> 2 ) Firewall ( 192.168.100.1 ) -- > NLB Clu ( 192.168.100.200 ) <> Public
> IP
> ( 10.0.0.100 ) ---> Inside Network ---> Firewall ( 10.0.0.1 )
>
>
> I am semi-familiar with clustering so I am afraid I am mixing the 2 ideas
> and confusing myself to death...
>
> Any assistance would be greatly appreciated before I pound my head into
> the
> wall...
>
> Thanks in advance and best regards,
> Q
>
date: Mon, 4 Feb 2008 17:41:08 -0000
author: Rui Silva [MVP] rjms1808(nospam4me)@hotmail.com
Re: NLB + CAS \ HT Server IP question.
Hi Rui,
Thank you for your reply. So just to recap.
I create an DNS entry for the NLB cluster IP ( with a production network IP
10.0.0.110 ).
I would setup the servers with one NIC first ( 10.0.0.100 ) and make sure
the DNS and Gateway is correct.
I would then install the second NIC with an IP from the production
environment ( ie. 10.0.0.105 ) and make sure that it is physically connect
to the production network or ( just to each other on a seperate hub ) ?
I thought I have found the answer before but now after reading many
different answers I am back to square 1 ( confused ) again...
Help please.
Thanks and regards,
Quentin
"Rui Silva [MVP]" wrote:
> 1. Set up your servers using just 1 NIC. Configure it with each server's IP
> address, register those IPs with DNS, configure a DNS Server and a Gateway.
> 2. Configure the 2nd NIC. The 2nd NIC will ONLY be used for NLB. Each of
> these NICs will have an IP address of your production network segment, but
> you don't need to register these IPs with DNS, neither you need to configure
> DNS Server or Gateway for this 2nd NIC.
> 3. Each 2nd NIC on each server will share a virtual IP address (the NLB IP
> address). This is the IP you must register with DNS.
>
> The concept here is a little bit different from clustering, it's not an
> heartbeat, it's a dedicated NIC for NLB.
>
> And please remember that you should only load-balance ports 80 and 443!
>
> --
> Rui Silva
> MVP Windows Server System - Exchange Server
> Blog "subject: exchange", http://msmvps.com/ehlo
>
>
> "QChang" wrote in message
> news:A3DE75C1-BA2B-44C0-88B8-F68BD1341B6E@microsoft.com...
> > Hi All,
> >
> > I am new to the concept of NLB so pardon me for my ignorance.
> >
> > After reading Henrik Walther's excellent articles on the NLB I would like
> > to
> > setup NLB with Unicast and dual NICs for the two Exchange 2007 CAS / HT
> > servers that we have. However, I am confused about the IP ranges and
> > traffic
> > flow on the 2 NICs.
> >
> > Server 1
> >
> > So on NIC1 ( Public )
> > IP :10.0.0.100 ( Server 2 - 10.0.0.101 )
> > SM : 255.255.0.0
> > GW : 10.0.0.1
> >
> > NIC 2 ( NLB )
> > IP : 192.168.100.100 ( Server 2 - 192.168.100.101 )
> > SM : 255.255.0.0
> > no GW or DNS
> >
> > NLB Cluster DNS entry (192.168.100.200 )
> >
> > From what I have gathered from the articles ( and please correct me if I
> > am
> > wrong ) I would need to register a DNS entry for the NLB Cluster. I think
> > I
> > would also need to have the firewall NAT to the NLB Cluster IP but there's
> > where I can't get my head around this.
> >
> > I know traffic is suppose to traverse thru the NLB cluster but does the
> > traffic need to go thru a gateway or does it behave more like a Virtual IP
> > with heartbeat functions ?
> >
> > If I only have 2 servers to NLB would it be sufficient to use a crossover
> > cable between the 2 servers or am I completely wrong and need to have the
> > traffic be routable ( on it's own seperate network with a gateway )
> >
> >
> > Would the correct answer be ...
> >
> > 1) Firewall ( 10.0.0.1 ) --> Public IP ( 10.0.0.100 ) <> NLB Clu (
> > 192.168.100.200 ) ( own segment but no gateway )
> >
> > or
> >
> > 2 ) Firewall ( 192.168.100.1 ) -- > NLB Clu ( 192.168.100.200 ) <> Public
> > IP
> > ( 10.0.0.100 ) ---> Inside Network ---> Firewall ( 10.0.0.1 )
> >
> >
> > I am semi-familiar with clustering so I am afraid I am mixing the 2 ideas
> > and confusing myself to death...
> >
> > Any assistance would be greatly appreciated before I pound my head into
> > the
> > wall...
> >
> > Thanks in advance and best regards,
> > Q
> >
date: Mon, 4 Feb 2008 15:04:00 -0800
author: QChang
|
|
