URL health check content problem with alteon 180e

[startekker]

Hi all,

Am trying to configure SLB on a 180e with OS v 10.0.33.0

We've set the the URL health checking to an ASP page and it appears to be working except that if the default.asp page stops responding (ie. in testing we just rename the file on the IIS server so that it no longer exists) it doesn't mark the server as bad in the monitoring even though the alteon actually appears to stop sending anything to that server? Shouldn't the alteon actually mark the server as 'bad'?

Thanks!

 

[JeroeNortel]

Hi startrekker,

Snce the Alteon stop sending traffic to the 'offline url' (you checked this with sniffer?) I assmume he somehow recognizes it doesn't excist anymore. Is there is another health checking active on this server/application? I agree the Alteon should 'fail' the failed health check (url in your case) but if you have more health checking going on he only gives the inaccesible url bad but it can still have a succesfull health check on this server on, for example port 80. This is configuration dependant, maybe you can tell this.

Can you check this health checks on this group?

Regards,
JeroeNortel

 

[startekker]

Hi Jeroe,

Thanks for the reply...

You asked:
"Snce the Alteon stop sending traffic to the 'offline url' (you checked this with sniffer?)"

Well the URL I specified to check in the SLB config was: default1.asp... When I rename that file to default2.asp on the webserver so that it no longer exists, then the Alteon no longer sends client requests to that web-server in the group. I tested it by checking the logs on that web-server and see that it is no longer being hit and the external Virtual IP is still responding correctly to testing. Does that answer your question better?

"I assmume he somehow recognizes it doesn't excist anymore. Is there is another health checking active on this server/application?"

Well it is set to http health checking for the group?

"I agree the Alteon should 'fail' the failed health check (url in your case) but if you have more health checking going on he only gives the inaccesible url bad but it can still have a succesfull health check on this server on, for example port 80. This is configuration dependant, maybe you can tell this"

Ok I understand what you are getting at, but I'm not sure how to check this... The strange part is that it doesn't seem to include it in the group but does not mark it as bad... I will check what I can on your suggestion though.
Thanks.

 

[JeroeNortel]

Hi startrekker,

It's clear for me if the web server doesn't get any more hits the url isn't working anymore so the Alteon should give this one 'failed'. Since you noticed the alteon isn't sending anymore traffic to the server means the Alteon do recognize the url is not there anymore, only why it doesn't say the url is failed is a strange thing.
Functionally it's working fine cause the Alteon see the failed url and stops sending so this should be no problem. Only for managment/overview this is confusing seeing the url active but this could be otherwise...
Have you perhaps checked if this could be a bug in this release? I'm not familiar with 10.0.33.0 but if you could check this to be sure.
Also could you try to disable the url health check manually and see what happens. If the url still stays online there is defenately a bug in this release. Else it is related to a external change (health check failure), could still be a bug though.
Try also another port (use 80) to check what happens with health checking on this port.

Regards,
Jeroen