Bug ID 447132: Log messages when OneConnect is combined with HA on backup systems

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.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.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3,,,,, 11.6.4

Fixed In:

Opened: Feb 04, 2014
Severity: 3-Major


Log messages occur when OneConnect is combined with high availability (HA) on backup BIG-IP systems.


The system logs messages. The messages indicate that the HA backup BIG-IP system is not correctly mirroring some flows. If a failover event occurs, then those flows might not be transferred correctly. The messages appear similar to the following: err tmm1[7270]: 011f0007:3: http_process_state_prepend - Invalid action EV_INGRESS_DATA during ST_HTTP_PREPEND_HEADERS (Server side: vip=/Common/QR_VS6_80 profile=http server_ip=


OneConnect and HA are both configured. This might occur due to a race condition that results in loss of sync between the active and standby systems. When sync is regained, there is no guarantee that the OneConnect pool of connections will be the same between the two systems. If they are not, then eventually the two systems pick different flows, and the system posts the resulting HTTP message.



Fix Information

OneConnect is now packet-mirroring aware. HA has improved in reliability, which fixes the race condition in packet mirroring when OneConnect and high availability are both configured.

Behavior Change