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