Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Network Configuration Manager (NCM) > NCM Documentation > NCM 7.8 Administrator Guide > Config change templates > The basics of config change templates

The basics of config change templates

Table of contents
No headers
Created by Caroline Juszczak, last modified by Anthony.Rinaldi_ret on Oct 03, 2016

Views: 763 Votes: 0 Revisions: 4

A change config template enables you to accomplish a specific device configuration task for a set of NCM-managed nodes. Template describes the run-time wizard through which the user selects the NCM nodes or interfaces targeted for the change. The script behind the wizard articulates the logic of the configuration change itself.

An example of configuration change workflow is an IT manager who creates the script for a template, and other team members who use the template's wizard to perform the specific configuration changes on a set of NCM-managed nodes.

The framework for creating config change templates depends on the SolarWinds Information Service (SWIS). SWIS is an API that is installed with NCM and that interacts with inventory data in the Orion platform database. Any device that has not been 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.

Examples of routine changes you can expedite with config change templates include:

  • Changing VLAN membership by device port
  • Configuring device interfaces based on description
  • Enabling IPSLA for VOIP implementations
  • Managing NetFlow collection at the source devices

 

Last modified

Tags

Classifications

Public