discovery problem!!!

Thanks for the update Fabrizio. The error you're getting could be the result of either of the following causes:

 

 

1. The F5 Monitoring Service cannot connect to the SCOM Health Service, for writing health and performance data, or:

 

2. The F5 Management Pack data sources are not loaded in the SCOM Health Service running on the Management Server where you monitor the F5 Devices from.

 

 

I'm going to assume that you have done the correct deployment of the F5 Management Pack in your distributed SCOM environment: first you have installed the F5 MP on the RMS where you have left the F5 Monitoring Service stopped (and in Manual/Disabled) mode as the F5 MP setup leaves it, and then you deployed the F5 MP on a (secondary) management server, where you plan to discover and monitor the F5 device(s) from. If my assumption is not correct please let me know.

 

 

Coming back to the two possible causes for the error, for 1 make sure that the service account running the F5 Monitoring Service is in the Operations Manager Administrators group.

 

To validate 2, I would suggest running the "Show Failed Rules and Monitors for this Health Service" SCOM task for the Management Server where the F5 devices are being discovered/monitored from. The output of this task will show if the F5 Management Pack data sources are not loaded.

 

 

You can run the task from the SCOM Management Console :: Monitoring :: Operations Manager :: Management Server :: Management Server Health State :: select your management server :: Health Service Tasks (in the Action pane) :: Show Failed Rules and Monitors for this Health Service. Please let me know the result of this task or if you need assistance running it.

 

 

Also, if you send us the Operations Manager event log and the F5 Monitoring Log (event log) to managementpack(at)f5(dot)com, we can probably find out more about the root of the problem.

 

 

Thank you.

 

Julian