CSS with Advance Balance cookies -timeout issue

Unanswered Question
Feb 10th, 2009

We have a CSS configuration in which the CSS sets a cookie, but it never expires. Can we use the sticky-inact-timeout on the following setup?

I believe the answer is NO, as this is only related to IP stickiness

content offloaded_crw03

vip address 10.1.1.1

add service crmtst231_11000

add service crmtst232_11000

port 80

protocol tcp

url "/*"

add service SuccessNet_redirect

arrowpoint-cookie path "/"

arrowpoint-cookie name CRW03base

advanced-balance arrowpoint-cookie

no persistent

active

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
alan.lund Tue, 02/10/2009 - 11:45

I would like to let the CSS expire the time, so can I just use the following command to allow the CSS to expire the cookie after no activity.

arrowpoint-cookie expiration dd:hh:mm:ss

Syed Iftekhar Ahmed Tue, 02/10/2009 - 12:12

"arrowpoint-cookie expiration dd:hh:mm:ss " command has nothing to do with inactivity. It sets an absolute time when cookie will expire.

Did you see follwoing under "Usage guidelines"

"When you configure the arrowpoint-cookie expiration command and the advanced-balance arrowpoint-cookie command, the CSS CPU may spike and the CSS may experience a degradation in its performance. Configure the arrowpoint-cookie expiration command only when necessary."

Syed Iftekhar Ahmed

alan.lund Tue, 02/10/2009 - 12:53

Yes, saw those commands and did see the possible cause in spike CPU. We have tried most of the cookie expire commands and nothing appears to resolve the issue.

What we are looking for is if there is no activitely for a period of time with arrow-point cookie that the CSS drops the cookie and disconnects the user. Most of the users are not closing their browsers, and the usage of the arrowpoint-cookie browser-expire seemed to cause more issues withth application, than it helped.

jason.espino Wed, 02/18/2009 - 18:29

Hello Alan,

Once the ARPT cookie has been delivered to the clients browser they must delete the cookie or they will continuously be bound to the same server as I'm sure you have found out. The CSS will not delete an ARPT cookie based on inactivity however, you can apply an expiration time to the cookie. As stated by Syed applying an expiration date to the cookie could cause the CPU usage on the CSS to spike, so it would be best to verify the cpu utiliziation before and after enabling.

Command:

sho system-resources

Will show the cpu utilization of the modules on the CSS.

If you wish to use the sticky-inact timeout on the content rule then you would need to change your advanced-balanced method to L3 persistance and discontinue the usage of the session cookie. The sticky-inact will actually remove an entry within the L3 sticky-table based on the inactivity time on the clients session.

Hope this info helps!

alan.lund Thu, 02/19/2009 - 04:45

Thanks, with information is very helpful, as we started to make the changes mentioned.

Again thanks, Alan

Actions

This Discussion