Bug ID 1059441: Upgrading with a configuration that contains objects with properties that override the TCP profile can result in incorrect property values being used.

Last Modified: Jan 20, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP Install/Upgrade, LTM(all modules)

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1

Opened: Nov 03, 2021
Severity: 4-Minor

Symptoms

1. Displayed TCP profiles properties (for example, 'tmsh list ltm profile tcp') indicate they are using property values of the main TCP profile, even though they are marked as defaulting from the 'tcp-legacy' profile. 2. tmsh and the BIG-IP GUI display different values for TCP profiles.

Impact

TCP traffic-processing objects might start using invalid property values.

Conditions

This issue usually results after an upgrade from an older version (for example, 12.x to 13.x) where the configuration contains customized tcp profiles that use default values from the main tcp profile (these profiles are modified to use default values from the tcp-legacy profile during the upgrade process).

Workaround

If this problem is observed after an upgrade, use the following command sequence to reload the configuration: 1. tmsh save sys config 2. tmsh load sys config

Fix Information

None

Behavior Change