Forum Discussion
Roundrobin Load balancing not happen
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
14 Replies
- JRahm
Admin
Use a tool like ab (you can launch it from the BIG-IP cli) to send multiple concurrent connections and you should see RR kick in.
ab -n 10000 -c 50 http://10.134.34.101/
If you still aren't seeing load balancing, do you have persistence enabled?
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
- JRahm
Admin
surely the self IPs and the VIP are available on at least one vlan (even if it is shared)? are both pool members available?
- NikhilB
Employee
Have you tried another LB algo? (least connections member/node)
Let us know the results.
- shaggy
Nimbostratus
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? - swo0sh_gt_13163
Altostratus
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? - if i disable one pool member , i am able to login server from internet. If I enable both pool member same facing issues. i dont know what bug
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
- shaggy
Nimbostratus
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).
Hi all I used SSL persistence in this https traffic
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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