CSM cookie timeout/clearing

Unanswered Question
Sep 27th, 2010


We have this solution now in our production-enviroment.

sticky 20 cookie JSESSIONID timeout 30
vserver MOBI
  virtual tcp www
  vlan 10
  serverfarm MOBI
  sticky 30 group 20
  replicate csrp sticky
  persistent rebalance

And it seems to work fine except in one situation:
When one of the real-servers goes down it seems as if a cookie created for a session to that server (and not timed out) prevents the session to be lb to the other realserver.
Is there a way to make the CSM clear cookies related to a realserver that goes down?

SW-version 4.2(13)



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
jsirstin Mon, 09/27/2010 - 07:21


Are you using probes to detect the real server’s health? If so when the server goes down do you see the real server in a probe_failed state when you issue the command "show mod csm X serverfarm name MOBI detail"? X is the slot number the CSM is located in. It sounds like the CSM may not be seeing this server as down. If a new connection comes in with an existing cookie from a server that is marked as "probe_failed" it will be sent to one of the other operational real servers in the serverfarm. The CSM should only try to send this connection to the server that issued the cookie if it is operational.




This Discussion

Related Content