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

NodeID went splat

I just added a new node to NPM, and it overwrote an existing node. It's not a case of a duplicate IP (though I haven't gone back very far to confirm that the older device never used that IP). Fortunately, the device in question doesn't have customer connections, so no harm done in regards to billing this time. The only time I've ever seen this happen before is if I try to add a node by IP that is already being monitored. Is this something that's been known to happen, or did I just get "lucky"?

Find more posts tagged with

Accepted answers

cgregors

I've also seen it happen. It seems to occur when I am using the add-a-node web IF. If the hostname is already populated when I bring up the screen, I know it is going to cause a problem.

When that happens, I do one of the following: clear the cache in the orion web, restart my browser or add the node via the console.

Chris.

All comments

cgregors

I've also seen it happen. It seems to occur when I am using the add-a-node web IF. If the hostname is already populated when I bring up the screen, I know it is going to cause a problem.

When that happens, I do one of the following: clear the cache in the orion web, restart my browser or add the node via the console.

Chris.

justinh

That's unfortunate if it's truly just a crazy caching bug. This has the potential to be a data loss bug, which should be verified and squashed ASAP.

Miron

Hi,

I have experienced the same issue, which when it first happened caused me concern as to why one of my main devices suddenly disappeared.

Miron

epenney

I believe we were just the victim of this same issue (we are running NPM v10 SP1). Our most important, largest node just vanished - we believe this happened when a completely unrelated node was being added, looked fishy, so deleted newly added fishy node. In the process - it wiped out a very important node with years of history with it. RESTORE - DANG.

hez

We've experienced the same at least three times. You know something is really wrong when the Cisco 871 has 300Mbit on Gi0/1

I guess we all should open cases on this..