[prev in list] [next in list] [prev in thread] [next in thread] 

List:       loadbalancing-l
Subject:    RE: [load balancing] ServerIronXL - Real servers failing L4 check for no apparent reason
From:       "Katia Augugliaro" <katia.augugliaro () teicos ! it>
Date:       2004-07-16 12:13:35
Message-ID: 000101c46b2e$52b29740$5b64a8c0 () teicosnet ! spc
[Download RAW message or body]

Yo Basil

Do u use the command
server no-fast-bringup
?

It assures that the port becomes active ONLY when all the health Checks are
ok.
Ping, l4 and l7.
In the other way the server put active the port only after the L4 check and
then, after the L7 check is down put the port in the FAIL state and then
redo the check as u configured it (for default 10 2 if I remember
correctly).

Hope this helps :)
Best regards
	Katia

-----Original Message-----
From: owner-lb-l@vegan.net [mailto:owner-lb-l@vegan.net]On Behalf Of
Basil Hussain
Sent: Friday, July 16, 2004 10:45 AM
To: lb-l@vegan.net
Subject: RE: [load balancing] ServerIronXL - Real servers failing L4
check for no apparent reason


Hi,

Thanks for the reply.

I've solved it! They were indeed failing the L7 health check. The web page
it was checking (the default of '/') on those real servers was actually
performing an HTTP 302 re-direct. I find it strange that the SI by default
doesn't consider this a successful HTTP response (only 200-299 and 401
codes).

Anyway, I just needed to add a "port http status_code 200 299 300 302"
command to each of the affected real server's configs.

I still don't understand why, after failing the health check, it would then
come back up about 5 seconds later! Because of this, the real server status
was always showing as 'active', which is what confused me. I also don't
understand why it wasn't logged that it was the L7 check that failed, rather
than mentioning "L4" in the message.

Cheers,

--
Basil Hussain
I.T. Systems Developer and Administrator, Kodak Weddings
basil.hussain@kodakweddings.com


> -----Original Message-----
> From: owner-lb-l@vegan.net [mailto:owner-lb-l@vegan.net]On Behalf Of
> Frank Yue
> Sent: 15 July 2004 18:42
> To: lb-l@vegan.net
> Subject: RE: [load balancing] ServerIronXL - Real servers failing L4
> check for no apparent reason
>
>
> It sounds like the server is passing the L4 healthcheck, but
> failing the L7
> healthcheck.  You can do several things.  First, is to use the
> 'show server
> real http [name]' to look at the specific state of the healthchecks.
> Second, is to turn on the command 'server no-fast-bringup' at the global
> level.  This will change the Foundry methodology for bringing a server up.
> The server will only be brought up if the server passes the L4
> check AND the
> L7 check when this command is enabled.
>
> You should verify that the HTTP check that you are doing is returning a
> valid status code (200-299).  Otherwise, the site will be marked as down.
>
> -Frank Yue
> Consulting Engineer, Layer 4-7
> 1004 W. Mandevilla Court
> Wilmington, NC 28409
> fyue@foundrynet.com
> www.foundrynet.com

____________________
The Load Balancing Mailing List
Unsubscribe:    mailto:majordomo@vegan.net?body=unsubscribe%20lb-l
Archive:        http://vegan.net/lb/archive
LBDigest:       http://lbdigest.com
MRTG with SLB:  http://vegan.net/MRTG
Hosted by:	http://www.tokkisystems.com


____________________
The Load Balancing Mailing List
Unsubscribe:    mailto:majordomo@vegan.net?body=unsubscribe%20lb-l
Archive:        http://vegan.net/lb/archive
LBDigest:       http://lbdigest.com
MRTG with SLB:  http://vegan.net/MRTG
Hosted by:	http://www.tokkisystems.com

[prev in list] [next in list] [prev in thread] [next in thread]