Forum Discussion

scarpozzi_82104's avatar
scarpozzi_82104
Icon for Nimbostratus rankNimbostratus
Jun 06, 2012

10.2.3 Persistence Profile inconsistencies

I have a web portal deployed that is behind a pair of F5s. There are 3 web servers being load balanced that require persistence because there's no central session broker for the portal system.   ...
config
design
hooleylist's avatar
hooleylist
Icon for Cirrostratus rankCirrostratus
Jun 07, 2012
Make sure you have match across services enabled on the source address profile. And make sure that each virtual server's pool has the same node IP addresses. See SOL5837 for details:

 

 

 

sol5837: Match Across options for session persistence

 

https://support.f5.com/kb/en-us/solutions/public/5000/800/sol5837.html

 

 

The Match Across Services option is used in the following two configurations:

 

 

Configurations that have multiple virtual servers with the same IP address but have different services specified

 

Configurations that have pool members sharing the same address but have different services specified

 

 

 

And ensure that the timeout on the persistence profile is long enough so that the persistence record is preserved for as long as the application session.

 

 

While you're troubleshooting the source address persistence issue, you could try using an iRule to implement cookie based persistence across services:

 

https://devcentral.f5.com/wiki/iRules.Cookie_Encryption_across_pools_and_services.ashx

 

 

Aaron