Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP GTM
Known Affected Versions:
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, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.0.0
Opened: Aug 15, 2014 Severity: 3-Major
Cannot set GTM wide IP iRules priority via tmsh, so priority does not get saved to config
Creating or modifying Wide IP iRules via a configuration load or interactive tmsh commands results in arbitrary priority ordering for Wide IP iRules.
Modifying Wide IP iRules via tmsh.
If Wide IP iRules need to be executed in a specific order, these priorities can be set via the GUI or iControl SOAP.
The 'add' and 'remove' commands for Wide IP iRules have been removed in tmsh, and the system presents an iRule list of 'none' or re-lists all iRules on a given Wide IP. The listed order of iRules on a given Wide IP implies the priority for these iRules. For example, to set Wide IP 'example.com' A-type Resource Record iRules rule_A, rule_B, and rule_C to have priorities 0, 2, 1, respectively, via tmsh: (tmos)# modify /gtm wideip a example.com rules { rule_A, rule_C, rule_B }.
Previously, tmsh did not allow GTM Wide IP iRule priority modification, although iRule priority could still be set via iControl SOAP and the GUI. In this release, the 'add' and 'remove' commands for BIG-IP DNS (formerly GTM) Wide IP iRules have been removed in tmsh, and the system presents an iRule list of 'none' or re-lists all iRules on a given Wide IP. The listed order of iRules on a given Wide IP implies the priority for these iRules. For example, to set Wide IP 'example.com' A-type Resource Record iRules rule_A, rule_B, and rule_C to have priorities 0, 2, 1, respectively, via tmsh, use the following command: (tmos)# modify /gtm wideip a example.com rules { rule_A, rule_C, rule_B }.