Hardware Load Balancing?

Mar 16, 2009 at 5:22 PM
Anyone have any ideas how this could work with hardware load balancing? We have 4x Web Front End servers and our current "warm-up" scripts only seem to hit one of them!
Mar 16, 2009 at 10:32 PM
Configure the warm up script to run directly on each WFE server with the sites.conf listing a URL of the respective server's back-end url (not your load-balanced url).


NLB url: intranet.yourcompany.com
WFE server1: server1.yourcompany.com
WFE server2: server2.yourcompany.com

sites.conf on WFE server1:

sites.conf on WFE server2:

I think that if you substitute the appropriate URLs, it may work.

May 8, 2009 at 5:59 PM

This approach doesn't work if you're using aliases (i.e. host headers) on each of your WFE's. Both of our WFE's have a SharePoint app on them that share the same host header and URL. Other "warm up" scripts I've seen simply call the URL which hits the NLB and then goes to one of the WFE's. This leaves the other WFE still sleeping.

May 11, 2009 at 1:41 PM

This is a problem I'd meant to revisit, but haven't had a chance to look at.  I've been swamped with other work since the beginning of the year, so have been neglecting my little tool.  If anyone knows of a way to get around an NLB to force specific WFEs to respond, I'd appreciate any pointers.

May 27, 2009 at 1:52 AM

One simple way is to use pjacob's suggestion. However, for each of the WFEs, configure the HOSTS file such that the host header points to the IP address of each the WFE that it is hosted on, rather than the NLB virtual IP address.