11-09-2020 05:46 AM
Hi all,
I am playing around with the Velocity templates in DNA (running System ver 1.3.0.159) and it doesn't appear to copy the template changes to the startup-config on switches after deployment (switches running Gilbraltar 16.12.03 and Fuji 16.9.5)?
I was hoping to use them to deploy new NTP servers and login banners in a single deployment but if I have to run around to all devices doing a write mem afterwards then it kind of limits the scalability and purpose of using templates.
Apologies if I missed something really obvious
Thanks for your help anyone.
Solved! Go to Solution.
11-09-2020 06:39 AM
System version 1.3.0.159 corresponds to Cisco DNA Center 1.3.3.8, which does not save the configuration provisioned through a template to the startup-config. Starting with Cisco DNA Center 2.1.x, configurations pushed through templates will be saved to startup-config. We expect the first generally available release of 2.1.x to be made public later this month.
11-09-2020 06:39 AM
System version 1.3.0.159 corresponds to Cisco DNA Center 1.3.3.8, which does not save the configuration provisioned through a template to the startup-config. Starting with Cisco DNA Center 2.1.x, configurations pushed through templates will be saved to startup-config. We expect the first generally available release of 2.1.x to be made public later this month.
11-09-2020 08:16 AM - edited 11-09-2020 08:25 AM
Just to add to this, you can add the following to the end of your template to save the configuration.
#MODE_ENABLE write memory #END_MODE_ENABLE
or
do write memory
11-09-2020 08:37 AM
Thanks - both replies were extremely helpful.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide