Bug ID 620625: Changes to the Connection.VlanKeyed db key may not immediately apply

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 13.0.0

Fixed In:
13.1.0, 13.0.0 HF1, 12.1.2 HF1

Opened: Oct 05, 2016
Severity: 3-Major
Related Article:


When you modify the connection.vlankeyed database key, some asymmetrically routed connections unexpectedly fail.


Some connections using asymmetrical routing do not reach their destination.


This issue occurs when the following condition is met: You modify the connection.vlankeyed database key. For example, you set the database key value to disable. For more information, refer to K13558: Allowing asymmetrically routed connections across multiple VLANs (11.x - 13.x) :: https://support.f5.com/csp/article/K13558.


Restarting TMM resolves the issue, though this briefly interrupt traffic so should be performed during a maintenance window. To do so, run one of the following tmsh commands: -- On an appliance (BIG-IP platform): bigstart restart tmm -- On a clustered system (a VIPRION or VIPRION-based vCMP guest): clsh bigstart restart tmm

Fix Information

Asymmetrically routed connections no longer fail with Connection.VlanKeyed disabled.

Behavior Change