We've had a lot of people downloading the Orion Management Pack for OpsManager 2007. We're wondering how it's going? What's working well? What would you like to see improved?
Denny,
could you explain the benefits of running Orion alongside SCOM 07?
I have some engineers in my organization that are pushing to toss out Solarwinds as our monitoring platform in favor of SCOM.
SCOM focuses on Windows and Microsoft apps. As you might expect, it does pretty good job there. It has less depth on non-Windows OS's or non-MSFT apps. Where it really lacks, however, is in network management. It has only rudimentary ability to do SNMP polling of network devices and their interfaces. If SCOM's app management fits your needs, then running Orion NPM and NTA alongside it are a great complement to get both app and network management.
I am *trying* to use it, but have not been able to get it to work in my environment. I have SCOM running on a Windows 2008 x64 server, and Solar Winds running on a separate Windows 2008 x86 server.
My issue is that after running the Management Pack install, and doing the post-install configuration, none of the monitored nodes show up in SCOM. The only information I see is that in the Orion Components View the Orion Database is shown as being in the Warning state, and the Orion Web Server is shown as critical. This is despite the fact that Orion itself is working just fine in our environment - it is only the Orion-SCOM integration that seems to be having issues. I would appreciate any assistance I could get with this.
I called the Orion support hotline, but they were not able to help me at all.
I wish I could help, but I don't have enough information to know why you're not seeing the correct information . Direct contact with Support is what I would recommend. You might try to re-open that ticket.
SCOM does not even poll interfaces by default. What is does is discover the device using snmp 1 or 2. Once it's entered as a monitored object. It then does an snmp-get to check the availability of the device.
It would be nice to have a select all feature when selecting the node for import. Also it would be nice to have a way to filter out nodes on the import.
deleted
I would like to see the volumes exposed to SCOM as well as the APM elements.
Being able to see the node status and the interface stats is a good start.
Chris Gregors
So I get volumes, but why APM? Doesn't SCOM meet your app monitoring needs? Are you using both?
Rather than go to the trouble of re-implementing UNIX application APM definitions in SCOM, I'd like to expose them to SCOM and then use it for the health-rollup and alerting.
Testing the ORION MP with our LAB SCOM 2007 SP1 setup.
1. Alerts on the NPM console are showing up in the SCOM console about 45 minutes after they occur. Is there some setting I need to change?
2. Our Production SCOM 2007 SP1 is a clustered RMS. Is the management pack
cluster friendly? Cluster Install Procedures?
We are evaluating it in our environment. One question that I have not found the answer too yet. When the Orion MP is imported into SCOM does it generate any SCOM reports or must we use 2 reporting solutions (Orion and SCOM)?
Thanks in advance,
Steve
We are currently evaluating Orion and for us to consider the product it needs to integrate into SCOM, right now it fails to install correctly. Have a ticket open and emailed the sales rep.
We also have a clustered RMS and wonder has the install procedure become cluster aware yet? Today it continues to fail with the cannot restart service error.
