F5 Discovery failure

Hello,

 

 

Is the account 'ncmt01' an administrator account on the BIG-IP? To make changes to the certificates on the BIG-IP, the user must have administrator privileges.

 

 

Thank you,

 

Stephen Fisher

 

F5 Networks

After the account was added as an admin I was able to discover it, but it gets stuck on the Action "Retrieve device chassis." The state just stays at "Starting."

If the discovery is still waiting, you can go to a Console window and run "f5mpcmd /ad YOUR_BIG_MGMTM_IP_ADDRESS" which will abort the discovery, then you can retry discovery.

 

 

Before retrying discovery, can you enable diagnostic verbose logging?

 

 

http://devcentral.f5.com/wiki/default.aspx/MgmtPack/GeneralTroubleshooting.html

 

 

It would be helpful if you can provide the SystemInformation output, the F5 Monitoring and Operations Manager event logs [during the period of time for issue], and the F5 Monitoring service service/trace logs.

 

 

If the discovery gets stuck again, you can send us the logs either zipped here or you can email them to ManagementPack (at) F5 (dot) com.

 

 

Thank you,

 

Stephen Fisher

 

F5 Networks

I enabled verbose logging. Tried discovery again and it still got stuck on the "retrieve device chassis" part. Attached some log files.

 

Hello,

 

 

It looks like you are attempting to discover BIG-IP version 9.3.1.

 

 

Is that correct?

 

 

If so, we have seen some issues with the big3d agent running on the 9.3.1 version. We have made some improvements in the new version of the Management Pack 2.0.0 that was released last week, which may help this particular issues.

 

 

Can you try installing the new version of the Management Pack and retry the discovery?

 

 

Thank you,

 

Stephen Fisher

 

F5 Networks

 

I tried installing the new version of the F5 Management Pack but it came back with an error saying I need SCOMR2 Hotfix KB981740. I followed the instructions and ran the hotfix on our Ops Manager DB with success but an error came back when I tried to run it on the Data Warehouse server. Tried the F5 management pack install again and it still came back with an error. Do I need a successful install on both the Ops Manager & Data Warehouse DBs for the new F5 MP to work?

I believe I know what the issue is. In our setup utility, we are checking for the hotfix to be installed locally, rather than checking the db version directly. This was a mistake on our part, so it will be fixed for next release, but the work around for you right now would be to just install the hotfix utility on the rms/ms that you are attempting to install the F5 Management Pack onto. You don't have to run the sql, it is just looking for the installation GUID for that particular hotfix. Sorry, I know this is inconvenient, but let us know if it installs correctly and you are able to discover your 9.3.1 Big-IP.

 

 

Thanks,

 

Dave

Hello Ying,

 

 

We are aware of this issue and are working on a fix for our next release. Unfortunately we don't have a good workaround for you at the moment, but if we find something that will work, I will be sure to let you know as soon as I can. Sorry for the inconvenience.

 

 

Thanks,

 

-Dave

 

I'm having the same issue when trying to upgrade to 2.1.1.140

I found this thread and am also having a similar issue. I have a clustered pair of LTM 1500s running 9.3.1 build 37.1. My SCOM server is a single server and I recently applied the CU3 hoping to get the discovery working. Since that did not work I saw there was a more recent release to the Management Pack than the 2.0.0 version I had in place, so I upgraded to the 2.1.4 in hopes my units would get discovered, but they were not.

 

 

My SCOM server sits on the same subnet as my units, 192.168.162.0/23. In the F5 Monitoring Log I get the error

 

 

Failed to discover device at address: 192.168.163.248

 

Network-related failure has occurred: [Category]SecureSocketLayer:[Type]ConnectFailure;LastError=SSL IO Error 474139472: SYSCALL: UNKNOWN

 

 

In the actual log that you see when double-clicking the failed discovery I get

 

Execute device discovery:Failure

 

Failure Message: F5Networks.Protocols.iQuery.iQueryException: [Category]SecureSocketLayer:[Type]ConnectFailure;LastError=SSL IO Error 474139472: SYSCALL: UNKNOWN

 

 

I am using an admin account for discovery so the permissions for the account should be suitable. What else should I be looking at?