Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > How to use NCM to make config changes on multiple nodes

How to use NCM to make config changes on multiple nodes

Table of contents
Created by Allain M Umalin, last modified by Alexis Pasao on Nov 21, 2018

Views: 11,677 Votes: 3 Revisions: 9

Updated November 21, 2018


How to use NCM to push a config change to a device or multiple devices


  • NCM 7.4
  • NCM 7.3.2
  • The commands being issued need to be valid commands on the target devices


1. Log in to the NCM Web console.
2. In CONFIGS tab, click Configuration Management.
3. Select the preferred nodes and then click Execute Script.execute_scripts.png
4. Type the script on the right pane and then click Execute.

Note: Click Load Script from file on the right pane if you already have the script saved.


If this is a command to be issued frequently one should save the script



These command in the Execute Command Script will mimic making a change via putty

for example:

NCM logic will get you as far as the Enable prompt after a login if set up correctly

at this point, if you are making a change, likely you will need to enter into a configuration mode.

Below is a demonstration of removing a username from a Cisco IOS device and then explain what NCM is actually doing

conf t

no username bill



At the end of each line NCM is going to send a ${CRLF} to enter

so it looks like this:

conf t[ENTER]

no username bill[ENTER]




Often one will add spaces between commands.  NCM does not ignore this line, it will send an ${CRLF}. In some cases depending on what commands are being issued, the extra ${CRLF} is not desired. Maybe I entered a command and the device sent me a question back.  the default return may not be the desired answer you wanted to send

Same command as above but thereis a clank line in the command set I wrote

conf t

no username bill




NCM does:

conf t[ENTER]

no username bill[ENTER]



Not a big deal in this example but could cause overhead or could result in devices giving an error and disconnecting

Rule of thumb -- Avoid extra spaces, indents, blank lines.

If you do want to send an carriage return line feed, go ahead and use a ${CRLF} as opposed to the blank line



Last modified