F5 MP fails to resolve the right host name for the SCOM Health Service in an MS Cluster

I've added a new thread on the current issue for better tracking. As Vincent pointed out, he had similar issues while deploying the F5 Management Pack in on an RMS cluster and they could be worked around until a certain point. Thanks to the significant feedback from you guys, some of these issues have already been resolved in our F5 MP/setup (and will make it into our next release of the F5 MP).

 

 

For you Bao, the problem is that when the F5 MP is trying to resolve the host name of the [virtual] host (i.e. cluster group) running the clustered SCOM Health Service, which is actually the "RMS Cluster Group", it will get this right, but then when trying to query the Health Service status through the Service Control Manager (SCM), it will still use the "RMS Cluster Group" host name, which is obviously wrong. It should rather query the SCM through the FQDN/NetBIOS name of the server hosting the cluster. Apparently this has been working as expected under Windows Server 2008 / R2 but is producing the error that Bao is hitting, on Windows Server 2003. We're looking into fixing this issue as well.

 

 

Unfortunately there's not much we can do to circumvent the problem at this point, so Bao, you'll have to wait for the new F5 MP release which will address this issue. We are working hard to get this new release out the door ASAP and will let you know when this happens.

 

 

Thank you for your support and patience!

 

Julian