Forum Discussion
Device Discover fails
I am trying to add a pair of BIG-IP in F5 MP I installed today but unable to success Device Discover regardless performing big3d install. My BIG-IP is 10.0 and F5MP is downloaded today.
Log message of the result of the discovering is attached.
Please let me know if you need further information.
- Hello,
Thank you for providing the detailed trace log. It looks like there may be a bug in the F5 Management Pack's support for your object.
We will attempt to reproduce the issue and let you know the results of the investigation.
Thank you,
Stephen - Hi, can you tell me if you have BIG-IP version 10.0.0 or 10.0.1 ?
- Currently we are running 10.0.1.
- The management pack is detecting the BIG-IP as version 10.0.0 -- could you take a look at the version file on the BIG-IP to confirm what you see there ("more /VERSION") ?
If it says "10.0.0" in the VERSION file I will have a workaround for you -- otherwise I may need to ask for some more detailed logs. - I'm sorry about that, it is 10.0.0 build 5401. Please give me information on workaround. thx
- Thanks -- this problem is due to a change that we thought was introduced in version 10.0.1 of BIG-IP, but was actually introduced in version 10.0.0.
A fix will be in the next version of the MP, but I can give you a workaround if you are comfortable executing a SQL script in your SQL server. Here is the process:
1) Stop the "F5 Monitoring Service" service on the RMS (or the management server(s) if you have a distributed opsmgr installation)
2) Open SQL Server Management Studio
3) Connect to the same SQL server that you used during installation of the management pack
4) Expand the Databases list on the left and click on the "F5_ManagementPack" database
5) Click on the "New Query" button in the top left
6) In the query window, paste in the following command:
UPDATE StaticDefs.MonitorState SET MinimumVersion = '10.0.0' WHERE MinimumVersion = '10.0.1'
7) Execute the query by clicking the 'Execute' button or using the Ctrl+E shortcut. The bottom pane may show "(13 row(s) affected)".
8) Start the F5 Monitoring Service, wait a few moments, and then try discovery again - Thank you for the support.
I did the operation you described and attempted "Rediscover F5 Device Configuration" but same error occurred. Attachment is error message.
Please let me know if you need more data to investigate this issue.
Thank you,
