Mike, and anyone else who is interested... It does appear that the serveriron is doing the trick. i.e. the local real servers are filled to max-conn, then subsequent connections are sent to the server remote-name.
Quite impressed with it really as a Big/IP stalwart that is. My only problem now appears to be tweaking HTTP Keep-Alives to timeout in such a way that once you get a succesful connection to the main site, you keep it, and aren't presented with the too busy pages from the remote server halfway through your transaction. Should be fun eh ? Regards Andy ----- Original Message ----- From: "Mike Allen" <[EMAIL PROTECTED]> To: "Andy Fry" <[EMAIL PROTECTED]> Cc: <[email protected]> Sent: Wednesday, November 03, 2004 3:26 PM Subject: Re: [f-nsp] Fw: Local and Remote Real Servers > Andy, I am pretty sure the remote servers will only be used if the > reals are unavailable (failed healthcheck). I don't thnk max > connections would force that switch. > > > On Mon, 1 Nov 2004 11:33:18 -0000, Andy Fry <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> I wonder if anybody knows what situations would cause the remote servers >> in >> a pool to be used ? >> >> For example if we had one virtual server containing 4 local real servers >> and >> 1 remote real server, would connections be directed to the remote server >> only when the 4 real servers stopped responding to http requests, or >> would >> connections be directed there when the max connections were reached on >> the >> local servers ? >> >> Any help would be appreciated. >> >> Regards >> >> Andy >> _______________________________________________ >> foundry-nsp mailing list >> [email protected] >> http://puck.nether.net/mailman/listinfo/foundry-nsp >> >> >> > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp
