NTP clock - period value constantly changing

[carlbagge]

                   NTP clock - period on 3750 w/ 12.2 - 25 SW version changes daily on approx 20 switches. CiscoWorks collects configs 2X daily as I didn't exclude NTP clock from config compare exclude. On other switches from same NTP source the NTP clock - period is very stable. Any thoughts on what may be causing this ?

Thanks

[Richard Burts · Accepted solution]

Carl

The value for ntp clock period is a reflection of what it takes to compensate for variability in the local clock. It does not reflect anything about the ntp source/server but is about the local condition. If you have 20 switches where this changes on a daily basis then I would believe that you have 20 switches where there is some (probably minor) issue with the local clock.

If it were me I would ignore this "issue" since I do not believe that it points at anything of significance. If Cisco Works is flagging this as an issue then I would make changes in Cisco Works to suppress this particular issue on these switches.

HTH

Rick

[Marvin Rhoads]

+5 what Rick said. Most config archiving products exclude checking the ntp clock period for this reason.

[Leo Laohoo]

I wouldn't bother with NTP clock-period.  It's not really relevant.  If you load 15.0(X) IOS you won't see this line.

NTP clock-period command line gets inserted by the IOS.  Even if your configuration DOES NOT include this line, the operation of your appliance is fine. 

[johnlloyd_13]

leo,

i didn't notice this line disappeared on newer 15.0 code not until you've mentioned it.

i've checked this on our ISR G2s. good stuff! +5

[Leo Laohoo]

Thanks John.

One thing to know if you're dealing with a cut-and-paste-monkey is to look at the configuration for this line.