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

Please create an NCM feature that automatically adds nodes to scheduled NCM Jobs

Please create an NCM feature that automatically adds nodes to scheduled NCM Jobs

Update May 22, 2020:   This Feature Request is no longer needed, and here's why:

 

You can automatically add every node to any job through simple use of the dynamic selection tool.  There's no need to bump this idea--the solution is already present.

Every job has the ability to define which nodes should be part of that job, and you could list them all manually and specifically, or say "perform the job on any Node with these characteristics (and include your logic, like Vendor = Juniper, or Node Name Contains "SW").  

Let's say you have all your Cisco switches & routers & firewalls added to a job manually, like I used to do.  Each time a new node would be added to the network, I was forced to open every job and manually add the new node(s) to that job.  

That's not necessary if you use the dynamic node selection option instead of manually adding individual nodes.

Now my jobs use selection logic that says, in effect, "Run this job on any node that has vendor = Cisco".  It means that every time a new Cisco node is added, the job automatically includes it in the run.

This has saved me and my team countless hours of tedious manually adding nodes to jobs.  Now we don't have to add nodes to ANY jobs, thanks to the dynamic selection tool.

I applied this logic to NCM rules that do daily inventory of nodes, that back up start up & running configs, perform config change reports, and more.  If you're manually adding nodes to job on an individual basis, learn from my happy work and just use the dynamic selection tool to tell the job which nodes to include.

 

Swift Packets!

 

Rick Schroeder

 

==================================

Original feature request is here:

 

 

Each time we add a new node to our network, we must manually add the new node to NPM, and then manually add it to NCM, and then manually open up six NCM Jobs and add the node to each job.

 

It would be great to have a Dynamic Node Selector-to-Job solution that would automatically add a node to the NCM Jobs.

 

I don't mind having to manually add a node to NPM and NCM, but adding it to NCM Jobs seems like a task that could be automated, or at least simplified.

 

pastedImage_0.png

 

Some ideas that would at lest simplify the task might include:

  • As each node is manually added to NCM, the same area of NCM that contains the credentials to log into the device could have drop downs or radio buttons for every NCM Job.  I'd be happy to see that, and then simply click each Job's radio button to add the node to each job manually, rather than having to edit each job, click through the screens, add the node(s), click through more screens, and Save the Job.
  • A dynamic selector might let me say that if a new node is a switch or router, add it to the NCM Jobs that contain the word Daily or Nightly or Weekly or Fred.  If the Job is a server or UPS, provide other options to consider or select from drop downs.
5 Comments
Level 12

Agreed this would be most helpful.

Level 7

Custom, dynamic Groups in NCM would be really helpful. Actually could be a deal-breaker in my current evaluation.

We need to be able to specify node and/or configuration variables to search for, and have NCM run a job every night to update custom groups based on those searches. Then be able to schedule command scripts/templates to run against those groups on a recurring schedule.

At least let NCM utilize NPM groups.

I finally dug a little bit into the custom options and discovered NCM can automatically add all new nodes to all appropriate jobs.  There's no longer any extra steps required on my team's part--just add a node and NCM will automatically back up its startup & running configs, archive files, inventory it, write memory automatically every day--everything.

I just needed to get up to speed with the abilities of NCM's later releases.  Not so easy when I learned NCM in 2004 and have been only slowly updating my brain with new capabilities.

Thanks go to all who suggested this could be done with dynamic selection of tools.  They were right!

PM me if you need to see screen shots of how I got it all automated.  It's ridiculously simple and easy.

Level 16

Bump

@sja  Please see my previous comment that this is already available through simple use of the dynamic selection tool.  No more need to bump it--it's here.

In short, every job has the ability to define which nodes should be part of that job.  Let's say you have all your Cisco switches & routers & firewalls added to a job manually, like I used to do.  Each time a new node would be added to the network, I was forced to open every job and manually add it to that job.  

That's not necessary if you use the dynamic node selection option instead of manually adding individual nodes.

Now my jobs use selection logic that says, in effect, "Run this job on any node that has vendor = Cisco".  Now, every time a new Cisco node is added, the job automatically includes it in the run.

This has saved me and my team countless hours of tedious manually adding nodes to jobs.  Now we don't have to add nodes to ANY jobs, thanks to the dynamic selection tool.

 

Swift packets!