Cisco LMS 3.2 Problem with "Configuration Last Archived Time".

Michelle Bammel · ‎07-22-2010

For the past two months our CiscoWorks appeared to be completing the daily sync archive job but if I open a record from Device Center for a device that was shown as "successful" collection status for Config Archive the Device Center record shows an incorrect date. In fact, most of the device records show the same last date for "Configuration Last Archived Time" and the date shown remains the same (about 3 months ago). This date does not change on the Device Center record even though the Config Archive status in RME shows "successful" for the majority of our systems on a daily basis.

If I attempted to perform a manual archive sync from the device record the job fails with the message "Unable to get results of job exsecution for device. Retry the job after increasing the job result wait time using the option:Resource Manager Essentials->Admin->Config Mgmt->Archive Mgmt->Fetch Settings.

This worked with very few problems for over 700 devices until about 3 months ago. Any ideas what may be causing this issue?

Joe Clarke · ‎07-24-2010

First, RME will only update the date of a config if it archives the config. Even though a config archive job may complete successfully, the configuration may not be archived. To avoid archive churn, RME will first compare the config it downloads with the current version in the archive. If they are the same, then RME will not archive the new config, and thus the date will not change. Therefore, if your network is stable, and you are not changing configurations, then RME will not continue to update the config archive date.

As for the error you're seeing, that could be a known bug with ConfigMgmtServer locking up due to interactions with OpenSSH devices (typically WLCs). You can try restarting ConfigMgmtServer, then archive the config again:

pdterm ConfigMgmtServer

pdexec ConfigMgmtServer

Michelle Bammel · ‎07-27-2010

After some additional troubleshooting we determined that the issue was due to the device updates not being applied. The system administrator had thought these were selected to be applied automatically but when we checked device updates against the cisco.com site we found that were several updates available to include a few for a new type of switch we had added to our environment. Once the updates were applied the Inventory jobs and archive collection jobs ran correctly.