Bug ID 656811: Memory usage with MBLB SIP ingress buffer on standby

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,

Opened: Apr 07, 2017

Severity: 3-Major


Memory usage increases to high levels when the ingress-max profile setting is set to a large value.


Degraded performance. With the built-in MBLB profile allocations will go up to 50 and stay there until the 'while' is killed on the client and the flow is allowed to expire. With a non-default MBLB profile, allocations will go as high as the ingress-max setting.


Incoming SIP messages are mirrored to standby, then the flow is aborted on active.


- Make sure there is at least one available pool member. - Use default MBLB profile, or at least ingress-max set close to the default (50).

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips