Application persistence 'lost'

[cbuzzard]

We setup our pair of CSS11506 units in VRRP redundancy mode about 2.5 years ago. All of services are created individually, one on port 80 and one on port 443. Each of their VIPs are the same, port 80 and 443. It was a requirement for our 443 application that when a service is suspended the users currently on that server through the VIP should not be impacted. They should be able to complete their work until they close the session or reach the content rule's idle timeout. Below is an example of how our services and rules are created. Anyone see an issue with this?

service server01-443

ip address 10.10.10.5

protocol tcp

port 443

redundant-index 5

keepalive type script ap-kal-ssl "10.10.10.5 "

keepalive frequency 15

active

service server01-80

ip address 10.10.10.5

protocol tcp

port 80

string server1

keepalive type script ap-kal-httptag "10.10.10.5 /keepalive.asp <A HREF="javascript:newWin('http://www.oururl.com"')">www.oururl.com"</A>

keepalive frequency 15

active

content www-oururl-443

vip address 10.10.10.30

protocol tcp

port 443

add service server01-443

redundant-index 30

sticky-inact-timeout 30

advanced-balance sticky-srcip

balance weightedrr

active

content www-oururl-80

vip address 10.10.10.30

protocol tcp

port 80

url "/*"

advanced-balance arrowpoint-cookie

arrowpoint-cookie browser-expire

add service server01-80

balance weightedrr

active

Thanks

Chad

[Gilles Dufour]

Chad,

the config looks good.

Regarding the 'shutdown' and keep active connection this is call graceful shutdown.

This is done by configuring a weight of zero.

More info at:

http://www.cisco.com/en/US/products/hw/contnetw/ps792/products_configuration_guide_chapter09186a0080409c84.html#wp1113353

Regards,

Gilles.

[cbuzzard]

Hi Gilles -

So you are saying that there has never been a graceful shutdown of application persistence to a content rule before 7.3 and the graceful shutdown? We use the Cisco HSE to allow help desk personnel to take troubled servers out of service, if we have to go to the weighting method for graceful shutdown that introduces a new issue to us. We do have a few of our content rules as weighted, but those are the exception for a test we did, most are leastconn.

Thanks

Chad

[Gilles Dufour]

the 'weight 0' works with all type of loadbalancing method - leastconn included.

I would like to clarify something.

suspend will actually not impact current connections.

So, you could suspend a service and the currently connected users will be able to keep their connections.

However,most of the time, during an HTTP connection you open and close connections.

With suspend, no new connections are allowed, even for users already connected.

The graceful shutdown allows connections to go to the server if there is a sticky entry matching the client and server.

This is useful to permit a user to finish browsing - not just finish downloading a page.

Gilles.