NCM using incorrect SaveConfig command

I need to schedule a nightly job that save the running config for our Cisco gear. Our firewalls and most switches support "write memory". However, I have some newer Cisco switches running NX-OS that only support "copy running-config startup-config". I scheduled a nightly job to execute the following script:

${SaveConfig}

exit

I figured it would adjust the command accordingly based on the device, but the job's email results indicated that NCM is executing "write memory" on my NX-OS devices, thus failing to save the config. The template's OID exactly matches the OID of the NX-OS devices. In this template, the SaveConfig command is correct:

<Command Name="SaveConfig" Value="copy running startup"/>

I even explicitly set the devices to use this command template instead of auto determine. NCM still executes "write memory". Does anyone know what is going on here?

Find more posts tagged with

Accepted answers

cvachovecj

This is a bug in NCM; for internal folks: FB188310.

Regards,

Jiri

All comments

cvachovecj

Hi,

Could you please post the whole template you are using?

Regards,

Jiri

rjordan

The template is below. I did some more testing and here is what I found. When executing a script on multiple devices, NCM will substitute the variables from device template of the first device it connects to. I confirmed this by selecting different sets of nodes through the schedule task. When a NX-OS device was the first in the list, NCM would run "copy run start" on all other devices. If a IOS switch or ASA firewall was the first in the list, it would run "write memory" on all devices.

Am I not doing this right? I guess I can setup a separate task just for my NX-OS devices, but this becomes a slippery slope. What happens when I have 20 different devices? I would need to have 20 separate tasks assuming they have different SaveConfig commands. To me, this behavior defeats the purpose of having variables in the command templates.

<Configuration-Management Device="Cisco 5548 NX-OS" SystemOID="1.3.6.1.4.1.9.12.3.1.3.1084">

<Commands>

<Command Name="RESET" Value="terminal width 0${CRLF}terminal length 0"/>

<Command Name="Reboot" Value="reload${CRLF}y${CRLF}y"/>

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

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

<Command Name="Startup" Value="startup-config"/>

<Command Name="Running" Value="running-config"/>

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

<Command Name="UploadConfig" Value="${EnterConfigMode}${CRLF}${ConfigText}${CRLF}${ExitConfigMode}"/>

<Command Name="DownloadConfigIndirect" Value="copy ${ConfigType} ${TransferProtocol}://${StorageAddress}/${StorageFilename} vrf management${CRLF}${CRLF}${CRLF}"/>

<Command Name="UploadConfigIndirect" Value="copy ${TransferProtocol}://${StorageAddress}/${StorageFilename} ${ConfigType}${CRLF}${CRLF}"/>

<Command Name="UploadConfigIndirectSCP" Value="copy ${TransferProtocol}://${SCPServerUserName}@${SCPStorageAddress}/${StorageFilename} ${ConfigType}${CRLF}${CRLF}${SCPServerPassword}"/>

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

<Command Name="SaveConfig" Value="copy running startup"/>

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

</Commands>

</Configuration-Management>

cvachovecj

Hi ">rjordan,

I quickly consulted the problem with engineering and they advise to open a support ticket -- you have active maintenance, I checked it.

Please attach a copy of your DeviceTemplates folder and list all systemOIDs of devices that were included in your tests.

Regards,

Jiri

rdbaker31

This is interesting to see. I discovered today that I am experiencing the exact same issue as well and would be very interested to hear what the resolution is. For information I found the issue when testing on a Cisco 7200 Series router running IOS Version 12.4(25c). If you 'test' (within scheduler, right click the job, select 'test') the scheduled job that uses the 'copy run start' command from within the scheduler it works fine. However if you 'run' the scheduled job (within scheduler, right click the job, select 'start') it doesn't. HTH.

Regards

SolarWinds products currently in use on the same server; Orion Core 2012.1.1, NCM 7.1, NPM 10.3.1, IVIM 1.3.0, VNQM 4.0.

cgaller

You can create an alias in NX-OS for the write command. One of the first things I do when I setup a NX-OS device. Use 'cli alias name write copy running startup' in configuration mode and that should be a work around.