F5 SCOM Management Pack Not Collecting All Data

From the trace logs you've sent us I can see that statistics are collected from the F5 device. The only errors that I've seen in the trace log were: Device x.x.x.x has received configuration iQuery on the stats connection; may indicate stats request for invalid object. These errors eventually cleared up, right after your service configuration update for enabling the verbose logging. So I assume you may have had a stale device configuration state cached for the F5 Monitoring Service.

 

 

Regarding the critical state on the F5.MonitoringService monitor: this could have been triggered by the 401 event ID error (which I assume you would see in your F5 Monitoring Log in the Event Viewer). The critical state of this monitor should be automatically reset by a 'paired' 202 event ID, on a successful service start-up / restart, but unfortunately this doesn't work as expected in your case (the related bug has been recently fixed). So, go ahead please and [manually] close / resolve the related alert on the F5.MonitoringService monitor and restart the F5 Monitoring Service (using the Windows Services Control Manager MMC snap-in).

 

 

After the service restart, check the F5 Monitoring Log in the Event Viewer and make sure there are no errors (Event ID 201 or 401). Then make sure you have a healthy state on the F5.MonitoringService monitor in SCOM. If it does stay green, you should be fine with the health of the F5 Management Pack.

 

 

If you still get the red state on the F5 Monitoring health, let us know. Otherwise you should be seeing the stats enabled by default for the F5 Management Pack coming in. If you plan on overriding other rules for the F5 Management Pack, make sure you follow the appropriate steps described here: http://devcentral.f5.com/wiki/default.aspx/MgmtPack/PerformanceCollectionAndMonitoring.html

 

 

Let us know the results.

 

Thank you.

 

Julian