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

Importing Nodes into NCM

I am running NPM v 10.0.0 SP1 and NCM 5.5.2. I cannot find a way of importing the nodes contained in NPM into NCM. Is there a way to do this or to manually add nodes? I can't find any import applet etc to do this.

Find more posts tagged with

Accepted answers

borgan

There is a default job for doing this already in NCM. Open the NCM console on the server, go to Schedule-->Create New Job. Select the Import Devices from Orion Database option and proceed to edit using the wizard.

Let us know if you need any specific help setting this up.

All comments

borgan

Let us know if you need any specific help setting this up.

snauzer

Thanks for that, however, when I log into the NCM console on the server as Administrator, I cannot see "Schedule" anywhere.

borgan

You're not logging into the NCM web console are you? I'm talking about the NCM console on the application server. There you will see the Schedule menu in the tool bar.

snauzer

Hi, I cannot see any other console (see below) - is it on the Start menu ?

jsirrett

Great feature to schedule the job and import from NPM, was going to ask for this feature!

Just started to set it up and it appears you cannot run a selection criteria on the nodes imported, there are many nodes in our NPM database that we do not backup through choice or technical limitations. It would be great to filter these out.

Also we have customers who have access to the NPM data and the central team have to then input NCM data for them due to technical security issue's around different customers data.

I'd hoped to add a Custom Field along the lines of "Backup_Device" with an integer of either 1 or 0, as a backup do not back up rule that I could use on the selection criteria to save importing nodes we never backup.

(Side note - Just realised I can import that field and change the backup schedule to only backup devices with that field set! But it would be nice not to clutter the NCM database with devices that we are never going to backup.)

savell

Here is the solution I came up with to deal with a selection criteria on the Import Nodes job..

I added it as a feature request (i.e. allow node selection via an SQL statement within the import job) - but this has been doing the job for us for some time now.

Dave.