There seems to be a bug in the switch group for SNTP.When deploying SNTP settings the outgoing udp PORT seems to default to 1029 and not 123 from what I can tell , and I cannot see any TZ settings being applied.
show sntp unicast-mode status
auto discovery of sntp/ntp servers is enabled
unicast poll interval value is 64
unicast max poll time out value is 5
unicast max retry time value is 3
unicast current mode value is NOT SYNCHRONIZED
sntp client is up for 00:07:46
unicast primary server host name is pool.ntp.org
unicast primary server version is 4
unicast primary server port is 1029
Num sntp-client req-msgs transmitted to the primary server 3
show running-config sntp
# Building configuration...
# Software version: 3.2.1-r5
# Model Name : cnMatrix EX2028-P
!
sntp
set sntp client enabled
set sntp unicast-server auto-discovery enabled
set sntp unicast-server domain-name pool.ntp.org port 1029
!
end
Of course right after I submit the post, it start syncing Seems to just take its sweet time.
One thing that doesn’t seem to work is the timezone setting.Doesn’t seem to affect timing at all and I can’t find any trace in the config that it alter the clock setting.Seems to be stuck on UTC 0
show sntp unicast-mode status
auto discovery of sntp/ntp servers is enabled
unicast poll interval value is 64
unicast max poll time out value is 5
unicast max retry time value is 3
unicast current mode value is SYNCHRONIZED TO PRIMARY SERVER
sntp client is up for 00:22:35
unicast primary server resolved ip address is 5.200.6.34
unicast primary server host name is pool.ntp.org
unicast primary server version is 4
unicast primary server port is 1029
last updated time from the primary server is Mon Feb 01 2021 10:52:43
Num sntp-client req-msgs transmitted to the primary server 9
show clock properties
System Clock Information
------------------------
Variance : 0
Class : 248
Accuracy : 254
Source : NTP
Offset : +00:00 (UTC)
HoldOver : Enabled
We were able to reproduce the issues related to SNTP and have fix currently being tested by our QA team. I will reply back once we have the servers updated with the fix. Thanks for listing out the issues.
Seems to just take its sweet time.