Cookie Persistence and oneconnect profile question

Hi,

Suppose you have one VS and 2 pool.

• pool A (node A1, node A2)
• pool B (node A1, node A2)

you set an irule:

• if uri starts_with "/a/" forward to pool A
• if uri strats_with "7b/" forward to pool B

Use case

• now suppose that your first uri is: https://mydomain.com/a/local.jsp
• you will be FW to pool A and the LB decision send you to nodeA1
• then you click try to access to https://mydomain.com/b/local.jsp
• Without OneConnect enabled, the default LTM behaviour is to persist to the first server selected for the life of the connection. so instead FW your request to Pool B (nodeB1) the request stay in Pool A (nodeA1).

Keep in mind that one connect is usefull when you have several pool in the same VS and you use irule to route user request on theses pool. It will allow you to detach each connection on Server side to FW you in the right pool/node.

You have an explanation here:

https://devcentral.f5.com/articles/oneconnect-for-my-irule

Last point, if you want to avoid using oneconnect. you can built your policy using "LTM Policy" the LTM Policy manage by request so each request is processed and oneconnec is not usefull in this use case.

Hope it's clear.

Keep me update. regards