CSS to CSM migration and http health checking

sasaadamovic · ‎03-04-2009

Hi All,

I hope someone can help me here.

We are migrating number of web services to new DC and I have some issue migrating load balancing from CSS 11501 to CSM module in 6509 within new environment.

Here is config from CSS:

content WS1

vip address 192.168.1.125

add service 192.168.1.105-80-web1

add service 192.168.1.115-80-web2

port 80

protocol tcp

balance leastconn

active

service 192.168.1.105-80-web1

ip address 192.168.1.105

keepalive port 80

keepalive uri "/URIDirect_Default.aspx"

keepalive method get

keepalive type http

keepalive hash "44baffe2618ba829a6b14ad9bccfdcf4"

active

service 192.168.1.115-80-web2

ip address 192.168.1.115

keepalive port 80

keepalive uri "/URIDirect_Default.aspx"

keepalive method get

keepalive type http

keepalive hash "f41469e68c42273622774ec706e3ddcf"

active

With this config CSS uses URI health check to determine whether or not the app live on the nodes of the farm (CSS checks for certain file's existing in app's home folder by checking the hash value of the file name - I beleive so). This is also handy for windows team which remove/rename checked file on server when want to remove it from web farm.

However, reading manuals for CSM I can not see http health probe checking for hash, but only for return status.

Can someone help me with how can I replicate above configuration using CSM.

Regards,

Sasa

Gilles Dufour · ‎03-04-2009

Sasa,

the hash corresponds to a hash of all the text contained in the html page.

This is to guarantee that the page was not modified.

This is some kind of security in case a hacker would alter your pages.

The CSM does not have this feature.

But honestly, you usually get more troubles with this option than benefits.

If the Apps team wants to have the server down while changing files, they can I guess turn off the server themselves before doing changes. And then re-enable after.

Gilles.