RME will trigger a collection for both startup and running config based on various criteria that is detected via syslog and if changes are made. Table 15-1 and 15-2 have a list of messages that will trigger an inventory collection and config fetch operation.
Table 15-1 and 15-2 list of messages that trigger collection and fetch of configuration:
Startup configs are only collected when selected during the archive job otherwise, its just the running config that gets archived. In the users guide for RME 4.3, there is a section called "How Running Configuration is Archived" which is a workflow how archiving works.
Hi Lothar, The out-of-sync report is a really good feature but I would say it only shows potential out-of sync devices. As Nael said and Joe pointed out in this thread (https://supportforums.cisco.com/message/651200#651200) RME collects both running and start-up when triggerd by a syslog message. The crucial point is the timeline of the process that detects the out-of-sync. If you leave the config modus of an IOS device, the syslog message will be generated immediately and the config will be collected usually in the next minute. But when are you typing the "wr mem" ? So it could be, that RME is faster then you and gets both running and start-up config archived before you have saved the current changes - whith results in "false" positives, i.e. the archived startup is not in sync with the latest archived running.
You have mad your changes and when you logout of the device some minutes after the change you usually issue the "wr mem". Which will sync running and startup - but RME does not see this and has yet marked the device as being out-of-sync. The problem is, that "wr mem" or "copy running start" does not generate a syslog message which could trigger the collection in RME..
Config Change Polling would be the automatic feature of RME that should delete these false positives, as it looks at both, the running and the startup-config (RME > Admin > Config Mgmt > Archive Mgmt > Collection Settings)
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 custome...