Forum Discussion
Dazzla_20011
Nimbostratus
NimbostratusPersistence problem due to client using citrix
Hi,
We have an internal developed application which is load balanced using the F5 device across multiple pool members using different tcp ports. Within one day a user must stick to the same pool...
Dazzla_20011Nimbostratus
NimbostratusHi,
Config is very simple.
pool hmlpphs_bbg {
lb method least conn
action on svcdown reset
monitor all monitor_Jade
members {
10.72.0.34:63201 {}
10.72.0.34:63202 {}
10.72.0.34:63203 {}
10.72.0.34:63204 {}
10.72.0.34:63205 {}
10.72.0.34:63206 {}
10.72.0.34:63207 {}
10.72.0.34:63208 {}
10.72.0.34:63209 {}
10.72.0.34:63210 {}
10.72.0.34:63211 {}
10.72.0.34:63212 {}
10.72.0.34:63213 {}
10.72.0.34:63214 {}
virtual hmlpphs_bbg {
pool hmlpphs_bbg
destination 10.128.153.2:63201
ip protocol tcp
persist src-sticky-internal
monitor monitor_Jade {
defaults from tcp
interval 60
timeout 181
profile persist src-sticky-internal {
defaults from source_addr
mode source addr
timeout 43200
Thanks
