Bug ID 1462821: Wrong virtual server processing traffic

Last Modified: Oct 19, 2025

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

Known Affected Versions:
16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 16.1.6.1

Opened: Dec 18, 2023

Severity: 3-Major

Symptoms

When applying changes to the traffic-matching criteria (TMC) objects which include port and address lists, the listener is not created and traffic is matching to the wildcard virtual server. Below logs are seen in ltm logs during this scenario. err tmm[489]: 01010008:3: Proxy initialization failed for /Common/my-virtual err tmm[489]: 01010009:3: Failed to bind to address

Impact

Applications may fail due to wrong matching criteria.

Conditions

Configure two virtual servers with the same traffic-matching conditions and one wildcard virtual server. Make some changes to the port list or address list and remove and reattach the traffic-matching criteria to the virtual server.

Workaround

1.Restart the TMM (use the command: bigstart restart tmm) after making changes to traffic-matching criteria. or 2.Reload the configuration. Impact of workaround: both of these workarounds cause a traffic disruption while services restart.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips