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

Device Credentials Disappear from DB !

Odd issue I have been having on the last four devices I have added to NCM.

We import our devices into NCM from NPM via the scheduled job in NCM.

All looks fine, I ensure the device credentials are in place, I am able to download copies of the configurations.

But the next day, the device credentials are no longer stored in NCM.

I thought I was going crazy, but looking at the database indeed the credentials are no longer there for each of the four new devices.

I can add them back in, download configurations, and they again disappear the next day.

Anybody else seen similiar behavior?

Regards,

Bob

We are running:

SolarWinds Orion Core 2011.1.0 SP1, NCM 6.1, NPM 10.1.2 SP1

Find more posts tagged with

Accepted answers

reheindel

Verified that my credentials were still intact this morning, so indeed the "Import" job configuration appears to have been the problem.

I'm happy now!

Regards,

Bob

All comments

fcaron

This does not ring a bell (but will ask for more and will post here if I find anything).

I suggest you open a case.

fcaron

Nothing obvious on our side. I recommend opening a case.

MarieB

reheidel--

When you open a support ticket, could you:

--Reference this thread to Support.
--Post back here with a case number.
--Post any solutions you get from Support.

Many thx,

reheindel

I think I might be onto the problem.

I believe the issue is found in the "Import devices from NPM" job.

Looking at the merge wizard, you can pick and choose which columns to merge, and which to ignore.

It looks like it is configured to merge the credentials fields, which are null for the devices in NPM (at least for username/password/enable password), so maybe they are getting set to null in the NCM database as a result of the merge process.

I am going to modify the job to ignore those columns, and see if that fixes the issue.

I will report back my findings.

Regards,

Bob

reheindel

Verified that my credentials were still intact this morning, so indeed the "Import" job configuration appears to have been the problem.

I'm happy now!

Regards,

Bob