Cookie Rewrite & ASPSESSIONID

If you are using cookie insert persistence, the client request should be load balanced to the same node irrespective of what cookie the node might set. There might be application level errors but these shouldn't affect the LTM's reading of the persistence cookie or selecting the node specified in the cookie.

 

 

When a failure occurs, does the ASPSESSIONID cookie name that the node sets in the response change from what the client presented in that request? Or does the name stay the same as what the client presented in the request, but the value change?

 

 

If the name changes, I'm thinking the issue is that persistence is failing for some reason and as a result, the LTM sends the request to a new IIS server. As the ASPSESSIONID cookie the client presents in the request isn't valid for the new IIS server, the IIS server sets a new ASPSESSIONID cookie with its specific ASPSESSIONID cookie name.

 

 

When you see a failure, is the selected node different than the one selected in past requests?

 

 

If anyone else has ideas, feel free to jump in.

 

 

Aaron