Forum Discussion
miodas
Altocumulus
AltocumulusPersistence source addr / cookie, client->vip1->pool1->vip2->2pool
Hello Everyone Scenario: Client is connecting to VIP 1 ( with 2 pool members ) new connection from one of the pool members is set up to vip2-pool2 (with 2 pool members ) in short client->VIP1...
Nikoolayy1
MVP
MVPThe cookie persistence is for VIP2 to select between the members in pool 2 , so it shouldn't care about if the source is the first or second member of pool 1 (the pool for VIP1) and work. Still read this just in case:
miodasAltocumulus
AltocumulusHi
to be exact it looks like that
client -> ( with public IP )->NAT->172.25.241.11vip1 -> (172.25.200.13 , 172.25.200.22) -> 172.25.242.32vip2 -> 172.25.119.18/19/29/30
When i tested it with cookie persistence on VIP2 user was ending up on one of the 4 servers in pool of VIP2
wit each website refresh he was on a different node.
Problem is that VIP 1 has only 2 pool members that are initiating a connection to VIP 2
and with source persistence traffic is not distributed to all 4 pool members from VIP2
Customer wants to have persistence and even distribution between 4 servers from VIP2
The easy way would be to just add 2 additional nodes to VIP1 but is there any other way to make that work with 2 nodes ?