Bug ID 2313477: TMC Fallback Wildcard Synthesis Incorrectly Sets prefix_len(0), Causing Config Load Failure When Coexisting Wildcard Forwarding virtual server Already Owns The 0.0.0.0 Virtual Address

Last Modified: Jul 28, 2026

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

Known Affected Versions:
17.5.1.6, 17.5.1.8

Opened: Jun 03, 2026

Severity: 3-Major

Symptoms

After upgrading to an affected version, a configuration containing both a wildcard IP-forwarding virtual server and a second virtual server using a Traffic Matching Criteria (TMC) with a source address list may fail to load with the following error: 0107176c:3: Invalid Virtual Address, the IP address 0.0.0.0 already exists. Unexpected Error: Validating configuration process failed.

Impact

The BIG-IP system fails to load its configuration after upgrade, interrupting traffic processing

Conditions

All of the following must be true: - A wildcard IP-forwarding virtual server exists with destination 0.0.0.0:0 and mask any - A second virtual server in any partition references a TMC configured with: - destination-address-inline 0.0.0.0 (any destination) - destination-port-inline <port> - source-address-list <list-name> - No destination-address-list - The configuration is loaded from disk (upgrade, reinstall, or MCP force-reload)

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips