Ways to edit network configs

Edit configs to streamline complex configuration changes and make bulk changes to multiple nodes. To edit a config, you can manually run a script against a node or use a config change template. Read below about the differences between using a script and a template to decide which method is right for your task. The troubleshooting and remediation section provides an example of a config change that had a major impact on a network and how a system administrator used tools to discover and remedy the problem.


Executing a command script is the most effective way to make a change to a device or group of devices if you already know which components of the device configuration need to be changed. Users who write scripts must know command line interface (CLI). Commands include arguments and logical operations needed to produce a set of CLI commands and execute those commands against each NCM node targeted for a specific config change.

Several tasks can be automated with command scripts. For example:

  • Download configuration files
  • Upload configuration files
  • Upload IOS images
  • Update login banners
  • Update access control lists (ACLs)

Ready to create a script?


Config change templates include programming language that enable you to create sophisticated config change routines without writing a script. This method removes the chance of incorrect script syntax creating network errors. Change templates use variables based on custom properties and data from the NCM inventory to make a change to a device. You only need to know the variable information of the node that is being changed.

Examples of tasks that can be completed using a template:

  • Change VLAN membership by device port
  • Configure device interfaces based on description
  • Enable IPSLA for VOIP implementations
  • Manage a NetFlow collection at the source device

You can either use a config change template provided with NCM out-of-the-box, import a template from THWACK, or create your own.

The framework for creating config change templates depends on the SolarWinds Information Service (SWIS). SWIS is an API that is installed with NCM and interacts with inventory data in the Orion Platform database. Any device that is not inventoried in NCM cannot be targeted with a config change template. Each object in a device inventory is a SWIS entity that can be referenced in specific ways within scripts.

Ready to run a template?