Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

CPI2.x Configuration Management and avoiding out-of-sync configs

Hi,

I did'nt found an option to can save the configs after deployment as in LMS neither as a global setting nor as a deployment task setting.

Aside letting changes unsaved is not a good network operation practice, it bring the configs in out-of-sync state at the archive.

Also "System Settings => Inventory => Enable Syslog and Traps on device" does not save the configs and bring everything into out-of-sync state in the archive.

Q1: Is it necessary to write this to all your templates, if you need to globaly enable "config save after deployment" with a "nice" scaleability?

#MODE_ENABLE

write memory

#MODE_END_ENABLE

Q2: Why are system CLI templates copy&paste protected in its content?

thx for answers,

Steffen

167
Views
0
Helpful
0
Replies
CreatePlease login to create content