Last Modified: Jul 22, 2021
See more info
Known Affected Versions:
126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 15.1.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52
16.0.0, 15.1.1, 184.108.40.206, 220.127.116.11
Opened: Mar 16, 2020
The source port is always changed in source-port preserve mode even if the original source port with the other parameters would hash to the same TMM.
Applications relying on a specific, fixed source port might not work as expected.
This issue occurs when both of the following conditions are met: -- The virtual server is configured with source-port preserve (the default). -- The system uses one of the following hash configurations including IP addresses. - Using RSS DAG as a default hash on BIG-IP Virtual Edition (VE) (Z100) or on 2000- and 4000-series devices. - Configuring a VLAN's 'CMP Hash' setting to a non-default value. - Using a special variable such as non-default udp.hash or tcp.hash.
Set source-port to preserve-strict.
Now source-port preserve setting does best effort to preserve the source port.
Beginning with v16.0.0, the TM.PortFind.Src_Preserve BigDB variable introduced in v15.1.0 is no longer supported. The source-port preserve setting now does best effort to preserve the source port.