Action on service down question

There are several states for a Node to be in within a pool:

 

 

Enabled (All traffic allowed)

 

Disabled (Only persistent or active connections allowed)

 

Forced Offline (Only active connections allowed)

 

 

All of these will allow traffic to remain active and die off slowly (non-service impacting).

 

 

Enabled - Normal

 

Disabled - Previous customers with a cookie or active connections will be allowed.

 

Forced Offline - Previous customers with cookies now denied, but active connectionsn allowed.

 

 

There are a ways to really and truely make it unavailable, but the best that I've found is by adding a conditional Health Check for it to FAIL, and be marked as Off-Line / Red / Dead. Then everybody must go somewhere else.

 

 

I'd suggest a custom HTTP Health Check / Health Monitor.

 

 

This is a good post to look at : http://devcentral.f5.com/Default.aspx?tabid=53&aft=13662