nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

How was your NCM Upgrade with Orion Integration

Ciag

Just looking to hear peoples stories who have upgraded Cirrus to NCM and who are also running the integration with Orion NPM. We have downloaded NCM but our management want us to wait before we integrate it with Orion. So I 've raised this topic to hear everyones experience first.

So, good experiences, bad experiences, lets hear them.

Cheers

Ciag

Find more posts tagged with

Accepted answers

All comments

FormerMember

Hi,

Just did the upgrade this morning. I had no problems with the actual installs etc but now i have two different syslog servers, one in NCM and one in Orion. The original syslog server service no longer starts and thus does not collect data .This happens to be the syslog server that is displayed via the orion web interface and i have not been able to swap this over to the new NCM syslog server yet. Does anyone have any ideas on how i would go about this?

Other than this small problem everything else seems to be fine.

Cheers

chris.lapoint

So just to make sure I understand the issue, you installed NCM on your NPM server and now you have two Syslog Servers? If that's the case, you might try stopping the NCM Syslog Server and then try restarting your NPM Syslog Server. It may be an issue with port conflict.

chris.lapoint

I've confirmed with dev that the NCM installer logic is as follows:

When Orion NPM is already installed on the machine and the Syslog service running we do not install NCM Syslog service.
When Orion NPM is already installed on the machine but the Syslog service is not running – we install NCM Syslog service.

So, we believe that it might have been scenario 2 that caused your issue. To fix this, you'll need to stop NCM Syslog service (make sure it is not Automatic start) and start the Orion NPM Syslog service. You only need 1 Syslog Server for both NPM and NCM.

fluxeon

I have had no issues with the installation, what so ever. Both packages ran smoothly and was running up within say 20mins.

Some minor tweaks and off and running again.

Had to change the timeout page () and re-baseline and d/l configs to set the pie charts correctly (

) but these where minor things and really nothing to do with the install.

Overall I had a very pleasant experiance with install the new NCM and have been enjoying the new interface and look.

-James

BryanBecker

I upgraded last night....my 2 issues :

1. Everytime I click on Network Configuration Manager link on the Orion web site I get prompted for login. I select 'Windows Account' and click on remember settings. But everything I do this I get prompted. I just want to get passed thru after the 1st time. Any ideas?

2. I posted this on another thread...I have 2 NCM servers and 1 Orion site. You can't added a second NCM server in Orion. So half of my devices are not seen.

BB

chris.lapoint

1. Everytime I click on Network Configuration Manager link on the Orion web site I get prompted for login. I select 'Windows Account' and click on remember settings. But everything I do this I get prompted. I just want to get passed thru after the 1st time. Any ideas?

By prompted, do you mean you have to click the "login" button? Or are you saying you have to select "Windows Account" again and remember settings?

Also, can you confirm that you have cookies enabled?

BryanBecker

It was a cookie issue...not sure why it wasn't enabled for a local site. It appears to be ok now.

justinh

I finally got the upgrade installed. It took several days because of a snafu on my part installing SQL 2005. I had been running SQL Server 2000, but didn't know I had to upgrade until I was running through the NCM config wizard. Then I ended up leaving a default option checked that I shouldn't have (because I'm really not a DB person - just a hack), which kept the SQL install from completing. Eventually, I just uninstalled SQL Server completely, reinstalled, finally figured out I had to run the configuration wizard before I could add it to the Database Manager, eventually got the database detached so I could import my pre-install-backup, and finally ran through the configuration wizard again to upgrade the database.

I'm not sure I want to try getting the integration set up, quite yet. At least not until I recover from the upgrade!

savell

Performed the v5 upgrade today without any issues at all - great job by the developers! We have a large number of scheduled jobs, scipts and policy reports, so I was a little concerned at the migration.

Have left the Orion intergration module for now - just waiting on the service pack to address the Orion v9 SP2 and NCM issue that is floating around.

I have posted a few enhancement type posts in other threads concerning the web page contents - but Solarwinds have created a fantastic web based platform extension for NCM.

Dave.

Edit: The upgrade comment above by Justin concerning a required SQL2005 upgrade only refers to the Express Edition - we are still running SQL 2000 Standard (at least for a few more weeks) which is still supported by NCM.

chris.lapoint

Thanks for the post. We're glad to hear your upgrade went well. Wrt/ Orion NPM 9.0 SP2 and NCM integration issue, this has been resolved. Please go to your customer support portal and redownload the NCM 5.0 bits. You will notice that there is a readme that describes the newer version of the NCM integration module installer included in the zip.

NOTE: If you have already installed the NCM integration module on your Orion NPM 9.0 SP2, you must reinstall SP2 to fix the problem.

bcjordo

I upgraded to NCM yesterday and the upgrade was fairly uneventful. The one thing I did find is that my sql password caused the configuration to puke because it has an "&" in it. I changed the password and all worked great.

The one thing I am noticing is that my CPU utilization has greatly increased. It really has slowed down the performance of the website. My implementation is in a virtual machine (vmware esx) with a single cpu assigned. It is regularly peaked at 100% because of the netperfmon service. I didn't know if anyone else has seen this.

I'm running Orion 9.0 SP1, NCM 5.0 and Engineers Toolset on the same box. The SQL server is a 2005 sql server standard box also running as a virtual machine. This configuration has not given me any issues until this upgrade. Any thoughts?

justinh

Edit: The upgrade comment above by Justin concerning a required SQL2005 upgrade only refers to the Express Edition - we are still running SQL 2000 Standard (at least for a few more weeks) which is still supported by NCM.

Fair enough. Thanks for clarifying that. It's still a little disconcerting that I didn't find out during the install rather than when I was trying to run the config wizard.

ceclark

My upgrade puked

I opened a TS ticket (9/29) and I heard back today that I'm S.O.L. until the first Service Pack is released (which may resolve my problem).

ShamChauthani

ceclark,

What is the TS ticket number for the issue you submitted. I will follow up with the TS rep.

Thanks

chris.lapoint

Would you mind elaborating on the exact problems you encountered? If this is something others reading this post might encounter, it might save them some headache. Also, I'd like to confirm your issue is resolved in SP1.

ceclark

During the upgrade I receive the following error-

"Error while executing script - There are no matching rows on which to report."

A screenshot of the error is available in the ticket, number 61083.

chris.lapoint

This is fixed in SP1 which you should be receiving soon.