- Gold, 750 points or more
A user made a running-config change on a switch yesterday morning, and performed "copy run start". RME 4.0.x duly noticed this and retrieved the running-config. However, if I understand correctly from wrestling with a similar concern in the LMS 2.2 days, there's no such detection mechanism for the startup config. So, the startup config was not due to be retrieved until the scheduled Periodic Collection, set in my environment at midnight. But since the users look at the Startup and Running Out-of-Sync Summary every 12 hours, the scenario described above inevitably would produce false reports that are not reflecting reality. A workaround that immediately comes to mind is to schedule the Periodic Collection more often than once daily, but alas, I find that's not possible with RME 4.0.x. So, is RME 4.1 in LMS 3.0 any more flexible in this regard? Also, IIRC, there was some rather unintuitive way that RME 3.x in LMS 2.2 could be manually prompted to retrieve either the startup or running configs (RME -> Admin -> Config Mgmt -> Update Archive -> click on the blue 'Startup' or 'Running' link), is this still possible in RME 4.x, with RME -> Config Mgmt -> Sync Arhcive -> making sure "Fetch startup config" is checked?