Forum Discussion
Persistence issue with TCP
- Dec 29, 2017
Ok, I finally fix it ^^
The issue was because I created a pool with 4 members, 2 same IP but different service port, cause we have 2 versions who using different socket
And I have 2 Virtual Services different (based on version) with an iRule different for each in order to select specific node with the target port. The irule was like this :
when CLIENT_ACCEPTED { set xxx_node1 "13.x.x.183" set xxx_node2 "40.x.x.221" set xxx_ppol "pool_vm_xxx_prod" set xxx_port yyyy if { ([LB::status pool $xxx_ppol member $xxx_node1 $xxx_port] eq "up") and ([LB::status pool $xxx_ppol member $xxx_node2 $xxx_port] eq "up") } { node $xxx_node1 $xxx_port node $xxx_node2 $xxx_port } elseif { ([LB::status pool $xxx_ppol member $xxx_node1 $xxx_port] eq "up") and ([LB::status pool $xxx_ppol member $xxx_node2 $xxx_port] eq "down") } { node $xxx_node1 $xxx_port } elseif { ([LB::status pool $xxx_ppol member $xxx_node1 $xxx_port] eq "down") and ([LB::status pool $xxx_ppol member $xxx_node2 $xxx_port] eq "up") } { node $xxx_node2 $xxx_port } else { log "Error : Pool $xxx_ppol is down" }
}
Finally, I just recreate 2 new pool specific to each version and on my 2 VS I associate this new pool based on target version and deleted the associated iRule.
And now, my traffic is correctly load balanced 😉
Thanks to all who help me in this situation
Have a nice day, Regards Alex
Hi
Thank you for your response. The protocol used is a no-known, developed by a company (based on tcp socket). So I’m not sur how to reply you about l7 on this traffic.
But if I understand what you mean, I don’t have to use a VS with a standard type, correct ?
Ok, I begin t understand better with theses explanations. And It could be useful to try chech information in TCP Payload, very useful. Thanks, and I will use it but not sure for this special case.
In fact, here we don't need to get this information about something, no need to keep persistence or affinity. It's for IOT project where devices connect to farm server and etablished a socket (and keep it open). If IOT become disconnected, he can reconnect to any node without reconnect previous one.
So, which settings I need to set for load balance tcp connection without any affinity, persistence, etc.. Just want redirect traffic to each nodes based on TCP connection. For example, we have 10k device connected for 3 node farm, 3333 TCP connection need to be redirect to each node.
I'm totally agree that like it's TCP socket, if a node fail then revert, all TCP socket will remain connected in other nodes in farm and only next TCP will be load balanced. We already have a plan for kill TCP socket on server UP after a node failed for equalize again.
Thank you again, Alex
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com