Cisco Prime 2.1: Not writing running config after template deployment
I have noticed that Prime is not writing the running config after CLI template deployments. I deployed a changeset to over 1100 devices the other night and noticed that the configs had not been written the startup config.
I did some testing today and am using the following CLI template:
You might have already figured this out but the reason your "copy running-config startup-config" thing didn't work is because that command requires interaction whereas "write mem" does not. In order for your "copy running-config startup-config" to work, you'd have to include:
But in Cisco's world, I guess that just doesn't make any sense at all. Why use the actual interactive question when you can simply just use the first word (even though all of their examples show multi-word interactive questions). The correct syntax would then be:
#START_SARCASM Duh! It's so obvious. Why in the world would one ever think anything other than that you would simply take the first word in the interactive question and just leave it at that. I feel so stupid #ENDS_SARCASM
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...