maintaining clock settings on a 2950 switch?

Answered Question
Mar 20th, 2008
User Badges:

I have set up external NTP synchronization on a 2950 switch which works fine while the switch is powered on. However if the switch is cycled with a "reload" command, the time established is way off once the switch comes back up. Is this the expected behaviour?


Thanks.

Correct Answer by Jon Marshall about 9 years 2 months ago

Hi


This is expected behaviour because the 2950 does not have a hardware clock which can keep the time between reboots. As long as your switch is resynching it's time via NTP it is nothing to worry about.


HTH


Jon

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Correct Answer
Jon Marshall Thu, 03/20/2008 - 01:53
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

Hi


This is expected behaviour because the 2950 does not have a hardware clock which can keep the time between reboots. As long as your switch is resynching it's time via NTP it is nothing to worry about.


HTH


Jon

ocicat002 Thu, 03/20/2008 - 02:09
User Badges:

Thanks for confirming! I hadn't found this in the documentation yet.

Joseph W. Doherty Thu, 03/20/2008 - 04:20
User Badges:
  • Super Bronze, 10000 points or more

BTW:

Also sometimes difficult finding mention whether the hardware supports an on-board calendar. I've found using the ntp update-calendar both often a fast method to help in determining this, and a great way to keep the calendar accurate across reboots/reloads (if you're using NTP).

Actions

This Discussion