Last Modified: Jul 18, 2026
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.5.3, 11.5.3 hf1, 11.5.3 hf2, 11.6.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.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 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.0.0, 12.0.0 hf1, 12.0.0 hf2, 12.0.0 hf3, 12.0.0 hf4
Fixed In:
12.1.0, 11.5.4
Opened: Jul 09, 2015 Severity: 3-Major Related Article:
K17495
If the client-ssl profile is /Common/clientssl, its parent profile is supposed to be /Common/clientssl. But the configuration could potentially use 'defaults-from none'.
The upgrade fails after booting into the new release, during the config loading phase. This occurs because the script extracts the line 'defaults-from none' and treats 'none' as its parent profile.
This condition could be caused by executing the following command when generating the configuration. 'tmsh modify ltm profile client-ssl clientssl defaults-from none'
Edit the configuration prior to upgrading, changing the defaults-from value on the client-ssl profile to the name of that profile.
Upgrade no longer fails if 'defaults-from none' is under profile '/Common/clientssl'.