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

NCM NPM "SYNC" issues

HI all,

After upgrading to NCM v7, we have a couple of "new" npm nodes, due to the fact that the nodes in NPM/NCM wasn't entered with the same IP. Anybody managed to move the NCM information from the "new" NPM node to the old NPM node?

(I've serveral years of history both on the NPM and NCM nodes, so would prefere not to delete any history, just move the releationship between the NCM history over to the real NPM node.)

Tx in advance for any hints

/heZ

Find more posts tagged with

Accepted answers

All comments

fcaron

Hi Hez,

We are thinking about ways to detect and handle duplicate nodes during the sync (same nodes managed by NPM and NCM via diff IP before the first sync) - (101576)

For now, the recommended procedure is to "manually" decide which one to keep. We don't of any procedure to connect the history of the one that will be deleted to the one that will remain (to avoid loss of history). I'll double check this last point.

rcahill

Post NPM 10.2 and NCM 7.0.1 integration still working on your situation also. We now have the same device and ip address under monitoring.

I don't know if the history is more important or the linked config data. For our industry the linked config data is regulated by our State.