Nimbostratus
I got the setup log, analyzed it and everything looks fine (apart from the few previously failed attempts to install the F5 Management Pack). So I assume the F5 MPk and the related datasources are correctly deployed in SCOM, which makes me think that the error condition signaled by the 405 and 800 event IDs may be caused by a stale state of the F5 workflows in the SCOM HealthService. If you restart the SCOM HealthService (and consequently the F5 Monitoring Service would restart because of the dependency), are you still getting the 405 error? Is the error re-occurring in a timely manner?
If you still get the errors, we can further investigate the sanity of the F5 workflows / SCOM HealthService by analyzing the Operations Manager event log, which you could forward to us at managementpack(at)f5(dot)com. You can also use the Workflow Analyzer tool (in the SCOM 2007 R2 Authoring Resource Kit) to check the state of the running F5 workflows in SCOM. You can download it here: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9104af8b-ff87-45a1-81cd-b73e6f6b51f0&displaylang=en
You can also check for failed workflows by running the related SCOM task in the Management Console >> Monitoring >> Management Group Diagram >> select the RMS in the diagram view >> Health Service Tasks (on the right) >> run the following tasks:
- Check Health Service Startup Configuration Diagnostic Task (used by Health Explorer)
- Show Failed Rules and Monitors for this Health Service
Let us know about the results of these tasks. If you want to expedite the troubleshooting process, we can also assist you trough a GoToMeeting session and try to help you directly, to get this problem solved as soon as possible.
Julian
