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

Bao,

 

 

We created a fix for the specific problem you were encountering (failing to correctly resolve the network name of the RMS Cluster Group on a Windows Server 2003 MS Cluster). The reason why we didn't hit this problem in the first place was because in our test environment the name of the RMS cluster group was the same with the Network Name associated with the RMS cluster. And this is always true with Windows Server 2008 clustering, where apparently the cluster group name is the actual network name of the cluster group (in our case the RMS Cluster).

 

 

Just to make sure the fix would cover your environment as well (as there might be some variables that we haven't thought about), can you please check the following, and you can send the results directly to managementpack(at)f5.com:

 

 

1. What is the value for the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0 on any of the RMS Cluster nodes?

 

2. What is the name of the MS Cluster hosting the RMS cluster group?

 

3. What is the name of the Network Name resource associated with the RMS Cluster Group?

 

4. What is the host name shown in your SCOM Management Console's Tools > Connect window?

 

 

For 2 & 3 you would go to the Cluster Administration console and get the values from there. For 3 select the RMS Cluster Group and then in the details panel select the "Network Name" resource, right-click > Properties > Parameters tab > Name.

 

 

Providing the answers for these questions would help us better understand your SCOM RMS Cluster environment and possibly assist us with addressing the possible configuration scenarios with RMS clustering.

 

 

Thanks!

 

Julian