Hi Ravi,
It looks like the F5 Management Pack condition detection module for monitoring rule overrides may not be correctly initialized in your environment. We would need more information to troubleshoot this. I would suggest the following, for a more efficient troubleshooting:
1. Temporarily disable all of the non-default overrides for the F5 Management Pack (collection rule overrides and threshold rule overrides). I assume you have an override management pack for all these, so you could export this XML file (using the SCOM 2007 Management Console) and then just delete the override management pack.
2. Stop the F5 Monitoring Service.
3. Enable verbose tracing for the F5 Management Pack (
Click here to see how to enable verbose logging support). Remove the existing trace.log file in the Log folder inside the F5 Management Pack installation directory (by default Program Files\F5 Networks\Management Pack).
4. Stop and restart the SCOM Health Service.
5. Start the F5 Monitoring service.
6. Run the "Refresh F5 Device Threshold Rules" action and see if you get any errors. If you do, then zip the trace.log file and go to the last step.
7. Create one threshold rule override (you can add the corresponding collection rule if it's not enabled).
Click here to follow the instructions on how to create collection rule overrides and threshold rule overrides for the F5 Management Pack.
8. Run the "Refresh F5 Device Threshold Rules" action and see if you get any errors. If you do, then zip the trace.log file and go to the last step.
9. (Last step) Run the system information diagnostic script.
Click here to find out more. Zip the output file.
Send us the trace.log and diagnostic output files at the following email address: managementpack(at)f5.com.
I'm not sure yet if this might be related to the report data problem that you also have. It may be a common cause though for both. We'll take a look at the trace logs and diagnostic results once we get them from you, and we'll take it from there.
Julian