VIP:10.134.34.101 POOL MEMBERS(SERVER-A:10.134.34.177, SERVER-B: 10.134.34.202 )
IF I disable any one pool member round robin load balancing working fine.But if both are up it is not working properly. while pinging web Some times server A opens and once login goes inside server B and not able to login. kindly suggest
hi jason thanks for your comments, Persistence not enabled also i suspect due to VIP,Poolmembers in same segment or due to Automap configured. and also there is no vlan configured in my SLB. All are local
are you saying that round-robin is not sending even traffic to all pool members, or are you saying that the application breaks when you enable more than one server in a pool with round-robin enabled?
Hello kartheeswaran, You’ve mentioned that you have only 2 pool members. i.e. SERVER-A:10.134.34.177, SERVER-B: 10.134.34.202, now when you disable one pool member, round robin works, didn’t get that. Minimum requirement to measure any LB algorithm is to have 2 pool members. If you have only one member available in the pool, we cannot say LB works fine. Can you shed more light here?
Also in this scenario 2 servers are having ssl certificate.Here SSL offloading happens in Server. Not in Load balancer. And given http profile has none
Try enabling persistence. This isn’t an issue with the LB method but is an interoperability issue in which you need a user to continue using the same pool member once a pool member has been selected. Try source_addr persistence at first to see if it resolves your issue. Cookie persistence would probably be better, but the F5 would need to terminate SSL for the application (SSL offload).
I experienced this same problem in LTM 11.6 hotfix 5. After applying the hotfix and coming back up one pool would not send traffic to one of two servers. SA complained that traffic was just hitting one server.
I changed load balancing from Least Connections (member) to Round Robin. No effect.
Just for shiggles I disabled the pool member that was handling traffic. The traffic did them move to the second pool member. I re-enabled the first member and load balancing started happening per the statistics for the pool.
Did you ever get an answer for this i had the same problem twice. one time changing the name of the cookie in our persistence profile fix it. In our upgrade to 12.0 same thing happened but have not had a fix for this yet.
I am facing the same issue. When I am enabling one pool member then connection is going through the server but when i am enabling two pool member it’s not working. I also checked with Least Connection member but it’s not working.