The F5 Monitoring Service Data Source Singleton Error

The F5 Monitoring Service depends on the SCOM Health Service, so this means that the SCOM Health Service needs to be up and running for the F5 Monitoring Service to start.

 

The reason why the F5 Monitoring Service starts and then eventually would stop is because it cannot connect to the SCOM Health Service. But the SCOM Health Service is obviously running, so it's either a permission issue of having the communication channel open between the F5 Monitoring Service and the SCOM Health Service, or the F5 data sources are not loaded inside the SCOM Health Service.

 

 

What I'd like to check next, is to make sure the F5 data sources and workflows are loaded and actually running inside the SCOM Health Service. What we've checked previously was to look for 'Failed Rules and Monitors'. So the task you'll be lookinf for to run is "Show Running Rules and Monitors for this Health Service":

 

 

You can run the task from SCOM Management Console :: Monitoring :: Operations Manager :: Management Server :: Management Server Health State :: select your management server :: Health Service Tasks (in the Action pane) :: Show Running Rules and Monitors for this Health Service.

 

 

Make sure you see the F5 Monitors and rules loaded and running. If not, than we may have a problem with the actual SCOM F5 Management Pack not being correctly imported in SCOM.

 

 

Let me know.

 

Julian