RMS Cluster Installation issues

Kevin,

 

 

I'm sorry you're having these problems. Support for RMS clustering has been recently added to the F5 Management Pack (F5 MP), and if you follow the instructions on this Dev Central article:

 

 

http://devcentral.f5.com/weblogs/jbalog/archive/2010/01/18/clustering-the-f5-management-pack-with-scom-2007-rms-cluster.aspx,

 

 

you should be able to have it set up correctly. If you have a distributed management server (DMS) environment with the RMS cluster (i.e. multiple management servers) it would probably be worth taking a look to an extension of the article mentioned above:

 

 

http://devcentral.f5.com/weblogs/jbalog/archive/2010/03/01/installing-the-f5-management-pack-in-a-scom-2007-rms.aspx,

 

 

about configuring F5 MP with RMS clustering in a DMS environment. I would recommend uninstalling the F5 MP from the RMS cluster and start afresh following the instructions on the Dev Central articles mentioned. Also, make sure you download the lastest F5 MP available on DevCentral.

 

 

* * *

 

 

Now a few words on the actual problems that you were having: a possible reason why the F5 Management Pack will not import in SCOM within an RMS cluster, is if you attempt to install the F5 MP first on a non-active RMS cluster node (i.e. the node is not the owner of the RMS cluster group and such the SCOM Health Service is not running). The Dev Central article about F5 MP and RMS clustering covers this matter in detail.

 

 

The F5MPPATH environment variable is specific to the [internal] PowerShell runspace of the SCOM management console, and this is being set up during the installation process of the F5 MP, and there's really no direct and easy way to manually do this, post F5 MP setup. One reason that I can think of, why the F5MPPATH environment variable has not been successfully saved in your environment, is probably because there were possibly open management console sessions running on either the other RMS cluster node(s) or management server(s). Before installing the F5 MP, I would make sure there are no SCOM management console (and PowerShell) sessions running on the RMS cluster nodes and management servers, just as a safety measure against this issue.

 

 

Let us know how it goes, and if you still have problems, we'll take it from there.

 

 

Thank you.

 

Julian