Cisco works backup question

[Manoj Wadhwa]

Hi Friends,

I have a question regarding Cisco works. The Cisco works runs automatic backup everyweek. There are quite a few devices that show up as "partially successful" with the below message. Recently we wanted the latest running config of one of the devices. We went to version tree to retrieve the config and were surprised to see the Cisco Works does not have the latest config though it does say that the running config has been successfully backed up. We are running LMS 2.5 and Resource Manager Essentials 4.0.4. Any help in this regards will be greatly helpful. Thanks in advance.

Partial successfull output

1. test1 PRIMARY RUNNING Apr 22 2008 22:37:05 Successful

2. test1 PRIMARY STARTUP Apr 22 2008 22:36:42 Internal error

Version tree output :-

Devices

test1

PRIMARY

RUNNING

6/Nov 11 2007 09:45:28

7/Nov 11 2007 09:45:33

8/Nov 11 2007 09:46:26

9/Nov 11 2007 10:10:46

10/Nov 11 2007 10:27:58

11/Nov 11 2007 10:31:55

12/Nov 11 2007 10:33:35

13/Nov 26 2007 13:34:39

14/Dec 15 2007 01:26:43

15/Dec 27 2007 13:58:29

16/Dec 27 2007 14:02:58

17/Feb 24 2008 12:32:11

STARTUP

Best Regards,

Manoj

[Joe Clarke]

First, RME 4.0.4 is quite old relatively speaking. Given that you have LMS 2.5.1, you can freely upgrade to LMS 2.6 SP1 which comes with RME 4.0.6. This version has quite a few bug fixes in it.

It will also to help to understand how RME archives configurations. RME will only archive a configuration if an interesting change has occurred. Interesting changes are those which do not match a command which has been configured under RME > Admin > Config Mgmt > Exclude Commands. The reason RME doesn't create new config entries for each config fetch is that would cause the disk space to disappear rapidly.

So, what this output tells me is that the config on this device last changed on Feb 24, 2008, but RME is still successfully downloading the config as of April 22. In other words, the config from February 24 is still the latest config. If you were to make a change on this device, then force a config collection, the date would change in RME accordingly. So this is not a problem.

The startup config issue is a problem. Again. upgrading to RME 4.0.6 may fix this, but you can always enable ArchiveMgmt debugging under RME > Admin > System Preferences > Loglevel Settings, force a config archive, then check dcmaservice.log for errors.