Forum Discussion
Iain_McGuire_11
Aug 02, 2006Nimbostratus
Guys,
Thanks for the thoughts, much appreciated. I've been giving this a little more thought - If the virtual webservers are configured to run on a separate port, rather than being differentiated based on host headers, this would be much more feasible, wouldn't it? I could presumably create several pools, each with two members, one for each serverIP:port combination. Then, if one of the virtual webservers is stopped in IIS, it would only be that member server:port combination that's marked as down?
eg, two physical webservers, at 10.0.0.1 and 10.0.0.2 host cat.com, dog.com, rat.com and donkey.com, with
cat.com = port 8081
dog.com = port 8082
rat.com = port 8083
donkey.com = port 8084
So if cat.com is stopped in IIS on one physical server, the others are all still marked as up? And we have one virtual server listening on the routable address, using iRules to select a pool based on the domain name.
That would be much more workable than trying to run all websites locally on port 80, right?
Thanks again.