Hi All,
This simple thing is still haunting me and no one seems to know the answer.
What is the difference between Local and Running Configuration. Working with Cisco device for more than 2 decades, I know what a running-configuration is. This is the configuration that the router is currently running. But the confusion is on the Local Configuration.
People thing the "Local configuration" is the configuration built by vManage using the Templates or Configuration Group. But my tests show differently.
If I make a change in CLI (say system-ip), then I see the system-ip updated on both running and local configs. Running-config is fine, but how come vManage updates the local config when CLI changes are made? As per my understanding, Local config is the config generated by vManage the last time the template/CG was deployed. But my tests show the other way. Also, different parameters behave differently. site-id changes go out of sync, but system-ip change syncs with both the configs. I am unable to come to a conclusion.
Also, while applying Policy or Configuration Groups, vManage shows two configurations, Local Configuration and New Configuration. Sometimes it is "Old Configuration and New Configuration". See attached screenshots.
Why Cisco engineers are not able to make things more consistent and make it easier for the customers to understand!
I would appreciate if any one can clarify what the "Local Configuration" really mean.
Thanks,
Mohan
View more