cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post

Automatically Manage Node with NCM

Automatically Manage Node with NCM

Since the merger of NPM and NCM databases, it is no longer possible to automatically import nodes to NCM as a job.

Instead, the importing of nodes is now leveraged on the ability to perform a network scan with CLI credentials included (CLI credentials will be tested on the scanned nodes).

A node is only automatically added to NCM if the logging in to the node during discovery is successfull.

The issue with this is that not all Orion setups can or may scan their networks.

This leaves us with only one other option and that is to Enable NCM License on the nodes manually.

So, if a person adding a node forgets to add it to NCM as well, or doesn't have the required privileges to do so, then the node will never be added since it has been forgotten.

This issue is discussed in detail here: Re: Importing Nodes to NCM v7.4 Automatically

18 Comments

Still not possible in NCM 7.9

Bump.

Try it now...

Still not possible in NCM 8.0

NB: Orion NCM 7.3 was released on the 27th of May 2014. 5 Years ago...

It's more work, but after adding or discovering nodes for NPM, it's easy to select them all and apply NCM to them all at once.

I know, not what you asked for.  But it's the method I use.

8 releases later.

Still not possible in NCM 2019.4

Wonder if this feature will ever be brought back.

It sure would be nice to have some official feedback from swi on this!

jreves​ ?

This is "conditionally" a good Feature Request, in my humble opinion, from the point of view of automatically adding all NPM nodes to NCM.  That's a labor saver and a no-brainer. 

pastedImage_8.png

But it's not a "perfect" Feature Request because some of my nodes (particularly Meraki VPN/firewall devices, but also Cisco ACI hardware, and other systems) cannot be monitored with NCM.  They aren't compatible, don't have a flat file to download/backup/restore/compare/manage.  While I WISH they WERE compatible, I don't need failed jobs or more things that need my administrative attention to disable them in NCM when they need not be backed up by NCM.

So we still need to manually select the drop-down to Manage the node with NCM.  But it doesn't have to be done one at a time.  You can go to Admin > Node Management > Manage Nodes, select your nodes by some group (vendor, machine type, etc.) and Edit them.  Once there, just click the "Manage with NCM" option and they're all done.

No, it's not automatic.  But it IS pretty simple.

No, it won't prevent you from having to manually enable this on all (or individual) nodes every time you add more nodes.

But, once this option is enabled, I discovered how easy it is to automatically back up every new node by adding it to a Job special selection.  Using this process has eliminated all the cases of someone on my team adding a new node to NPM and forgetting to add it to NCM. 

Here's how this works:

  1. Create a new scheduled NCM backup job

pastedImage_5.png

2. Use the Dynamic Selection option to choose which devices to backup.  It's easy if ALL your devices are compatible with the backup, but it's also pretty easy to select (or NOT select) groups of devices based on Vendor, Node ID, etc.  Use this and you're going to get all you wish for, and nothing you don't.

pastedImage_6.png

3. Enter the Notification Details (e-mail contact info, subject, "only e-mail results if the job encounters an error", etc.)

4. Choose what to backup, and what content requires notification.

pastedImage_7.png

5.  Save it, apply it, click Finish.

With just that one job you're automatically backing up all nodes with NCM.

BUT . . . .       This only ensures your nodes that have NCM enabled are included with the Backup Jobs you build.  It's a great time-saver that way, but this still does not automatically go into each Node's Properties and select "Manage node with NCM".

Plus 1 on this Feature Request, and let's keep bumping it to make it happen.

Hi rschroeder

Thanks for the suggestion but this doesn't come anywhere close to what is required. I feel I need to make an added point about the importance of this issue.

When I made the case for this issue and feature request 5 years ago here: Re: Importing Nodes to NCM v7.4 Automatically , I pointed out that this is a critical feature that needs to be present for larger networks. We added a thousand new devices to NCM, manually, a year after the post was submitted.

superfly99.png

We have since then added another 2 thousand odd nodes to NCM, manually.

This could be done automatically by using the dynamic selection that would be made available in the NCM job. That way you can avoid licensing nodes to NCM automatically based on vendor/machine type/other. IF a config backup were to fail then the job would be able to send out an email notification to the person responsible and more importantly, to the person that has enough permissions in NCM to rectify the issues.

As for adding all nodes to NCM then selectively downloading configs for the ones that matter (if I understand the suggestion correcty), I'm afraid this will cause more problems for those that don't have unlimited NCM licenses. Forget about the fact that adding nodes to NCM would still be a manual task, adding more nodes to NCM than yur licens permits will break the process.

The way I see it, the only thing that can be done to solve this problem is to bring back the import job type.

Thanks for your vote!