F5 SCOM Management Pack Not Collecting All Data

Hi Joe,

 

 

Thanks for the update. The post is very clear. I believe the critical state that you're seeing for the F5.MonitoringService monitor may not be accurate, since you don't see any 401 event ID errors in the event log. This monitor should only be triggered by a current 401 event ID error. The 704 event ID warnings about the unknown config items encountered are not critical. This issue should be fixed in a more recent build/release of the F5 Management Pack (v2.1.5.440).

 

 

First I'd like to troubleshoot the [apparently] inadequate health state of the F5 Monitoring Service in SCOM. This may reflect a stale config state of SCOM's Health State Configuration Cache. I would recommend the following steps:

 

 

1. Close the alert regarding the 401 event ID error in SCOM.

 

2. Stop the F5 Monitoring Service.

 

3. Enable verbose logging support (see http://devcentral.f5.com/wiki/default.aspx/MgmtPack/GeneralTroubleshooting.html).

 

4. Stop the SCOM services (Health, Config and SDK).

 

5. Delete the SCOM health state config cache file (OpsMgrConnector.Config.xml), located in \Program Files\System Center Operations Manager 2007\Health Service State\Connector Configuration Cache\ folder

 

6. Restart the SCOM services (SDK, Health, Config).

 

7. Start the F5 Monitoring Service.

 

 

Make sure the health state config cache file has been created in the location mentioned at 5. If this file has not been created automatically we need to take a deeper look on why the SCOM SDK connector cache wouldn't update. If the config cache is successfully created and you still get the red state on the F5 Monitoring Service monitor, please zip and email the trace.log file located in \Program Files\F5 Networks\Management Pack\Log to managementpack(at)f5(dot)com.

 

 

Also, please send us the F5 Monitoring Log (zipped) and the override management pack (XML file) for the F5 Management Pack overrides.

 

 

Thank you.

 

Julian