matchclass, uri routing, and cookie persist & snat irule

Okay, so in thinking about this, it seems that the JSESSIONID check in the outbound HTTP_RESPONSE are required so that the F5 knows to put an entry into its session table, indicating the outbound JSESSIONID as a persistence entry, thus ensuring that when it comes back in future HTTP GET requests from the client, the LTM knows to which pool member the request(s) should be sent.

 

 

That said, please lend a hand with my other questions is possible:

 

 

1. If the SESSIONID cookies referenced in the iRule exist we should be good, but if they don't (like on an initial visit to the site) will the LTM iRule err out and stop processing or just ignore the persist command?

 

 

2. Is my catch all properly structured, so that when any request comes in which does not match one of the aforementioned URIs, the LTM will try to persist it using the cookie name of UMPSESSIONID, and then send it to the appropriate pool, whether as a sticky session or a new session.?

 

 

3. Regarding OneConnect for the L7 persistence (JSESSIONID), as mentioned in the article above, we've been using that persistence iRule for some time now and don't have OneConnect enabled for our other VS's. Could this be causing odd connection issues, and should I look at enabling it for this new iRule too? Can you please explain why? I'm not entirely sure I understand the explanation given in the other link.

 

 

Thanks!

 

Brian