Bug ID 1388997: Identical listeners can be deployed to the same BIG-IP Next instance

Last Modified: Oct 19, 2025

Affected Product(s):
BIG_IP_NEXT(VE/HW) TMOS(all modules)

Known Affected Versions:
20.0.1, 20.0.2

Fixed In:
20.1.0

Opened: Oct 26, 2023

Severity: 2-Critical

Symptoms

Two or more identical listeners within the same application or across multiple applications can be configured successfully. There is no validation check to identify identical listeners in the BIG-IP NEXT. Protocol, Destination IP address, Destination port, and L3-networks of listener configuration are considered as unique for Traffic Matching Criteria validation.

Impact

Even though identical listeners can be configured and deployed to the BIG-IP NEXT instance, deployment will fail. TMM creates only one active listener in the case of an identical listeners configuration.

Conditions

Deploy two different application services using the same listeners or Deploy an application with two same listeners.

Workaround

Assign different listeners for different/same application services to avoid failed deployment. If any two existing applications have the same listeners defined, you can change the data by adding unique listeners and re-deploying.

Fix Information

Implemented Traffic matching criteria validation as part of the data plane validator. For version 20.0.2 (K-2023.11.14) release validation considers unique/unicast destination IP address along with Protocol, Destination port, and L3-network. For version 20.1.0, the subnet and range format of destination IP addresses will be included as well as part of the validation. In case of conflicting traffic matching criteria, below validation error below can be seen in DPVD logs “Configured application <FIRST_VIRTUAL_SERVER_NAME> has conflicting traffic matching criteria with application <SECOND_VIRTUAL_SERVER_NAME>” This validation can be disabled by following the below steps in the NEXT instance sudo kubectl edit deploy f5-fsm-tmm Modify “DPVD_NETWORK_VALIDATOR_ENABLE” env variable to “false” This validation can be disabled by following the below steps in the NEXT instance sudo kubectl edit deploy f5-fsm-tmm Modify “DPVD_NETWORK_VALIDATOR_ENABLE” env variable to “false”

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips