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

Last Modified: Sep 13, 2023

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

Known Affected Versions:
14.1.3,, 14.1.4,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3, 16.0.0,, 16.0.1,

Fixed In:

Opened: Jan 10, 2021

Severity: 3-Major


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.


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


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


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

Fix Information

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

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips