Startup and Running Out-Of-Sync Summary on LMS 3.1

Answered Question
Sep 30th, 2009

I think commonly ask question but I couldn't find direct answer. what is the main reason the start up config newer than running config? if I run sync on device so which one will save? or dates are not the matter LMS save the running config, even though the dates are older than the start up. I don't want to mess all new configuration on the device, because currently I have unusual 400+ devices out of sync. if this is risky I want to go directly to the device. run "wr mem" command.

Thanks in advance.

I have this problem too.
0 votes
Correct Answer by yjdabear about 7 years 3 months ago

I think that's because RME always reports the Startup config timestamp based on when it goes and fetches it from the device. OTOH, for the Running config, RME reflects the same "Last configuration change at XX:XX:XX by so-and-so" timestemp one sees in "show running".

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Joe Clarke Wed, 09/30/2009 - 08:44

The reason RME reports startup and running configs out-of-sync is typically because someone made a config change without running "write mem". However, there is at least one known bug where configs fetched by TFTP may always report out-of-sync even if the configs appear to be in sync on the device. The workaround is to make use telnet or SSH to fetch the config. This bug is fixed in LMS 3.2.

The best way to confirm is to look at the archived configs in RME. What are the differences RME is reporting? If they appear to be strange lines at or below the banner commands, then you are seeing this bug. If they are inconsequential lines like "ntp clock-period", then you can add those commands to the list of exclude commands under RME > Admin > Config Mgmt > Exclude Commands, and RME will no longer report a diff.

If, however, the differences are legitimate, you should sync the configs on the device. RME can do this for you, or you can manually run "write mem", then re-fetch the running and startup configs.

raindrop18 Wed, 09/30/2009 - 08:59

thanks for detail explanation, however I have one issue didn't explain. what about the dates? why is running is older than start up?

Correct Answer
yjdabear Wed, 09/30/2009 - 09:11

I think that's because RME always reports the Startup config timestamp based on when it goes and fetches it from the device. OTOH, for the Running config, RME reflects the same "Last configuration change at XX:XX:XX by so-and-so" timestemp one sees in "show running".

Actions

This Discussion