Clock on 3750 not syncing time from internal NTP

We have configured NTP on a local server on site. When I point my switch to the server, it wont sync the time. I can ping the server from the switch just fine. I am not getting anything out of a debug, nothing is coming up which makes me think that this isn't even trying,
LVL 3
Shark AttackNetwork adminAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Don JohnstonInstructorCommented:
Please post the (sanitized) config.
0
Shark AttackNetwork adminAuthor Commented:
Thats the only thing I got

_Switch#show run | i ntp
ntp server 10.153.0.21

Open in new window

Switch#ping 10.153.0.21

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.153.0.21, timeout is 2 seconds:
!!!!!

Open in new window

Switch#show ntp sta   
Clock is unsynchronized, stratum 16, no reference clock
nominal freq is 119.2092 Hz, actual freq is 119.2092 Hz, precision is 2**18
reference time is D9611B88.FD704FA5 (21:05:12.989 UTC Mon Jul 27 2015)
clock offset is -4.5307 msec, root delay is 186.80 msec
root dispersion is 68.95 msec, peer dispersion is 10.53 msec

Open in new window

Switch#show ntp associations detail 
10.153.0.21 configured, insane, invalid, unsynced, stratum 16
ref ID 0.0.0.0, time 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)
our mode client, peer mode unspec, our poll intvl 64, peer poll intvl 64
root delay 0.00 msec, root disp 0.00, reach 0, sync dist 0.000
delay 0.00 msec, offset 0.0000 msec, dispersion 16000.00
precision 2**5, version 3
org time 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)
rcv time 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)
xmt time D9611D95.FF50B683 (21:13:57.997 UTC Mon Jul 27 2015)
filtdelay =     0.00    0.00    0.00    0.00    0.00    0.00    0.00    0.00
filtoffset =    0.00    0.00    0.00    0.00    0.00    0.00    0.00    0.00
filterror =  16000.0 16000.0 16000.0 16000.0 16000.0 16000.0 16000.0 16000.0

Open in new window

0
Don JohnstonInstructorCommented:
Did you try "ntp server 10.153.0.21" instead of the "ntp peer" command?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Shark AttackNetwork adminAuthor Commented:
yes I did,  and then I put it back to server. Used to be peer..
0
Don JohnstonInstructorCommented:
Please remove the ntp peer statement and put in the ntp server command and after 5 minutes post the output of:

show ntp assoc
and
show ntp status
0
Shark AttackNetwork adminAuthor Commented:
Switch#show ntp associations 

      address         ref clock     st  when  poll reach  delay  offset    disp
 ~10.153.0.21      0.0.0.0          16     -    64    0     0.0    0.00  16000.
 * master (synced), # master (unsynced), + selected, - candidate, ~ configured

Open in new window

Switch#show ntp status 
Clock is unsynchronized, stratum 16, no reference clock
nominal freq is 119.2092 Hz, actual freq is 119.2092 Hz, precision is 2**18
reference time is D9611E03.0075E88C (21:15:47.001 UTC Mon Jul 27 2015)
clock offset is -0.8335 msec, root delay is 187.59 msec
root dispersion is 57.86 msec, peer dispersion is 3.13 msec

Open in new window

0
Don JohnstonInstructorCommented:
Couple things stand out:

The NTP server doesn't have a reference clock.
The stratum is 16.  Which I think means that it is invalid.

Just for giggles, Set your server to a public NTP server and see if it sync's.  Something like:

ntp server 64.90.182.55 prefer
0
Shark AttackNetwork adminAuthor Commented:
i did a different public server and it works.
Switch#show run | i ntp
ntp server 38.99.39.136 prefer

Open in new window

Switch#show ntp status 
Clock is synchronized, stratum 4, reference is 38.99.39.136
nominal freq is 119.2092 Hz, actual freq is 119.2092 Hz, precision is 2**18
reference time is D9612571.13CCF35C (21:47:29.077 UTC Mon Jul 27 2015)
clock offset is 16.5783 msec, root delay is 64.32 msec
root dispersion is 3949.17 msec, peer dispersion is 3875.12 msec

Open in new window

0
Shark AttackNetwork adminAuthor Commented:
does that mean that the NTP server is incorrectly configured ?
0
Don JohnstonInstructorCommented:
Yep.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Shark AttackNetwork adminAuthor Commented:
thank you
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.