Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > Downloading Context from devices as of NCM 7.4.x

Downloading Context from devices as of NCM 7.4.x

Table of contents

Updated: September 21, 2016


In previous versions of NCM, although it was possible to download multiple contexts in NCM, the startup config was usually sacrificed because of the switches and where the config type was identified. In NCM Version 7.4.x, a new process has been developed.


  • NCM, all supported versions



In NCM 7.4.x, a new template command was introduced which allows logic to get context as well as the startup config from the Admin context.

NOTE: Only the Running and Startup Configs can be gathered from the context NCM initially logs into (normally the Admin context). After changing to a different context, it will be an either or, based on the command on the context line in the Device Template.


This is an example of the template that would enable NCM to get the Running (admin context) Config, Startup Config, and the System Context Config:


<!--SolarWinds Network Management Tools-->

<!--Copyright 2007 SolarWinds.Net All rights reserved-->

<!--Modified by bc 9/16/2016-->

<Configuration-Management Device="Cisco ASA Context" SystemOID="">


                  <Command Name="Reset" Value="terminal pager 0"/>

                   <Command Name="system" Value="changeto system${CRLF}show run"/>

                 <Command Name="Startup" Value="show start"/>

                   <Command Name="Running" Value="show run"/>

                   <Command Name="DownloadConfig" Value="${ConfigType}" RegEx="#"/>

                 <Command Name="UseMultipleDownloadCommands" Value="True"/>

                   <Command Name="Reboot" Value="reload noconfirm"/>

                   <Command Name="EnterConfigMode" Value="config terminal"/>

                   <Command Name="ExitConfigMode" Value="end"/>

                   <Command Name="EraseConfig" Value="write erase${CRLF}Yes"/>

                   <Command Name="SaveConfig" Value="write memory"/>

                   <Command Name="Version" Value="show version"/>




The process to set up NCM:

1. Go to NCM Settings > Configs. 

2. Add a new Config Type for each context.

3. Create the Config Type in the Device Template as well as the command needed to download the config as listed above.

The key commands in this Template making is different:

<Command Name="Reset" Value="terminal pager 0"/>

<Command Name="UseMultipleDownloadCommands" Value="True"/>

<Command Name="DownloadConfig" Value="${ConfigType}" RegEx="#"/>

<Command Name="system" Value="changeto context system${CRLF}show run"/>

<Command Name="Startup" Value="show start"/>

<Command Name="Running" Value="show run"/>



NCM logic when downloading the system context:

Log in to the device as one has set up in NCM Device settings. Provided the settings are correct, NCM upon logging in will be at the Enable Prompt.

NCM will recognize the Enable Prompt and logic is flagged as OK to issue a command.

The first command NCM will try to issue is the command identified in the “Reset” Command Line. This is designed to enter a command to turn off paging to prevent blank lines in the config (terminal pager 0/terminal length 0 …)

Once this command is issued, the device returns back the prompt, and NCM is ready to process the next command if any.

In this example, a user has selected to download the system config type for the Web Console.

NCM is set up to use SSH to request and transfer the configs.

NCM will then use the line and use the defined Value: <Command Name="DownloadConfig" Value="${ConfigType}" RegEx="#"/>

  • ${ConfigType} (system was selected as the configtype by the user) is defined in the Command line: <Command Name="system" Value="changeto context system${CRLF}show run"/>
  • Since the prompt is going to change based on the context for these, we have to tell NCM to only consider the # when looking for the Prompt at this point as opposed to the original prompt and this is the Reason for the RegEx="#"
  • End result of the command is “changeto context system [ENTER] show run”


The same process will be done for the running, startup, or any other context created and identified in the device template.


This logic or process can also be modified to be used for other devices that have sub configs in a text format such as Nexus and ACE devices.




Last modified