07-26-2012 01:13 AM - edited 03-10-2019 07:20 PM
Is there a built-in mechansim for revision control in Cisco ISE? If not built-in, then what is the other way? I have been trying to look for documentation online but didn't find any.
Just to explain what I am looking for:
-----------------------------------------
A way to properly manage all the configuration changes to ISE node. Changes are usually identified by a number or letter code, termed the "revision number". For example, an initial set of files is "revision 1". When the first change is made, the resulting set is "revision 2", and so on. Each revision is associated with a timestamp and the person making the change. Revisions can be compared, restored, and with some types of files, merged.
----------------------------------------
I ask this because "show run" output in ISE CLI does not give all the configuration details. How can we maintain the history of configurations?
PS: I rate useful posts
Thanks,
Kashish
07-26-2012 01:48 AM
Can any security expert help me with this?
07-26-2012 07:18 AM
There is not a way to track which version a specific ISE configuration is on. The ADE-OS configuration, or cli configuration typically is static once the repositories, dns info...etc is all set and done. For the application database you can setup a timer where an automatic backup is generated, from there you can manage what dates a backup is good for.
Thanks,
Tarik Admani
*Please rate helpful posts*
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