ACE Sharepoint Setup/Keep getting IIS Splash Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2012 08:59 AM
I have setup load-balancing on an ACE 4710 for HTTP for Sharepoint 2010. The Server Admin says that the IIS server will recognize the right site by DNS name. Problem is I have no clue how to make sure the servers get the DNS name passed to them. They says this is for a multi-homing setup so that we can run multiple sites using the same VIP to the same Serverfarm. How do I do this? I keep getting the IIS splash page since the real server cannot determine the IIS site that I am supposed to access.
Thanks!
- Labels:
-
Application Networking
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2012 02:01 AM
Hi Dino
I don't know your exact implementation but if you have simple L4 loadbalancing, there nothing you should do on ACE. Webserver must be configured properly. I don't really know IIS, but here is an example for Apache
NameVirtualHost *:80
DocumentRoot /www/example1
ServerName www.example1.com
DocumentRoot /www/example2
ServerName www.example2.org
With this configuration on Apache and this on ACE :
class-map match-any vcd-https
2 match virtual-address 1.1.11.221 tcp eq https
rserver host VH
ip address 1.1.10.183
inservice
serverfarm host VH
rserver VH
inservice
policy-map type loadbalance first-match VH
class class-default
serverfarm VH
policy-map multi-match VH-L4
class VH
loadbalance vip inservice
loadbalance policy VH
(1.1.10.183 - is real IP of Web server and 1.1.11.211 - is VIP and both www.example1.org and www.example2.org are resolved to it)
Everything works perfectly, as ACE doesn't change Hostname field in GET request (by default) and it's web server responsibility to redirect this particular request to proper virtual host.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2012 05:27 AM
Application owner was incorrect on DNS name an caused confusion. This was a non-issue
