Forum Discussion
Testing for iControl auth errors
Hi folks,
one of my clients noticed API auth errors after upgrading the systems to TMOS v15.1.5.1. When trying to use a newly created auth token to access LTM objects via API the systems returns ...
Hi, on behalf of my client I opened a service request with the F5 support.
The engineer was able to reproduce the issue based on the script provided.
The Bug ID 1108181: "iControl REST call with token fails with 401 Unauthorized" was confirmed and an Engineering Hotfix for TMOS v15.1.5.1 (Hotfix-BIGIP-15.1.5.1.0.230.14-ENG.iso) was provided. I can confirm, the hotfix solves the issue.
I can also confirm, that TMOS v16.1.3 is not affected.
In case you are facing sporadic issues with the F5 Ansible modules after upgrading to TMOS v15.1.5.1, it might be worth to try the script and to open a service request with F5 support.
Thanks again to Leslie_Hubertus
One of my colleagues in PS (who mainly works on Rakuten stuff) said,
"If the problem is related to REST API then the workaround is to add more memory to restjavad process:
tmsh modify sys db provision.extramb value 2000
tmsh modify sys db provision.restjavad.extramb value 1984
tmsh modify sys db restjavad.useextramb value true
tmsh save sys config
bigstart restart restjavad
bigstart restart restnoded"
They think that “provision.restjavad.extramb” was added in 15.1.3.something.
Here's the K30042148: Restjavad memory provisioning threshold limit article.
Hi Leslie_Hubertus,
thanks for your reply. I have tried it, but it doesn´t work.
The following command isn´t available on my device under test (TMOS v15.1.5.1):
tmsh modify sys db provision.restjavad.extramb value 1984Btw, I also tried to provision MGMT with more resources. No luck.
Last week I opened a service request with F5 support. As soon as a solution is provided, I will post it here.
Best regards, Stephan 😊
Well, drat. I was hoping.
Vielen Dank in advance for coming back to share the solution when you get one, StephanManthey!