NCM Import Nodes from NPM

Currently have NPM and now evaluating NCM. I have noticed that when devices are discovered through Auto_Discovery that the newly added devices use the global username / password that I have configured, but devices imported from NPM do not use the global username / password settings. This is not the desired result.

The job that I have set up imports a single 0 for the fields Username, Password, Enable Level and Enable Password. I assume this is because I do not have anywhere in NPM with this configured. I attempted to set these columns as ignore in the import job, but it does not keep this setting after I save the job. When I go back into the job, those columns are no longer set to ignore. I'm not sure if this is by design or not, but don't see any reason I shouldn't be allowed to ignore these columns.

Has anyone else seen this issue? I am using the most current NPM and NCM versions.

Thanks,

Mark

Find more posts tagged with

import

orion

npm_integration

integration

npm

orion_ncm

ncm_integration

Accepted answers

markb

There is work-a-round for this if you don't want to wait for the next update. You can contact SW for it. It is a manual update to the NPM database. I applied the work-a-round and it is working as expected now.

All comments

savell

Hi Mark,

We are just setting up the same import from NPM - and have the same result.

I can't see how we force the global username / password, and also don't have the option to ignore the Username, Password etc fields.

I think we both need help here from support...

Dave.

Edit: After a little more playing around, this is turning ugly. I can't even import columns from NPM like SNMPVersion. It seems logical that we would map this to the SNMPLevel column used in NCM - but in NPM it's referenced as a numeric value (i.e. 2), while NCM requires a value like 'SNMP V2'. The Orion import process provides no intelligence within the import process to map inconsistent columns.

Between the inability to use global defaults and inconsistent mapping issues, I can't utilise the Orion import feature without manual intervention for each node.

It also means I can't map a custom property for the Node Group as a result (if I do, then I can't identify the imported nodes that require the manual changes).

Very frustrating when dealing with thousands of nodes and dozens of Node Groups.

MarieB

Howdy All--

It sounds like you should open a support ticket on this issue.

Open a support ticket here.
http://www.solarwinds.com/support/ticket
Click Submit a Technical Support Ticket
In order to receive technical support, you will need to be current on your SolarWinds maintenance. Complete the form. You will not be able to upload your Orion diagnostics, but you will receive an email back that allows you to upload diagnostics.

Also, I've marked this for the PM to review.

Thanks,

christineb

Hi all - could you send me a message with your diagnostics? I'll open a support issue for you both and make sure someone takes a look at it right away.

Thanks,

Christine

savell

Thanks for the offer Christine.

We are just heading into a long weekend here however, and I've already left (lucky for some - but why I'm still on the PC is another thing).

Will follow-up as a priority after the weekend.

Dave.

markb

Christine,

This morning I am sending diags to the SW engineer that is working with me on this. I will post with any updates from the engineer.

Thanks,

Mark

markb

This is from the SW engineer that I am working with on this issue after I sent him the diags.

Thanks…passed this on to dev. I found out yesterday that this was a bug in the system and trying to find out this morning if this fix is in the next release or if they are doing a service pack that will contain the fix.

Thanks,

Mar

markb

Update from the SW engineer

Hello, Mark. This issue is a known issue in NCM and will be fixed in a forthcoming release. The Username, Password, enablelevel, and enablepassword columns exist in the NPM database. Since these are not needed in NPM for any purposes (and will be blank in the database) the columns in the Nodes table for the above need to be dropped. Then the import should work fine.