running config not archived

Answered Question
Oct 15th, 2009

We have LMS 3.2 and on few devices the running config is not archived. the start up is archived and I have running config on device but RME unable pull that that running config. on version tree I can see on VLAN section the there is a running config however on PRIMARY section there is no new running config showing the old running dates that's 1 month old. where or which log I need to see the find out the error related to this issue or any suggestion highly appreciated.

Correct Answer by Joe Clarke about 7 years 4 months ago

RME will only update the archive if it detected an interesting change in the config (i.e. one not listed in the configured Exclude Commands). It sounds like the archive is already properly populated for this device. If not, you would certainly get an error when RME tries to decide if it needs to archive the config.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Thu, 10/15/2009 - 08:43

You should first run a new Sync Archive job for one such device. If the job fails, the failure error will be helpful, and the dcmaservice.log will have more details.

raindrop18 Thu, 10/15/2009 - 09:10

I did run Sync Archive job for one device and the job is not fails. actually it's successful. however the running config is not updated. and i know I have a running config on this specific device. I have checked dcmaservice.log there is no error reported. did i miss something?

Correct Answer
Joe Clarke Thu, 10/15/2009 - 09:12

RME will only update the archive if it detected an interesting change in the config (i.e. one not listed in the configured Exclude Commands). It sounds like the archive is already properly populated for this device. If not, you would certainly get an error when RME tries to decide if it needs to archive the config.

Actions

This Discussion