Forum Discussion
NimbostratusMore than one method of persistence
When selecting more than one persistence method. For instance SSL session ID and in addition source I.P address affinity, how does the LTM track the secondary persistence method. What I am looking for is an explaination of how for instance, once the primary persistance mthod fails, such as the SSL session ID beinge renegotiated, then how does the LTM know to stick that same session by source I.P. ? Given that the LTM no longer recognises that session.
1 Reply
What_Lies_Bene1Cirrostratus
Both Persistence methods create records at the same time. So in your example, the SSL session ID changes so the SSL persistence record can't be used. However, there is a source IP address persistence record that is used based and identified based upon the client IP and destination VS and Service Port.
So, the 'backup' method doesn't recognise the session but recognises the client based on layer3 and 4 information. Note that (OneConnect notwithstanding) the TCP connection within which the SSL session ID changes has already been persisted and that won't change, it's only new connections that will use the backup persistence method.
