Installing Solarwinds SCOM MP on a Clustered RMS

I'm trying to get the Solarwinds MP 1.1 to work on my SCOM 2007 R2 PoC environment. First question is: according to the docs it's only supported on W2k8. I'm running my SCOM 2007 R2 environment on W2k3 servers. The previous version of the MP (1.0) is stated as being supported on W2k3, but only runs on SCOM 2007 SP1. Can anyone confirm that 1.1 will also run on a W2k3 box? Will I need to upgrade to W2k8 if I want to use this on a SCOM 2007 R2 environment? Or can I use the old MP 1.0 to run on my environment? (and where can I get the old MP?)

Second question is: inital installations failed, due to me trying to install this on a MS. I got the 'failed to start the service' errors. I found out that the service is trying to talk to a RMS service on a 'localhost' level. So I guess it needs to be installed on the RMS... This makes my life difficult, since I've migrated to a clustered RMS. Of course, just installing it on a clusternode failed.. no RMS services there, they're at the cluster(name) level. So how to get this to work on a clustered RMS?

I've unpacked the .msi, lots of interesting things there.. Also I've run a loged msiexec install to see what it does. Next I'll be trying if I can manually install this on my clustered W2k3 RMS boxes, but if anyone can shed any light on this.. please do! (especially if my attempts are doomed to fail due to the W2k3/W2k8 issue, please do let me know... )

Thanks in advance! Pieter

Find more posts tagged with

scom_2007_r2_solarwinds_mp_1.1_clustered_rms_w2k3_w2k8

Accepted answers

Karlo.Zatylny

Hi,

SCOM 1.1 requires Orion 9.5. There is a component in 9.5 that does not exist in 7.7, namely the SolarWinds Information Service that didn't exist back when 7.7 was released.

We have not tested installing a separate Information Service on the 7.7 database, so I would guess your chances are slim but possible. The database schema has changed significantly from 7.7. We have added ESX, wireless, energywise, and a bunch of other improvements that have changed the database that the information service reads.

If you have a spare server, you could install a 9.5 evaluation and poll a few devices and confirm your SCOM 1.1 is set up properly.

Thanks

All comments

Karlo.Zatylny

Hi,

We have tested and officially support Windows 2K3 for the Orion SCOM MP.

For version 1.1 we require SCOM 2007 SP1 or SCOM 2007 R2. Both versions are supported with the new 1.1 release on both 2K3 and 2K8 boxes.

Orion SCOM MP requires to be installed on RMS with the Health and SDK services running. If you have a clustered environment then you need to make sure that your server with Orion SCOM MP has all these componenets to be fully functional.

Please let me know if you have any additional questions.

PBovy

Karlo,

thank you for the clarification. It rules out a couple of concerns I have. Now I know that my config is at least supported (apart from the Cluster). Perhaps the v1.1 manual should be amended, it lists SCOM 2007 R2 & W2k8 as minimum requirements.

Unfortunately, it doesn't solve my problems completely..

When installing on the active W2k3 clusternode of my W2k3 RMS cluster, the installation fails, the Orion service will not start. This is not unexpected, since it's trying to run under the clusternode name and both Health and SDK are running under the clustername.

I have tried breaking off the installation before it tries to start the service and creating a clusterresource service for the Orion service by hand, but unfortunately this doesn't work. Is there any logging to be found on what the service is failing to do, and why it won't start? I must be missing something. I'd love to get this working.

I'm going to go through the logging I got from a (failed) logged msiexec install to see if there is anything else I need to do at clusterlevel to get this working, but any help would be much appreciated!

PBovy

Karlo,

second question: I went out on a limb, and installed the MP in our production environment. There the RMS has not been clustered yet. It started the Orion MP service succesfully, but then, when the installation ran its restartservice tool to restart the Health service it failed. It's timing out waiting for the service to restart.

I can explain this, we're moving our RMS to new hardware and a cluster because of performance issues and the current RMS is too busy.. hence the timeout on the restartservice.. it takes a (couple of ) minute(s) for this service to restart on the RMS.

What are the possibilities to make this restartservice wait longer? I know I can adjust the timeout on a restart of a service through the registry, but will this work in this case?

PBovy

Progress.. kind of..

I've managed to get the Orion MP service working on my clustered RMS. By making it a 'Generic Application' in the Clustergroup of the RMS resources. It's now running under the cluster credentials and talking to the RMS services.

Next challenge is the running of the config wizard. It wo'nt talk to the Solarwinds Server. It turns out that we are running version 7.7.. (ahum....). I've requested an upgrade to the latest version, but no telling if this will / can be done.

In the meantime I've managed to get the v1.0 of the mp, with the information service. I've installed this information service on the server running the Solarwinds app. Unfortunately it's throwing several errors in the local eventlog (perf counters not loaded, SMSvcHost 3, custom counter, ReadOnly).

After installing the v1 MP by hand, I tried running the config tool again, but it's failing to connect to the solarwinds server, with errors from the Proxy, it can't verify security for the message. I've tried all the Solarwind credentials we have, I'm assuming at this point it's due to the outdated version of Solarwinds... What are my chances of getting this to work (for the time being) under the old v1 MP with SW 7.7 & SCOM 2007 R2?

Karlo.Zatylny

Hi,

SCOM 1.1 requires Orion 9.5. There is a component in 9.5 that does not exist in 7.7, namely the SolarWinds Information Service that didn't exist back when 7.7 was released.

If you have a spare server, you could install a 9.5 evaluation and poll a few devices and confirm your SCOM 1.1 is set up properly.

Thanks