NTP Issue

[prodigy811]

Hi there,

Any help on my issue. New 5510 switch installed and configured NTP etc, however it is still 1 hour off even though its sync with NTP server. What is the possible issue. Someone mentioned about having to do it via the GUI first, surely this cannot be true.
I look forwrd to hearing from you.

[Ivan_B]

Hello @prodigy811 !

Could you share with us:

1. NTP related statements from "current-config"
2. Output of "display ntp-service status" and "display ntp-service sessions" command

[prodigy811]

Hi Ivan,

Many thanks for getting back to me, please find output below;

dis current-configuration | i ntp

clock protocol ntp

clock protocol ntp

ntp-service enable

ntp-service unicast-server 10.60.82.7 priority

ntp-service unicast-server 10.60.82.6

dis ntp-service status

 Clock status: synchronized

Clock stratum: 2

 System peer: 10.60.82.7

 Local mode: client

Reference clock ID: 10.60.82.7

Leap indicator: 00

Clock jitter: 0.000198 s

Stability: 0.000 pps

 Clock precision: 2^-20

Root delay: 0.67139 ms

 Root dispersion: 5.55420 ms

 Reference time: e2ee4f03.39daaaa8  Mon, Aug 24 2020 14:36:51.225

dis ntp-service sessions

       source          reference       stra reach poll  now offset  delay disper

********************************************************************************

[12345]10.60.82.7      GPSs               1   255   64   28 -0.152 0.6713 3.5400

  [245]10.60.82.6      GPSs               1   255   64   39 -0.155 0.8087 3.8909

Notes: 1 source(master), 2 source(peer), 3 selected, 4 candidate, 5 configured.

Total sessions: 2

dis clock

14:38:55 UTC Mon 08/24/2020

I should be on IST time also

[Ivan_B · Accepted solution]

Sorry if I am missing something, but your clock seems synced with 10.60.82.7:

dis ntp-service status
Clock status: synchronized
Clock stratum: 2
System peer: 10.60.82.7
Local mode: client
Reference clock ID: 10.60.82.7
Leap indicator: 00
Clock jitter: 0.000198 s
Stability: 0.000 pps
Clock precision: 2^-20
Root delay: 0.67139 ms
Root dispersion: 5.55420 ms
Reference time: e2ee4f03.39daaaa8 Mon, Aug 24 2020 14:36:51.225

dis ntp-service sessions
source reference stra reach poll now offset delay disper
********************************************************************************
[12345]10.60.82.7 GPSs 1 255 64 28 -0.152 0.6713 3.5400
[245]10.60.82.6 GPSs 1 255 64 39 -0.155 0.8087 3.8909
Notes: 1 source(master), 2 source(peer), 3 selected, 4 candidate, 5 configured.
Total sessions: 2

dis clock
14:38:55 UTC Mon 08/24/2020

Was your question about timezone setting or about NTP clock syncing? These are two different stories.

If you need to set the time zone, use "clock timezone" command. However, there is no pre-defined IST timezone there. Actually, there is no single pre-defined timezone. You need to craft it by yourself. If IST is Indian Standard Time, then your configuration must be:

system-view
clock timezone IST add 5:30:00

[prodigy811]

Hi Ivan,

I thought they are both interlinked..So I presumed that once it syncs with NTP server it would automatically receive all timezone and time/date information?

So for all new builds i will have to add in the timezone IST add 1hr etc?

Many thanks for your help

[Ivan_B]

All NTP servers use UTC timezone and this is the only format NTP clients get time information from them. Then it's up to the client how to translate UTC timezone to the local standard. That is why all devices have separate timezone settings. If we think logically, how a switch can realize in what time zone it is located? It doesn't have location services like modern phones and PCs, so the only way to let it know where it is installed is to set the time zone setting, so it can correctly adjust its clock and convert UTC time to the local standard.

So yes, on all Comware (and ALL other vendors, really) devices you have to set the time zone manually, otherwise devices will use UTC clock as per NTP server's information. 

P.S. If my answer is useful and resolve your problem, please, mark it as accepted solution. Thank you!