For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

gbunting's avatar
gbunting
Icon for Nimbostratus rankNimbostratus
May 01, 2009

Discovery failure: invalid certificate when trying to update the Big3d

I was able to run the f5mpgui.exe -DD command from a command prompt opened with the run as administrator. The pathing was correct. I should have left a space between management and pack.   ...
management
microsoft
scom
Dave_Ruddell_79's avatar
Dave_Ruddell_79
Historic F5 Account
May 04, 2009
Currently we only support running the tasks from the computer they were installed on. The issue you were having before may have been caused by running discovery from the web console or a management server other than the RMS. Remote Desktop and Terminal Services should work just fine for discovery, however.

 

 

Do you have IPv6 installed? And if so, if you are not using it, try uninstalling it completely and trying discovery again. We've noticed some compatibility issues with IPv6 and certificates.

 

 

If that is not the issue, you can enable verbose logging by following the instructions here: Click here. Once you have this turned on, you should restart the "F5 Monitoring Service" and then try to discover again. If it is still failing at this point, if you can attach the trace.log file from C:\Program Files\F5 Networks\Management Pack\Logs we can read through it and figure out what is causing the invalid certificate error.

 

 

Thanks,

 

`Dave