I am experiencing discover issue while trying to add the F5 LTM guest to BIG IQ, Its throwing error as "check credentials: Unauthorized(401)" even though the credentials are correct.The guests are running code 126.96.36.199.. Big IQ is running 188.8.131.52
I have tried clearing reset java storage as well as restjavad process. Any suggestion would be greatly appreciated.
Have you confirmed that the request from the BIG-IQ is making it to the BIG-IP in question? Are you 100% certain that they are the correct credentials for the admin user of the BIG-IP? You should be able to perform a tcpdump on the BIG-IP on the interface that the BIG-IQ is connecting to so you can validate the request is making it to the BIG-IP. You should also be able to validate the user attempted to log into the BIG-IP by checking the audit logs.
Thanks all for the reply, I have tried to use admin/root as well as my Tacacs credentials and all of them throwing this error. I dont see this issue with code 184.108.40.206.
The connectivity from BIG IQ to the VCMP guest is good as i can telnet over port 443 as well as 22.
Yes thats correct, No issues with 220.127.116.11.
I have already tried to clear rest java storage and restated the restjavad process as well, i know the upgrade to 18.104.22.168 will fix the issue however was looking for some workaround solution.
Could you fix this?
I have tried suggested workaround but it still fails.
I have tried rebooting device and I have upgraded to 22.214.171.124 (from 126.96.36.199) and I am not able to add big-ip to the big-iq.
@pponte If you are user @ashu_aggarwal1 as well you should really stay logged in as the same user in order to not confuse those who are assisting you. Aside from that, it seems that you are at the position where you need to perform a code upgrade to resolve the issue if not of the articles are resolving your issue. I recommend creating a QKVIEW and uploading it to iHealth if a code upgrade to the latest does not fix your issue. This is all assuming that you have logged into the BIG-IQ CLI and attempted to SSH to the management IP of the BIG-IP as well as performing a rest command to 443 on the management IP of the BIG-IP as well. The user credentials need to be the local admin credentials of the BIG-IP in question.