Bug ID 504854: OneConnect does not balance new traffic for all load balancing methods

Last Modified: Oct 06, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.2.1, 11.4.1

Fixed In:
11.4.1 HF9

Opened: Feb 04, 2015
Severity: 3-Major
Related AskF5 Article:
K16771

Symptoms

With several load balancing methods, OneConnect does not load-balance new connections to pool members as desired. These methods include ratio (node), least connections (node), observed (node) and predictive (node). In these cases, new traffic will continue going to a limited number of pool members.

Impact

Traffic does not balance across nodes as desired.

Conditions

Using OneConnect along with one of the following load balancing methods: ratio (node), least connections (node), observed (node) or predictive (node).

Workaround

This can be partially mitigated if load balancing can be done with other methods; however, using these methods there is no workaround.

Fix Information

Adjusted counters correctly to load balance traffic as desired.

Behavior Change