For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

i-tech_182772's avatar
i-tech_182772
Icon for Nimbostratus rankNimbostratus
Oct 05, 2018

Persistence match across service

Hi Guys,

 

I am new and i need help on understanding how match-across-service works. Been reading the K5837, but is still kinda confused.

 

  1. For matching across-service to work ? Does both VS above need to have the same persistence method configured ? or it doesn't matter

     

  2. How does F5 decides when a incoming request can "match-across" and re-use an existing PR mapping ? if the original/1st request persistence record is created from cookie-hash, what does F5 check to see if a new subsequent request can match-across and reuse an existing mapping ? Does it still check if there is any cookie; if the cookie-hash value match; or just by plain client-source-ip + VS-IP ?

     

Thank you

 

application delivery
BIG-IP
cookie persistence
devops

1 Reply

  • Kevin_Stewart's avatar
    Kevin_Stewart
    Icon for Employee rankEmployee
    Oct 05, 2018

    1. In a match-across-services scenario, you'd typically have two VIPs with the same IP listening on different services (ex. HTTP/HTTPS), and yes, both of these VIPs would need to have the same persistence settings.

       

    2. An origin persistence record will maintain full details of the connection (pool, node, port). When a user arrives at another service VIP and has not origin persistence with that VIP, but does have match-across-service persistence information, it will only use the node IP to find the match.