dever
2004-12-16 03:40:11 UTC
Hi there,
I'm having an issue with my load balanced SPS configuration. I'm using Cisco
LocalDirectors to handle the load balancing.
Here's my setup:
I have two virtual servers (one hosts applications and web services, one
hosts a portal, we'll call them VirtualServers 1 & 2). Both of these are
bound to two "real" (physical) servers (RealServer 1 & 2) on ports 80 and
443. ICMP is disabled on the local director and the servers each have one
NIC, which is configured with standard settings from DHCP. No special DNS or
gateway or anything.
Basically, the portals work (mostly) fine from a workstation. But when I go
into the console on any one of the real servers and try to browse or telnet
on port 80 to the virtual server, about 60% of the time it acts as if the
server can't be found.
Using nslookup, I can tell it's resolving to the correct IP address for the
virtual server. Again, from a workstation, this same operation works fine
consistently. I said mostly fine above because when you declare a datasource
for a web part in Sharepoint, the request for the data is generated from the
server. This obviates the problem since it causes the same scenario -- a
real server requesting data from a virtual server. This errors out, and
therefore is a bigger problem.
My hunch is that this has something to do with masquerading or reverse
masquerading. RealSvr1 makes a request to VirtualServer1, the localdirector
routes the request back to RealSvr1 or RealSvr2, and the RealSvr(1/2)
responds directly to the source requestor, RealSvr1, without going back
through the localdirector. So the response doesn't look like it's coming
from VirtualServer1 anymore. That's my best guess at this point anyway.
Has anyone seen this behavior before? Does anyone know a remedy to get this
working properly?
Thanks very much for your time,
Esteban
I'm having an issue with my load balanced SPS configuration. I'm using Cisco
LocalDirectors to handle the load balancing.
Here's my setup:
I have two virtual servers (one hosts applications and web services, one
hosts a portal, we'll call them VirtualServers 1 & 2). Both of these are
bound to two "real" (physical) servers (RealServer 1 & 2) on ports 80 and
443. ICMP is disabled on the local director and the servers each have one
NIC, which is configured with standard settings from DHCP. No special DNS or
gateway or anything.
Basically, the portals work (mostly) fine from a workstation. But when I go
into the console on any one of the real servers and try to browse or telnet
on port 80 to the virtual server, about 60% of the time it acts as if the
server can't be found.
Using nslookup, I can tell it's resolving to the correct IP address for the
virtual server. Again, from a workstation, this same operation works fine
consistently. I said mostly fine above because when you declare a datasource
for a web part in Sharepoint, the request for the data is generated from the
server. This obviates the problem since it causes the same scenario -- a
real server requesting data from a virtual server. This errors out, and
therefore is a bigger problem.
My hunch is that this has something to do with masquerading or reverse
masquerading. RealSvr1 makes a request to VirtualServer1, the localdirector
routes the request back to RealSvr1 or RealSvr2, and the RealSvr(1/2)
responds directly to the source requestor, RealSvr1, without going back
through the localdirector. So the response doesn't look like it's coming
from VirtualServer1 anymore. That's my best guess at this point anyway.
Has anyone seen this behavior before? Does anyone know a remedy to get this
working properly?
Thanks very much for your time,
Esteban