Processing order - custom XML for ASA multi-context backups

FormerMember

Hi,

Apologies, another topic here for custom XML/device templates for backing up configs from an ASA running in multi-context mode. 

I have no issue finding posts detailing the commands and values for entering into a custom XML script, but what isn't documented anywhere it seems, is how the device processes the XML? There is a similar post below asking the same question:

ttps://thwack.solarwinds.com/product-forums/network-configuration-manager-ncm/f/forum/42298/cisco-asa-multiple-context-backup-with-ncm-7-2-2-what-has-changed

I have assigned a similar XML against a context firewall, and all that was retrieved was the config of the admin context. And yes, my context names and commands were correct. 

Surely the commands need to run in order, such as:

Change to <NAME>

Save config

Change to <NAME>

Save config

Please could anyone shed any light? This seemingly easy request is turning out to be more difficult than expected. 

Many thanks. 

bcorgey

Good morning,  

Really the best option is to add Each Context to NCM via its own IP address, but understandably this is not always possible.

If you have all of the Context names set up as custom config types, for example "Public" and then the system

and the command in the device template being used:

I use these as basics this has morphed since first created in 2012

<Commands>
<Command Name="Reset" Value="terminal pager 0"/>
<Command Name="system" Value="changeto system${CRLF}show run"/>
<Command Name="Public" Value="changeto context Public${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"/>
</Commands>

If this does still not work and you are downloading Public, but still getting the Admin context, i suggest opening a case with support.

The context name on the device should be case sensitive, so if on the device the Context is Public, and in the template, one has public, it will not change the to Public context and still in the admin context when NCM issues the show run command.

hope this helps