CSM Sticky is not working

Unanswered Question
Mar 25th, 2009

My current sticky command is as follows

sticky 10 netmask 255.255.255.255 address source

and virtual:

vserver TEST

virtual 10.10.2.2 any

serverfarm TESTSERV

sticky 1440 group 10

persistent rebalance

inservice

It is not working in that once a client connects they need to stay with the same real server throughout their entire session, but they get rerouted when they open another browser window to run reports, etc. What am I missing?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Gilles Dufour Wed, 03/25/2009 - 16:29

it should work.

Are you sure your traffic hits the same vserver ?

do a 'show mod csm x sticky'.

Is there any entry ?

Can we see a 'sho mod csm x vserver' and a 'sho mod csm x vserver name TEST detail'

What version do you run ?

Gilles.

thornick Thu, 03/26/2009 - 04:51

Yes I am sure they hit the same vserver, I have checked all the show mod csm x sticky, commands, configuration, etc. It is a problem with the real that they do not stick to in the middle of running the application, they go to run reports, and that is when some of the time they switch to another real server. I am running 4.3.2 just upgraded to see if that would make a difference, but no.

Gilles Dufour Thu, 03/26/2009 - 05:53

You will need to capture sniffer traces of the CSM portchannel.

We need to see the connection that fails and the previous connection - so we can see it was sent to a different real.

We need to see client side and server side.

Get all the show commands I requested before - sticky, vserver and vserver detail before and after the problem.

Send us everything or open a service request and give the TAC the info mentioned above.

G.

thornick Thu, 03/26/2009 - 06:13

That is one of my problems, we do not have a sniffer to do a trace, can you recommend any other method to get the trace?

Attached are the show commands.

Actions

This Discussion