Last Modified: Jul 12, 2023
Affected Product(s):
BIG-IP All
Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Fixed In:
13.1.0
Opened: Dec 13, 2016 Severity: 4-Minor
A config load failure can be caused by changing the mgmt shared settings api-status availability settings.
tmsh load sys config fails.
This might occur in the following configuration: (tmos)# list mgmt shared settings api-status availability deprecatedApiAllowed { deprecatedApiAllowed true } (tmos)# list ltm profile fastl4 fastl4_1 [api-status-warning] ltm/profile/fastl4, properties : deprecated : software-syn-cookie ltm profile fastl4 fastl4_1 { app-service none software-syn-cookie enabled } tmos)# list ltm virtual my_vs ltm virtual my_vs { destination 0.0.0.0:any mask any profiles { dos { } fastl4_1 { } } source 0.0.0.0/0 translate-address disabled translate-port disabled vs-index 4 } (tmos)# save sys config Saving running configuration... /config/bigip.conf /config/bigip_base.conf /config/bigip_user.conf Saving Ethernet mapping...done (tmos)# modify mgmt shared settings api-status availability deprecatedApiAllowed false (tmos)# q (tmos)# load sys config ... 01020036:3: The requested profile (/Common/fastl4_1) was not found. Unexpected Error: Loading configuration process failed. Changing the mgmt:shared:settings:api-status:availability:deprecatedApiAllowed to false, makes the validation more restrictive. This causes the prior saved configuration fail to load. Note: ltm profile fastl4 and ltm virtual my_vs are for illustrative purposes only. The same issue can occur for other elements with deprecated apiStatus.
To have subsequent tmsh load sys config operations succeed, run the following commands: #tmsh modify mgmt shared settings api-status availability deprecatedApiAllowed true #tmsh save sys config
None