Bug ID 530011: The TCP::option iRules command fails following upgrade to BIG-IP 11.x

Last Modified: Sep 13, 2023

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

Known Affected Versions:
10.2.4, 11.0.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.6.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Opened: Jun 25, 2015

Severity: 4-Minor

Related Article: K96532411

Symptoms

The iRules command TCP::option fails after you upgrade to BIG-IP 11.x. As a result of this issue, you may encounter one or more of the following symptoms: -- F5 iHealth lists Heuristic H539210 on the Diagnostics :: Identified :: Medium screen. -- You upgrade from BIG-IP 10.2.x to BIG-IP 11.x and see that iRules causes an error and triggers the following event: -- CLIENT_ACCEPTED - Illegal argument. TCP::option get on profile without tcp option setting (line 1) invoked from within 'TCP::option get 8'.

Impact

iRules that use TCP::option and depend on Rules.Tcpoption.settings do not work as you expect when you upgrade from BIG-IP 10.2.x to BIG-IP 11.x.

Conditions

This issue occurs when all of the following conditions are met: -- You use an iRule that contains the command TCP::option to gather TCP option information from the TCP header. -- You set the database variable Rules.Tcpoption.settings to specify a TCP option to collect.

Workaround

Configure TCP profile after upgrade that collects the version-specific TCP::option for iRules, as shown in the following example: create ltm profile tcp profile_name tcp-options "{8 last}" To work around this issue, configure the TCP profile after the upgrade that collects the appropriate TCP option for the iRule. Refer to the following article for information about changes to the TCP::option command in 11.x: TCP on F5 Cloud Docs :: https://clouddocs.f5.com/api/irules/TCP.html

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips