• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 620
  • Last Modified:

Load Balancer best practice for CAS internalurl

I'd like to know what the community thinks is the best practice when you have multiple CAS servers behind a load balancer in an internet facing site.  Should the internalurl of the cas point to the servername or the private name of the internal VIP?  Microsoft says you should use the server name.  I have also seen posts and blogs contradict this and use the internal vip for the internalurl.

example:  

https://servername.internaldomainname/ews/exchange.asmx 

or

https://vip.domainname/ews/exchange.asmx (vip contains multiple CAS servers)


Any thoughts and comments are appreciated.
0
mkllpit
Asked:
mkllpit
  • 5
  • 3
1 Solution
 
Md. MojahidCommented:
Load balancing recommendation.
1.Hardware Load Balancing
2.Integrated "is alive" monitoring recommended
3.Fixing of MAPI and direcotry endpoint ports
4.Create cAS Array and load-balace selected or all CAS in a site
5.Clinet IP affinity or cookie-based authentication where appropriate
NOt Recommended

1.DNS Round Robin
2.Windows Network Load Balacing
3.Do not load-balance cross-site,create two arrays instead and load-balance separately


Why Not Windows NLB?

Issues with WNLB

Switch/Port flooding in Unicast mode
NAT/Source IP pool
Scalbitlty over 8 nodes
Service awareness
Not support with Windows Failover Clustering
Add/remove single node causes all clients to reconnect
0
 
mkllpitAuthor Commented:
Appreciate the response.  But that wasn't the question I was asking.
0
 
Simon Butler (Sembee)ConsultantCommented:
Personally I use the same host name inside and outside for Exchange, and then have it resolve to the load balancer internally. That way I get a consistent result everywhere.

If I have a problem, or want to do troubleshooting, then hosts files on the test machine do the job. I also usually put a host file on every Exchange server so that the relevant URLs resolve back to itself, again that helps with working in ECP.

I don't use the server name anywhere.

However it does depend where the load balancer is.
If you are doing a NAT to the load balancer, so it is inside, then the above works very well and I would consider that best practise.
If the load balancer is outside (so ONLY has an external IP address) then I don't want traffic going out to come back in, so it would be routed directly to the servers. However I wouldn't deploy a load balancer like that, as the bulk of the traffic (and reason for having them is internal traffic).

I am a JetNexus certified installer btw.

Simon.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
mkllpitAuthor Commented:
Thanks Simon!  When I added an entry on the local host file for the server itself and I ping the server locally it resolves to the IPv6 address.  Is that normal?

Another followup.  We had someone recommend using http instead of https: for the internalurl since its internal communication only.  I don't know if I am comfortable with that philosophy.  Anyone else out there use http instead of https and why would you?  This person said it would save us on the amount of SAN names on our cert as we have the servernames in the cert.

Ex  http://servername.internaldomainname/ews/exchange.asmx
0
 
Simon Butler (Sembee)ConsultantCommented:
The server name itself coming back as IPv6 is normal. However you wouldn't normally put the server's own name through the load balancer, but the common name.

Therefore it is the common name that you want to resolve to the server itself.

As for the argument about SANs - from November 2015 (And any certificates that expire after that date) you cannot put internal domain names on to the certificate. I don't use the server's real name anywhere in the deployment - it is all the common name, therefore I can use HTTPS everywhere.

Simon.
0
 
mkllpitAuthor Commented:
Simon,

So in the hosts file I would put the IP of the server and resolve it to the common name?  or the IP of the VIP and resolve to the server?  Just want to make sure I have this right
0
 
Simon Butler (Sembee)ConsultantCommented:
You want the common name to resolve to the server.
The idea being that you are not using the load balancer at all to run things on the server (like ECP etc).

Simon.
0
 
mkllpitAuthor Commented:
Great.  Thanks again Simon!
0
 
mkllpitAuthor Commented:
As always... Simon is one of the best resources for Exchange questions!  Glad he is available to answer these types of scenarios!
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now