HP switches and SNTP

[yodink]

Hi,
We have Windows 2003 AD with the SNTP time server enabled, and we're trying to get our HP 2610s configured for SNTP with the domain controller.

set the following:
___________________________________
ProCurve(config)# timesync sntp
ProCurve(config)# sntp unicast
ProCurve(config)# sntp server 172.16.176.104
___________________________________

After that, I have to set the polling interval to 30, then do a
___________________________________
ProCurve(config)# show logging
___________________________________

and I can see a single SNTP update in the log.
No matter what I set the polling interval to, no more updates occur after the initial one.

Also, the SNTP time sync sets the wrong time. It's off by 5 hours.
I tried setting the correct timezone and daylight setting

__________________
ProCurve(config)# time timezone -6
ProCurve(config)# time daylight-time-rule continental-us-and-canada
__________________

Any clues?

[Mark Wibaux · Accepted solution]

the timezone command uses the number of minutes (not hours) so your command should be
time timezone -360

And from the manual
SNTP Messages in the Event Log
If an SNTP time change of more than three seconds occurs, the switchâ s event log records the change. SNTP time changes of less than three seconds do not appear in the Event Log.

[Pieter 't Hart]

>>>
no more updates occur after the initial one.
<<<
I agree with max, if the clock stays synced no updates will be logged. Only correction of large differences will be logged.

>>>
Also, the SNTP time sync sets the wrong time. It's off by 5 hours.
I tried setting the correct timezone and daylight setting
<<<

The timesync should occur UTC.

depending on the configuration settings it's corrected with the timezone difference and dyalight saving time before being displayde/logged.

even then time can be logged in UTC and displayed in local time.

to check if synchronization runs look for commands likee "show sntp status" or "show sntp associations" (my commands are for cisco devices).

If this still goes wrong, it's time to check the sntp-server is running the correct timezone!

Pieter

[yodink]

Thanks all for your help.

Was setting timezone to -6 instead of -360 (seconds).