Bug ID 652056: [api-status-warning] are generated at stderr and /var/log/ltm when listing config in tmsh from top level namespace or at module level

Last Modified: Nov 14, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP All(all modules)

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:

Opened: Mar 17, 2017
Severity: 4-Minor
Related Article:


tmsh list at the top namespace or at module level or mode level generates unexpected [api-status-warning] messages. (tmos)# list << top namespace (tmos)# list ltm << ltm module (tmos)# list ltm profile << profile mode Each of the three illustrative examples generates unexpected [api-status-warning] messages at stderr and /var/log/ltm. The warnings are expected only at component level. The following example uses fastl4 as the component: (tmos)# list ltm profile fastl4 myfast [api-status-warning] ltm/profile/fastl4, properties : deprecated : software-syn-cookie <<— warning message; as expected ltm profile fastl4 myfast { app-service none software-syn-cookie enabled }


There is no impact to the system. The excessive [api-status-warning] at stderr and /var/log/ltm for tmsh list commands are spurious and can be ignored.


This occurs when typing 'y' when being prompted to list all items: (tmos)# list Display all 155 items? (y/n) y [api-status-warning] ltm/profile/fastl4, properties : deprecated : software-syn-cookie <<< unexpected warnings These are displayed for several commands that give API warnings.


The following tmsh command can be run to disable all deprecated API warnings: tmsh modify mgmt shared settings api-status log resource-property deprecatedApiAllowed false

Fix Information

[api-status-warning] messages will be generated at stderr and /var/log/ltm with tmsh list for the specific component.

Behavior Change