Forum Discussion
SKS_198176
Nimbostratus
NimbostratusPriority group and least connection.
I have recently started my F5 journey and have a question. Let's suppose that I have a pool with 2 members that is configured as following: Load Balancing Method: least connection Priority Group A...
Hi, source address persistency is not a good idea if all traffic comes from a single IP address.
What is your expected scenario? Why do you think you will need persistency?
If there is a persistency record in the table, F5 basically bypasses load balancing decision and forwards the packet to the member bound to the record. This does not really change much in your scenario since PG2 already only contains one member.
When Member A has reached full capacity and a new client connection is received before persistency record expires, I believe LTM will try to forward this connection to Member A and you will hit a LB_FAILED condition.
You can see in vs and pool statistics if there is any failed LB or resets, or script an iRule that logs a message when this condition is met.
SKS_198176Nimbostratus
NimbostratusHi CA_Valli,
Thanks for the reply, further refinement to the above configuration
What will happen if I configure a source_addr persistence with 120 sec timeout setings ( which means that Member A will receive all the connection for 2 minutes) as it has the highest priority settings.
with the least connection LB method configured with 80 max connection setting, will the LTM reset the 81st connection received within 120 sec time period.
CA_Valli
MVP
MVPHi, source address persistency is not a good idea if all traffic comes from a single IP address.
What is your expected scenario? Why do you think you will need persistency?
If there is a persistency record in the table, F5 basically bypasses load balancing decision and forwards the packet to the member bound to the record. This does not really change much in your scenario since PG2 already only contains one member.
When Member A has reached full capacity and a new client connection is received before persistency record expires, I believe LTM will try to forward this connection to Member A and you will hit a LB_FAILED condition.
You can see in vs and pool statistics if there is any failed LB or resets, or script an iRule that logs a message when this condition is met.
- SKS_198176
thanks