Last Modified: Nov 08, 2022
See more info
BIG-IP Install/Upgrade, LTM
Known Affected Versions:
16.1.0, 16.1.1, 16.1.2, 188.8.131.52, 184.108.40.206, 16.1.3, 220.127.116.11, 18.104.22.168
Opened: Nov 07, 2019
Validation for TCP::collect was changed in BIG-IP software v12.0.0 (with the introduction of JET specifications). Prior to 12.0.0, there were no restrictions on the values of the two arguments. As of 12.0.0, the first argument ('collect_bytes') must be a positive integer, and the second argument ('skip_bytes) must be a non-negative integer. Occurrences of 'TCP::collect 0 0' in iRules experience issues when upgrading to a newer version, producing warnings in LTM log: /Common/T_collect:9: warning: [The following errors were not caught before. Please correct the script in order to avoid future disruption. "invalid argument 0; expected syntax spec:"136 17][TCP::collect 0 0].
Warning in the LTM log file. The iRules containing 0 values do not function as expected. There is no other impact.
-- Using a version of BIG-IP software earlier than 12.0.0, configure an iRule with a 'TCP::collect 0 0' command. -- Upgrade to 12.0.0 or later.
Change 'TCP::collect 0 0' to a value other than 0 (zero) in any iRules before or after upgrade.
TCP::collect now restricts its first parameter ('collect_bytes') to a positive integer, and its second parameter ('skip_bytes') to a non-negative integer.