Forum Discussion

tm500_165564's avatar
tm500_165564
Icon for Nimbostratus rankNimbostratus
Jun 05, 2015

Help with URI string-based session persistence

Hi all Warning: Newer to F5 but really enjoying the experience so far. Trying to get my hands dirty with iRules. I've been doing a lot of research on the forums and I haven't come across the "gol...
application delivery
devops
iRules
LTM
  • nitass's avatar
    nitass
    Jun 11, 2015

    If this happens the LB just sends the request to the same node that the TCP session is tied to - but the iRule still logs as seeing the new strID value. I was confused and expected this to create a new persistence record and load balance the request, but something tells me I would need more logic in my iRule to detach the connection and re-load balance it with a new persistence record.

     

    you can use oneconnect profile. it will do that for you.

     

tm500_165564's avatar
tm500_165564
Icon for Nimbostratus rankNimbostratus
Jun 08, 2015

The more I think about this the more I think maybe I'm confusing session persistence with the idea of tying a request string to a node.

 

ie.
String ID ABC comes in, load balancer directs to node A
String ID BBC comes in, load balancer directs to node B
String ID ABC comes in again, request is sent to node A
String ID BBC comes in again, request is sent to node B
String ID  comes in, load balancer directs to A or B and so on

 

The more I think about this, it seems more of a String to Node lookup table type solution. The problem here being the string is dynamic and generated for any given request, and follow up requests are essentially polling the status of the original request identified by the String ID. For speed, the hope was to direct these to the same servers so the request is in memory and can be responded to as fast as possible...