Bug ID 980821: Traffic is processed by All Port Virtual Server instead of Specific Virtual Server that is configured.

Last Modified: Jul 23, 2021

Bug Tracker

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

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1

Fixed In:
16.1.0, 16.0.1.2, 15.1.3.1, 14.1.4.2

Opened: Jan 10, 2021
Severity: 3-Major

Symptoms

Traffic is directed to a virtual server that is configured with port any even though there is a virtual server with a specific port that the traffic should match.

Impact

Traffic destined to the port matches the any-port virtual server rather than the specific port virtual server.

Conditions

There are two virtual servers configured: - One with a specific port and ip-protocol 'any' - One with port any and a specific ip-protocol

Workaround

Create individual listeners for specific protocols. For example, given the configuration: ltm virtual vs-port80-protoAny { destination 10.1.1.1:80 ip-protocol any ... } ltm virtual vs-portAny-protoTCP { destination 10.1.1.1:0 ip-protocol TCP ... } Replace the vs-port80-protoAny with virtual servers configured for the specific protocols desired: ltm virtual vs-port80-protoTCP { destination 10.1.1.1:80 ip-protocol TCP ... } ltm virtual vs-port80-protoUDP { destination 10.1.1.1:80 ip-protcol UDP ... }

Fix Information

More specific virtual server now gets more priority than wildcard virtual server to process traffic.

Behavior Change