Saving the configuration or not saving the configuration will not make any difference about the time being saved over a reload of the switch. Some Cisco devices have a calendar chip that will maintain time over a reload. Other Cisco devices do not have this chip and they will lose their time when they reload and it has nothing to do with saving the config. The suggestion about checking show version to verify whether the switch had reloaded or not is probably a good suggestion if you want to be sure of why the time changed.
As far as NTP is concerned you can make a Cisco device act as an NTP server by using the config command ntp master. I would suggest that you do this only on a device that has the calendar chip and will maintain time over a reload. Even better is to configure your Cisco routers and switches to learn time from some external NTP server.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...