Forum Discussion
AltostratusCookie persistence and source address fallback
You are correct when putting Cookie and Source Persist together. If there is a persist record it will go to that server and cluster all the clients that share the same IP to the same server.
AltostratusAlso, what i could do is to set up persistance options with cmd line, it was not saving settings from gui.
I used this command to check what are the settings :
tmsh show running-config ltm virtual vs_httpsand this command to set it ip like on the screenshots:
tmsh modify ltm virtual vs_https persist replace-all-with { Keycloak_cookies { default yes } keycloak_pers_sourceaddr { default no } }The result now is like this:
persist {
Keycloak_cookies {
default yes
}
keycloak_pers_sourceaddr {
default no
}
}but before it was like this:
persist {
Keycloak_cookies {
default yes
}
}Is this normal behaviour? I understand this is correct? now in GUI it looks like this:
You have added two different persistence profiles to the virtual server, "Keycloak_cookies" and "keycloak_pers_sourceaddr". Since "Keycloak_cookies" is set as the default persistence profile (default yes), then this will always be used. "keycloak_pers_sourceaddr" which is set to "default no" will never be used unless you call it using an iRule. Is this the behaviour that you wanted?
If not, then your intention may have instead been to have cookie persistence as the primary persistence method and source IP persistence as the fallback persistence. This would be configured like so:tmsh modify ltm virtual vs_https persist replace-all-with { Keycloak_cookies { default yes } } fallback-persistence keycloak_pers_sourceaddr- kbks
and this is ok? It looks like only persistance profile is used and fallback not exists:
persist { Keycloak_cookies { default yes } }The output you shared shows that only cookie persistence will be used. You are correct, fallback persistence is not configured.
