Removing or disabling the config change timestamp notification

Unanswered Question
May 17th, 2007

Would like to know how to get rid of the following config change notification timestamps on the cisco routers.

!Last configuration change at 23:01:52 AZ Mon May 14 2007 by test1"

!NVRAM config last updated at 22:31:48 AZ Mon May 14 2007 by test1

These messages are always on the top of the "show run" output on cisco routers.



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Richard Burts Thu, 05/17/2007 - 09:54


It is my understanding that if the router believes that it has correct time that it will put the timestamp in show run. I am not aware of any way to remove or stop the timestamp in show run except to take away correct time (do not run NTP and do not set clock). And I would not want to take away correct time.



rohit.rastogi Thu, 05/17/2007 - 10:02

Rick, We have this router which was configured with the command from exec mode "clock set" & since then we r seeing these config change timestamps messages.

Wondering if there is some sort of reverse command for "clock set" which would turn this off. Could u clarify when u say "do not set clock" here? Are u implying that I put a incorrect time on the router?

Richard Burts Thu, 05/17/2007 - 10:19


No I am not suggesting that you put an incorrect time. The use of that timestamp does not depend on whether the router has correct time or not but depends on whether the router BELIEVES that it has correct time - which clock set does.

Once the clock is set I believe that the router will put the timestamp in the show run. If you reboot the router and do not do clock set, then I believe that it may stop showing time in show run (but log messages and anything else from the router will not know what time it is).

Is there some reason that you object to having the timestamp in the show run/



rohit.rastogi Thu, 05/17/2007 - 10:41


Only reason that our team doesn't want this to have any timestamps for the config changes being the fact that this router is not yet in PROD/LIVE for the internet traffic. Hence this router should be accessible w/o any log being created for now. This way we know L-4 doesn't think it otherwise. Thanks for the suggestion here.


This Discussion