Cookie balancing between services

Posted By miketheman on 08/19/2008 8:00 AM

 

 

 

My understanding is that once the user connects to Pool1, the returned header will include a cookie from the LB, detailing the pool:node combo, and when the user submits that cookie back to the LB, the user will then be directed to the same node of the pool, but the cookie will not leave the LB (the application on Node1 never sees the cookie).

 

 

 

That's basically correct (it's a hash of the IP:port combo along with virtual server info), although the cookie is actually passed on to the server as well (it most likely just ignores it).

 

 

 

I guess what I'm trying to figure out is how does this session access function if there is only 1 server in each "Pool" and LTM is not involved (ie no server load balancing).

 

 

 

Nodes A & B are both members of Pool1, Nodes Y & Z are both members of Pool2, so both pools are load balanced. I apologize if the diagram didn't make that clear.

 

 

 

No I understood that, the diagram is fine, I'm just asking how would the application maintain the user session if you only had Node A and Node Y, and Node Y initiated a connection to Node A directly? That is the behavior you're going to have to get LTM to emulate via some iRule logic, I believe. Without knowing the underlying behavior I'm not sure how to go about building that logic though.

 

 

Denny