Forum Discussion
NimbostratusRound Robin or Least connections not working as expected LTM 10.2.4 Long lived connections
Hi F5 geeks, I have a scenario
VIRTUAL-LISTENING-ON-50101 (has Fastl4 enabled) SNAT2VIP {irule just snat} POOL-SERVERS-JAVA-SERVERS--- SERVER-A:50102 SERVER-A:50104 SERVER-B:50101 SERVER-B:50103
Requirements::
(i)VIP listens on 50101 (ii) at pool level we have ports defined as shown above {iii) equal distribution to each member:port combination for every connection that comes in (iv) since connections are long lived unless the server is bounced the connection remains active unless bounced and as data exchange is heavy equal distribution is vital
Failed implementations::
a) at pool level configured Round robin and Least connections method which fails only one server is used and no equal distribution occurring. Also no persistence enabled at any stage.
Question:: Is there a way to achieve equal distribution of the connections to the member:port combination, as in monitor which is available and send the connections to that port , and achieve equal distribution. Either by irule/someother method. it looked simple however hard to achieve.
-thank you fellow F5 user
question:: is there a way to monitor the ()
7 Replies
sprashanthac_81VIRTUAL-LISTENING-ON-50101 (has Fastl4 enabled) SNAT2VIP POOL-SERVERS-JAVA-SERVERS SERVER-A:50102 SERVER-A:50104 SERVER-B:50101 SERVER-B:50103- sprashanthac_81
Also just to add, there is no one connect enabled... so that is also ruled out
shaggyis persistence enabled?- sprashanthac_81no persistence enabled that is the mystery.... Why it does not work. It does have a performance L4 applied. and then next step is to remove that and make it standard. Hope that fixes something
- shaggycan you provide the SNAT2VIP irule? do you have priority group activation enabled in the pool? are the servers used in other pools on the F5? how many clients are connecting to this virtual server? are all pool members passing the associated health monitor(s)?
- sprashanthac_81
when CLIENT_ACCEPTED { set VirtualIP [clientside {IP::local_addr}] snat $VirtualIP}
As I said there are no fancy methods assigned, no priority, no persistence, Yes they are used in other pools, however listening on different port numbers (so cannot use the least conn node). Once connection is established it stays on until dropped on the backend serverside. Yes all health checks are TCP or pings basically and they are all up.
- sprashanthac_81Also, there is one LB method that we are planning to use called the least session method. Probably that would be the last option as in the LB method from LTM it self.
