Forum Discussion
NimbostratusMatch across services for different persistent profiles
I have two VIPs on different ports but share the same IP. VS1:223 has MSRDP persistence and VS2:659 has source address persistence, they both have the same pool members but the port numbers are same as the port their virtual is. The requirement is the client that connects on VS1:22 will then connect on VS2:8550 and the traffic should always go the same node behind both the VIPs. I've read "match-across-services" option which is exactly what the app team wants, but then since VS1 and VS2 have two different persistent profiles, I'm clueless how this can be of any use ? Is there a different solution for this problem ?
https://support.f5.com/csp/article/K5837
DaveS_377638Cirrus
I read the article you linked to.
Under Match Across Services the two configurations are exactly your situation.
Also, "Important: The Match Across Services option uses only the node IP address to find a persistence match in pools other than the one for which the persistence record was written. This deviation from the normal persistence matching behavior is required to accommodate the intended use cases for the feature to match even when the service port does not."
So, even if each VS uses a different persistent profile, the match will only use the node address.
DaveSI read the article you linked to.
Under Match Across Services the two configurations are exactly your situation.
Also, "Important: The Match Across Services option uses only the node IP address to find a persistence match in pools other than the one for which the persistence record was written. This deviation from the normal persistence matching behavior is required to accommodate the intended use cases for the feature to match even when the service port does not."
So, even if each VS uses a different persistent profile, the match will only use the node address.
Red_19I am not sure how this will work Dave, As the persistent record for source IP has the client's ip while the persist records for MSRDP only has RDP_ID, without a common factor how can F5 perform a match across service ?
- John_Huttley
Employee
FYI: Have a little care with using source persistence with any other type. Normally seen as a "fallback". If it engages and you are behind a gateway/proxy/concentrator that presents few source addresses, its likely to "jam on" as traffic continually refreshes its timeout. --John
