Forum Discussion
Sumanta_88744
Cirrus
CirrusPersistence profile - How will I use source address affinity based load balancing?
Hi Experts
How will I use source address affinity based persistence profile across different pools having different IP but same port? For example there are two virtual server 1.1.1.1:80 and 2.2.2.2...
Don't worry, it's a common scenario for me.
Just pay attention that the upstream proxy insert the "X-Forwarded-For" header, or maybe another one "True-Client-IP" or even "X-Client-IP".
If you are just nating using a firewall, I think that the header is not inserted.
I add this peace of code in the example :
set clientip [IP::client_addr]because you may have situation where there is no "X-Forwarded-For" in the request, so that we can persist also in this scenario.
Yann_DesmarestCirrus
CirrusDon't worry, it's a common scenario for me.
Just pay attention that the upstream proxy insert the "X-Forwarded-For" header, or maybe another one "True-Client-IP" or even "X-Client-IP".
If you are just nating using a firewall, I think that the header is not inserted.
I add this peace of code in the example :
set clientip [IP::client_addr]
because you may have situation where there is no "X-Forwarded-For" in the request, so that we can persist also in this scenario.
Sumanta_88744Cirrus
CirrusHi All
This is giving error while trying to change source based persistence to universal.
01070394:3: HTTP_REQUEST event in rule (/Common/iRule_xff) requires an associated HTTP or FASTHTTP profile on the virtual server (/Common/AFG_XCAP_VS).