Forum Discussion

Jim_Sipkovich_4's avatar
Jim_Sipkovich_4
Icon for Nimbostratus rankNimbostratus
Mar 04, 2011

LTM Cookie Persistence issue

We have an issue where the same session cookies was sent back from the client but the ltm sent the traffic to another node in the pool. When looking at the logs none of the nodes were marked off line which should not matter anyhow as this was already in the connection table. Anybody have experience with this type of issue? Thanks

 

 

Versin BIG-IP 9.4.7 Build 320.1 Final

 

 

Cookie Node

 

BIGipServerp-drh-msft-active=772473354.516.0000

 

BIGipServerp-drh-msft-active=772473354.516.0000

 

BIGipServerp-drh-msft-active=772473354.516.0000

 

BIGipServerp-drh-msft-active=772473354.516.0000

 

BIGipServerp-drh-msft-active=772473354.516.0000

 

BIGipServerp-drh-msft-active=772473354.516.0000
  • So this is the exact same client each time? Are you simply logging requests? I recall seeing someone post a known issue similar to this but admittedly can't recall the problem. Might be worth a support case.
  • Jim: this is fairly common, particularly if you've got proxies involved. Have a look here and see if it applies to your situation.

     

    http://support.f5.com/kb/en-us/solutions/public/7000/900/sol7964.html?sr=13398618

     

     

    HTH,

     

    -Matt
  • Here is another Solution Article that overviews the OneConnect Profile fix action suggestion in solution L4L7 provided:

     

     

    http://support.f5.com/kb/en-us/solutions/public/7000/200/sol7208.html

     

     

    We also found out that this is very common when using services like Akami (like L4L7 pointed out).