Forum Discussion

6 Replies

  • I agree that using universal persistence is the way to go, I would look at using the source port to create the persistence on as it should be unique to each session.

     

  • I would use something similar to this (syntax could be wrong as it's off the top of my head)

     

    when CLIENT_CONNECTED {

     

    persist uie [TCP::remote_port] }

     

    This should take the remote port and use it as the persistence value source, the context may require TCP::local_port but that will require testing

     

    • El-Guapo_29797's avatar
      El-Guapo_29797
      Icon for Nimbostratus rankNimbostratus
      So, just to be sure, I created a new Universal Persistence, enabled "Match accross virtual servers" and also added an iRule which "persist uie "[IP::client_addr]:[TCP::remote_port]". Then on Virtual content, call this persistence. Any comment on if this is right or i am missing something?
  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus
    Matin, I wonder if a Universal Persistence profile might help here see sol7392 Not 100% sure this will help but there may be something in the connection that you can capture to ensure the required stickiness. Sorry i couldn't help more but just thought it would be worth mentioning this. N