Session state on CSS11051

jimb — Wed, 07 Apr 2004 19:44:40 GMT

I am load balancing using advanced-balance cookies. Most of the time it works, but we see sporadic failures in the session state which is hard on our customers who need to remain "stuck" to the same session. The only thing I can get from logging is this message:

JAN 1 00:00:02 5/1 303939 IPV4-7: Ipv4SfmForwRx: drop ICMP type 5 code 0 to VIP xx.xx.xx.xx

Anyone know what might be wrong?

Re: Session state on CSS11051

Gilles Dufour — Thu, 08 Apr 2004 08:53:53 GMT

if your customer is going through a proxy and the proxy connection with the CSS stays idle for 8 seconds, the flow will be marked for garbage collection and once garbage collected the flow is still being used but we can't modify it anymore.

So you stay stuck to the last server.

One way to reduce this problem is to increase the flow timeout.

With CSS first gen you can use the command flow port#1 80 timeout 600 or if you have a 2nd gen CSS you have to use the command 'flow-timeout-multiplier 50'

The message you showed is unrelated.

The only way to see the problem is to capture sniffer traces.

Gilles.

topic Session state on CSS11051 in Application Networking

Session state on CSS11051

Re: Session state on CSS11051