jan_de_wachter_
Jan 20, 2017Nimbostratus
LTM FastL4 and source-address persistency
We have an application that was difficult to make working as needed.
At last we succeeded by creating a Performance (Layer4) VS with FasL4 profile. They also needed sticky sessions.
ltm virtual /Infrabel/a1183-***-***_vs {
destination /Infrabel/10.252.13.204%113:6039
ip-protocol tcp
mask 255.255.255.255
partition Infrabel
persist {
/Infrabel/a1183-***-***_sticky-mirror {
default yes
}
}
pool /Infrabel/a1183-***-***_pool
profiles {
fastL4 { }
}
source 0.0.0.0%113/0
source-address-translation {
type automap
}
vs-index 160
}
The application guys are happy, everything is fine. BUT we can't find any persistency records.
I thougt that with an FastL4 profile, you couldn't have any special profiles (like coockie persistency, ...) which need HTTP (L7). But destination and / or source address persistency profile was permitted.
Can anyone help me with this "logic" problem - is there source address persistency or not and how can I find this out?
Thanks
Jan