Session mode irule

It sounds like you want to load balance sessions, but persist within each session.

 

 

Load balancing happens according to the algorithm you choose when building the config. Persistence is intended to tie all the connections within the same session to the same backend server. Source IP persistence is not going to create a separate session table entry for multiple sessions from the same source IP, so you'll need to find or create some unique data in each session that will be included in all connection requests. Cookie persistence for HTTP is simple and low overhead. Some applications and protocols set their own session identifier that LTM can persist on.

 

 

You can use an iRule to terminate connections and deny new ones matching a session identifier, but I'm not sure there is a clean way to determine the end of a session unless there is an explicit marker in the data stream. Using a FIN or RST as the trigger won't really work, since a session may consist of multiple connections that open and close naturally during the course of the session.

 

 

Please post a follow up if you'd like to clarify your goals.

 

 

HTH

 

/deb