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

Suspend nodes only in NCM

Prior to the NPM/NCM integration, I had the ability to suspend a node in NCM, but still have it polled via NPM. I no longer seem to have that ability using NCM 7 and NPM 10. Am I missing something?

Find more posts tagged with

Accepted answers

cvachovecj

Hi bleearg13,

I consulted with our dev team and they confirmed that from NCM 7.0 on, the functionality is not there.

Regards,

Jiri

All comments

cvachovecj

Hi bleearg13,

I consulted with our dev team and they confirmed that from NCM 7.0 on, the functionality is not there.

Regards,

Jiri

JesperVestergaard

I´m seeing some nodes in NCM that are status unmanaged (leftover from prior to the upgrade) yet in NPM they are managed.

I´m not able to set the status to "managed" in NCM again, and the only cure i can see, is rto remove the node from NCM, and re-add it.

Also, i get nodes in the "Overall Devices Backed Up vs. Not Backed Up" resource that shows that config are not downloaded, yet they are unmanaged in NPN (and apparently not reflected to NCM)

Looks like this resource does not resprct the unmanaged status.

While on the subject - Nodes that change it´s name or other settings (custom prop´s) are also not reflected to NCM - This is a pain...

Brgds Jesper

bleearg13

I actually get nodes still in the NCM database after deleting them from NPM, but it appears to only occur if said nodes are Unmanaged in NPM at the time of deletion. It has not been a serious enough problem for me to open a case yet. I don't see why we can't retain the ability to unmanage nodes in NCM while keeping them managed in NPM. It seems to me to be fixable by a checkbox or something in the 'Unmanage' pop-up.

Ismo

Jiri Cvachovec wrote:
Hi bleearg13,
I consulted with our dev team and they confirmed that from NCM 7.0 on, the functionality is not there.
Regards,
Jiri

Bad thing I think. I have many servers, printers etc monitored in NPM, so not only network devices. Now they show also in NCM list, confusing me and also making "backed up vs not backed up" statistics go wrong. I can't get a REAL value from these statistics now. I have no meaning to backup them ever (and it is not even possible with your scripts), so I don't need them in NCM. You should get that unmanaged-option back or you should make backup scripts work in windows and unix servers and network printers too.

I also have unmanaged devices which were not needed to monitor because they were powered on very rarely, but backing up them sometimes was good thing. So now I cannot get them back alive (managed) ever?

cvachovecj

Ismo,

Maybe I'm getting you wrong, but why would you want to import servers, printers etc. into NCM at all?

Regards,

Jiri

bleearg13

Probably for inventory - NCM can provide information on accounts on a Windows server, for one, with the right permissions.

In my case, I have several nodes that I need monitoring for availability (Orion), but I also need to back up their configs. The problem is, there is *something* that NCM does in its daily routine that causes a problem with these devices. Over time, when enabled in NCM, they start to not respond through the CLI and have to be rebooted manually. I noticed the problem some years ago and began suspending them in NCM, but leaving them managed in Orion and hadn't had a problem with them until NCM got to version 7.

I know this is a corner case and I know it's not an NCM bug, but there are definitely cases like the previous poster who use NCM in ways that you may not have thought about. I personally don't see why it's that big of a deal to add the ability to suspend a node only in NCM - it's merely (to me) a flag in the database.

Ismo

Jiri Cvachovec wrote:
Ismo,
Maybe I'm getting you wrong, but why would you want to import servers, printers etc. into NCM at all?
Regards,
Jiri

I didn't want to do that. Those servers that has been found since last NCM/NPM update has automatically been added to NCM also. All the old servers/devices include only in NPM, not in NCM. So, I dont actually know why they are in NCM but they just are. But as said, this is bad update, if this is as NCM should work. After one year I still have those 50 swiches in NCM as today, but also 500 other devices that has nothing to do with "configuration management".

And what about the license? I only have 100 licenses to NCM and 2000 for NPM. So soon I have 2000 devices in NCM also and have to buy new license?!?