Last Modified: Jul 12, 2023
Affected Product(s):
BIG-IP Install/Upgrade, TMOS
Known Affected Versions:
12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.0.0
Fixed In:
13.0.0, 12.1.2 HF1
Opened: Nov 02, 2016 Severity: 3-Major Related Article:
K86935473
After upgrading and attempting to set maxMessageBodySize via iControl REST, you get an error indicating the command is not implemented: {"code":400,"message":"onPut Not implemented","originalRequestBody":"{\"maxMessageBodySize\": \"111111111\"}","referer":"127.0.0.1","restOperationId":216941,"kind":":resterrorresponse"}
Command fails, unable to set maxMessageBodySize.
This occurs when upgrading from v11.6.1 to v12.1.0, v12.1.1,or v12.1.2, and applying the UCS from the 11.6.1 release. The error is generated because new defaults were added but they are not set on UCS restore.
If you encounter this after an upgrade and UCS restore, you can run the following commands from the BIG-IP command line: 1. curl -X DELETE http://localhost:8100/shared/storage?key=shared/server/messaging/settings/8100. 2. bigstart restart restjavad.
You can now set maxMessageBodySize via iControl REST after upgrading.