Last Modified: Apr 11, 2024
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.0.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.6.2 HF1, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1
Fixed In:
11.6.0, 11.5.2, 11.5.1 HF6
Opened: Oct 02, 2014 Severity: 1-Blocking Related Article:
K15476
BIG-IP aborts when mirroring a large size (> 128K) session DB message which can be produced by table iRule command or APM session variable. For APM deployment, most scenario involves with AD/LDAP query with large size AD/LDAP attribute. Please restrict the AD/LDAP query with attributes which actually needed to avoid retrieving unncessary large size attribute which triggers this issue. For table iRule use case, please avoid having a single table entry to hold a large size of data. Please break them into pieces.
The Traffic Management Microkernel (TMM) may produce a core file when using an iRule table command with large datasets, and the BIG-IP system will temporarily fail to process traffic as it recovers from TMM restarting.
This issue occurs when all of the following conditions are met: An iRule contains a table command, such as set, add or replace, which attempts to insert a large set of data (more than 128k): -- Session mirroring is enabled between BIG-IP high-availability devices. Note: Session mirroring is enabled by default through the StateMirror.MirrorSessions database variable.
To work around this issue, revise the iRule to avoid insertion of large datasets. Note: Changing the design of an iRule may have additional effects on traffic processing. Ensure any modification is compatible with your environment.
This release provides improved handling of large objects in the session database.