My understanding of the idea of creating a new config type is so that NCM knows where to store the downloaded config in its repository. Am I correct in saying this? eg if it has downloaded a config from "con1" when it trys to store it in config repository it'll see that there are only 2 (default) types of config (containers?) to store it in: Running or Startup.
Also regarding the Device Template itself I have a question about how it actually works. How does NCM know in what order to execute the commands? I can see from the structure of the template it provides an instruction set however if it was to work its way down the instruction set sequentially it wouldn't make sense.
Hence I have arrived at the conclusion that there is an intelligence built into the generic download config job you can schedule in NCM that knows what commands to run and in what order but a modified or custom device template will provide NCM with the native commands it is not aware of.
How does NCM know how many contexts there is in a multi context firewall? My guess is that NCM just goes by the amount you declare in the bespoke template? If you delcare 3 contexts and name them accordingly NCM will attempt to change to each context variable that has been declared eg if your template includes
<Command Name="Context1" Value="command to switch to Context1" />
<Command Name="Context2" Value="command to switch to Context2 "/>
<Command Name="Context3" Value="command to switch to Context3 "/>
it will try to find each of these contexts and download each. Am I correct in saying this? Any help is greatly appreciated. TIA!