SNTP - Clock is unsynchronized

[BigK]

I configured SNTP on 2 remote sites exactly the same. They both able to reach the SNTP server( switch). I can ping and traceroute to sntp ip from both sites. Both sites reach the same ip in the 6th hop. Site 1 shows the correct day and time but site 2 does not. any help is appreciated. 

Both sites are using Cisco SG350 with same firmware. 

Site 1 #

clock timezone PST -8
clock summer-time PDT recurring usa
sntp server 10.10.x.2

Site 1#sho clock

 07:09:39 PDT  Jun 21 2019

Time source is sntp

Site 1 #sho sntp status

Clock is synchronized, stratum 2, reference is 10.10.x.2, unicast

Unicast servers:

Server : 10.10.x.2
Source : Static
Stratum : 2
Status : up

Site 1#traceroute ip 10.10.x.2

 1  10.22.x.25 

 2  10.22.x.3 

 3  x.x.x.x public IP  

 4 x.x.x.x  public IP

 5  x.x.x.202 public IP

 6  10.10.x.5 

Site 2#

clock timezone PST -8
clock summer-time PDT recurring usa
sntp server 10.10.x.2

Site 2 #sho clock

*17:09:30 PDT  Apr 15 2019

Time source is sntp

Site 2 #show sntp status

Clock is unsynchronized

Unicast servers:

Server : 10.10.x.2
Source : Static
Stratum : 255
Status : down

Site 2#traceroute ip 10.10.x.2

 1  10.30.x.25 

 2  10.30.x.2 

 3  x.x.x.x  public IP

 4  x.x.x.x  public IP 

 5 x.x.x.202 public IP

 6  10.10.x.5 

[marce1000]

 https://www.cisco.com/c/en/us/support/docs/ip/network-time-protocol-ntp/116161-trouble-ntp-00.html

 M.

[BigK]

Only two commands are available on SG350

Site 1 #sho sntp
configuration    --> Show the configuration of the Simple Network Time Protocol (SNTP)
status             -->To show the status of the Simple Network Time Protocol (SNTP)

[Richard Burts]

It is sort of helpful to know that you do have IP connectivity for both switches to the sntp server (both can traceroute). The symptoms suggest that something is interfering with sntp from site 2. Is it possible that something along the path to the server (perhaps a firewall or something like that) has a security policy that is not allowing sntp traffic?

HTH

Rick

[BigK · Accepted solution]

Thanks for the reply. Issue has been resolved. After carefully going trough the config. I found out that applying the source interface for sntp helped resolved the issue.