Forum Discussion
bd2009_8132
Nimbostratus
Mar 01, 2010F5 MP fails to resolve the right host name for the SCOM Health Service in an MS Cluster
Hi Julian
we're getting this error with our installation on a Windows 2003 cluster RMS
Global Error: 4032828 : [03/02/2010 11:24:23][Service] System.InvalidOperationExce...
Vincent_96498
Nimbostratus
Mar 02, 2010Bao,
For licensing, you will need a key for both nodes.
We also had a similar issue during setup on W2K8 RMS cluster:
<02-03-2010 11:17:20> FatalError: The DataSource and ConditionDetection modules required for the F5 Monitoring Service to run could not be loaded by Operations Manager monitoring host. Check the Operations Manager Event Log for errors and manually start the F5 Monitoring Service once any issues have been resolved.
This has been solved with help of Julian:
1.Remove the F5 Monitoring Service from the RMS cluster group resources (if it’s still there).
2.Uninstall the F5 Management Pack from both cluster nodes.
3.Download the latest F5 MP build (v1.6.2.258) from F5 Dev Central: http://devcentral.f5.com/Default.aspx?tabid=217
4.Install the F5 MP on the current active cluster node. VERY IMPORTANT: towards the end of the installation, after licensing / accept / OK, where the install screen seem to be stuck (spinning), wait up to 1-2 minutes, and if you still have the setup running, let it run, but open up the Services Control Manager and try to manually start the F5 Monitoring Service. After a few moments, following the service start, the setup should complete successfully. This is a known issue and we’re trying to fix it in our next release. If even after the manual start of the F5 Monitoring Service the setup won’t complete successfully, you should stop here and let us know.
5.VERY IMPORTANT: DO NOT add the F5 Monitoring Service to the clustered resources yet and DO NOT fail over to the other cluster node yet.
6.Install the F5MP on the other cluster node, and if you experience the same problem with the last screen (after licensing / accept / OK) hung (spinning), stop here and let us know.
7.Add the F5 Monitoring Service as a cluster resource (following our DevCentral link) to the RMS cluster group and bring the F5 Monitoring Service online. If it doesn’t come up green, stop here and let us know.
8.If you got to this point without errors, and your RMS cluster shows all green, you should be OK now, so you can go ahead and discover a device on the active cluster node.
Hope it can help.
Best Regards,
Vincent
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects