NTP Status: Clock is unsynchronized

I have been having issues with a 3750X Stack that is not synchronizing with our NTP server. I have tried adding and removing the NTP server but it does not help. We are running Version 15.2(1)E. Any suggestions would be great! Thanks!

Daniel,
Thanks for the quick reply. Here is the “sh status” and “sh ntp associations”
Sh 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**19
ntp uptime is 26320700 (1/100 of seconds), resolution is 8403
reference time is 00000000.00000000 (18:00:00.000 CST Thu Dec 31 1899)
clock offset is 0.0000 msec, root delay is 0.00 msec
root dispersion is 0.16 msec, peer dispersion is 0.00 msec
loopfilter state is 'FSET' (Drift set from file), drift is 0.000000000 s/s
system poll interval is 64, never updated.
sh ntp associations
address         ref clock       st   when   poll reach delay offset   disp
~x.x.x.x    .LOCL.           1     40     64   377 2.409 2723270 16.508
~x.x.x.x     x.x.x.x     2      5     64   377 2.298 2723270 16.528
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured
We are using our internal Windows Domain Controller as an NTP source. I have multiple 3750 stacks looking at our DCs without an issue. Thanks!

Similar Messages

CiscoWorks: Compliance job to find NTP status in switches?

Hi,
We have about 4000 switches in our estate, and we want to find from CiscoWorks that which devices are not configured with correct NTP source. Is it possible to run a compliance job in CiscoWorks to findout that which switches "clock is unsynchronized". e.g. if we do "show ntp status" on switch, we get output as "clock is unsynchronized". How we can run this job in compliance jobs.
Or please advise a better way to find this issue.
We are using LMS 3.2 SP1
Thanks and Kind Regards,

I would run a job that puts the username password on all of them. And runs a no username johndoe for all username you know of, that you want to remove
So it may overwrite the same username password..... I don't mind, it will be done when I get back in the morning.
Cheers,
Michel

Cisco IOS NTP: "show ntp associations" versus "show ntp status"

what is the difference of the commands "show ntp ass det" and "show ntp status" ?
these commands differs on the referenced time source.
switch#sh ntp ass detail
Load for five secs: 17%/4%; one minute: 20%; five minutes: 20%
Time source is NTP, 10:45:15.469 MET Tue Feb 4 2014
10.1.5.4 configured, ipv4, sane, valid, stratum 2
ref ID 154.71.99.39   , time D69B3383.9D414772 (10:38:11.614 MET Tue Feb 4 2014)
our mode client, peer mode server, our poll intvl 1024, peer poll intvl 1024
root delay 0.38 msec, root disp 5.93, reach 377, sync dist 11.77
delay 0.84 msec, offset 0.3778 msec, dispersion 1.06, jitter 0.97 msec
precision 2**21, version 4
assoc id 26601, assoc name 10.1.5.4
assoc in packets 12339, assoc out packets 12361, assoc error packets 28
org time 00000000.00000000 (01:00:00.000 MET Mon Jan 1 1900)
rec time D69B347C.4ACDE42A (10:42:20.292 MET Tue Feb 4 2014)
xmt time D69B347C.4ACDE42A (10:42:20.292 MET Tue Feb 4 2014)
filtdelay =     0.88    0.87    0.85    0.90    0.84    0.90    0.89    0.87
filtoffset =    0.31    0.31    0.32    0.28    0.37    0.32    0.25    0.31
filterror =     0.97    1.00    1.03    1.06    1.09    1.12    1.15    1.18
minpoll = 6, maxpoll = 10
FD8C:2208:32F7:8EA::5 configured, ipv6, our_master, sane, valid, stratum 1
ref ID .PPS., time D69B318B.92FDD88A (10:29:47.574 MET Tue Feb 4 2014)
our mode client, peer mode server, our poll intvl 1024, peer poll intvl 1024
root delay 0.00 msec, root disp 0.42, reach 377, sync dist 17.18
c4507r01#show ntp status
Load for five secs: 19%/4%; one minute: 20%; five minutes: 20%
Time source is NTP, 10:42:03.441 MET Tue Feb 4 2014
Clock is synchronized, stratum 2, reference is 81.201.114.7
nominal freq is 250.0000 Hz, actual freq is 249.9987 Hz, precision is 2**10
ntp uptime is 752342800 (1/100 of seconds), resolution is 4016
reference time is D69B2950.47571873 (09:54:40.278 MET Tue Feb 4 2014)
clock offset is 0.9771 msec, root delay is 0.94 msec
root dispersion is 47.43 msec, peer dispersion is 1.03 msec
loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.000005068 s/s
system poll interval is 1024, last update was 2881 sec ago.
switch#sh ntp associations
Load for five secs: 18%/4%; one minute: 20%; five minutes: 20%
Time source is NTP, 10:53:12.750 MET Tue Feb 4 2014
address         ref clock       st   when   poll reach delay offset   disp
+~10.1.5.4      154.71.99.39     2    690   1024   377 0.848   0.377 1.069
*~FD8C:2208:32F7:8EA::5
                  .PPS.            1    400   1024   377 0.931   0.892 1.007
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured

Its hard to find expert on switches/IOS on the Network Management Forum, which is for NMS applications.
You should post this thread on Switching community of CSC forum.
Though, what i can suggest is to use SNTP. Certain low-end Cisco devices only support SNTP. SNTP is a simplified, client-only version of NTP. SNTP can only receive the time from NTP servers and cannot be used to provide time services to other systems. SNTP typically provides time within 100 milliseconds of the accurate time. In addition, SNTP does not authenticate traffic, although you can configure extended access lists to provide some protection. An SNTP client is more vulnerable to misbehaving servers than an NTP client and should only be used in situations where strong authentication is not required.
SNTP may not be much of an alternative because it is not widely supported in software.
You can use command # sntp server. SNTP generally is supported on those platforms that do not provide support for NTP.
Device (config)# sntp server {address | hostname} [version number]
For more clarification post this to Lan Switching and Routing section.
-Thanks
Vinod
**Rating Encourages contributors, and its really free. **

Timezone in ntp status

Hi
Please find below the output of "show ntp status" command on a NTP Server & client Routers.
NTP Server
Clock is synchronized, stratum 2, reference is 208.184.49.9
nominal freq is 250.0000 Hz, actual freq is 250.0001 Hz, precision is 2**18
reference time is C6D04612.22EA36B7 (21:23:14.136 kuwait Mon Sep 12 2005)
clock offset is 0.4224 msec, root delay is 217.96 msec
root dispersion is 1.24 msec, peer dispersion is 0.82 msec
NTP Client
Clock is synchronized, stratum 3, reference is xxx.xxx.xxx.xxx (IP address of the NTP Server)
nominal freq is 250.0000 Hz, actual freq is 250.0055 Hz, precision is 2**24
reference time is C6D04AF3.9FC434D0 (18:44:03.624 UTC Mon Sep 12 2005)
clock offset is 0.1061 msec, root delay is 220.26 msec
root dispersion is 1.07 msec, peer dispersion is 0.03 msec
The NTP Server's clock timezone (Kuwait) is configured properly. Why the NTP Client router (Shows UTC timezone) doesn't have the same timezone as of the NTP Server?
Also the following messages keep appearing on the console of the NTP Server Router. Is it related to NTP?
Sep 12 10:28:43.768: %DSX1-6-CLOCK_CHANGE: Freerun clock is now selected as clock source
Sep 12 10:29:15.379: %DSX1-6-CLOCK_CHANGE: Controller 1 clock is now selected as clock source
Sep 12 10:29:25.483: %DSX1-6-CLOCK_CHANGE: Freerun clock is now selected as clock source
Sep 12 10:29:31.023: %DSX1-6-CLOCK_CHANGE: Controller 0 clock is now selected as clock source
Sep 12 10:29:32.159: %DSX1-6-CLOCK_CHANGE: Freerun clock is now selected as clock source
Sep 12 10:29:55.471: %DSX1-6-CLOCK_CHANGE: Controller 1 clock is now selected as clock source
Sep 12 10:30:56.686: %DSX1-6-CLOCK_CHANGE: Freerun clock is now selected as clock source
Sep 12 10:31:56.185: %DSX1-6-CLOCK_CHANGE: Controller 1 clock is now selected as clock source
Sep 12 10:32:04.152: %DSX1-6-CLOCK_CHANGE: Freerun clock is now selected as clock source
Sep 12 10:32:10.900: %DSX1-6-CLOCK_CHANGE: Controller 0 clock is now selected as clock source
Sep 12 10:33:26.163: %DSX1-6-CLOCK_CHANGE: Freerun clock is now selected as clock source
Sep 12 10:33:56.135: %DSX1-6-CLOCK_CHANGE: Controller 0 clock is now selected as clock source
Sep 12 10:34:09.770: %DSX1-6-CLOCK_CHANGE: Freerun clock is now selected as clock source
Sep 12 10:34:16.942: %DSX1-6-CLOCK_CHANGE: Controller 1 clock is now selected as clock source
Sep 12 10:34:18.046: %DSX1-6-CLOCK_CHANGE: Freerun clock is now selected as clock source
Appreciate your reply.
Thanks in advance. // Anup

Anup
I believe the console message you ask about is not at all related to your NTP question. It looks to me like something is unstable about clocking for some serial interface or controller.
The explanation of your NTP question is that NTP transmits time in Universal Time (UTC) and the router translates that time into local timezone if it is configured to do so. Apparently the server has been configured to adjust for local time of Kuwait and the client has not. The command to adjust for local timezone is in global config:
clock timezone
If you configure this on the client you should find that the time is correctly translated.
HTH
Rick

GPS NTP reference clock

Hej,
I do have a problem on my OSX 10.6.6 Server - I cannot successfully connect a GPS receiver for my NTP service.
What I did works perfectly on OSX 10.6.6 client, but on the server it fails with
fcntl(F_SETOWN) fails for clock I/O: Inappropriate ioctl for device
The device is a HOLUX GM-210, connected via USB (PL2303 driver from Prolific)
works fine with cu, but not with the bundled ntpd.
I looked around, but only found one with the exact same problem back in 2004, but his question was never answered.
So what might be the reason for this behavior, and how to fix it?

MrHoffman wrote:
To clarify my understanding of the current configuration: setting the 127.127.20.0 driver doesn't get accepted via Server Admin, or that reference clock driver value is accepted but no synchronization happens? (I'd tend to expect it to be accepted, but that you're not getting a lock?)
Yes, serveradmin accepts that happily, but it does not show up as a valid peer.
if you're messing with the ntp configuration files (and adding stuff), try putting your additional lines after a # line or two. (The comment characters will reportedly keep Server Admin from stepping on your changes. This is one of the differences between Mac OS X and Linux distributions.)
Thanks for this valuable tip.
What does +ntpq -p+ show?
schneekoenig:~ oskar$ ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*time.euro.apple 17.72.133.54 2 u 772 68m 377 56.646 9.836 0.607
so, basically, the 127.127.20.0 does not show up.
Given the pl2303 stuff usually instantiates itself as a USB TTY device (/dev/ttyUSBxyz something or other? I run with another series of USB-to-serial widgets, so I will not see the same device names here as you'll get), and you might (will?) need to add a link to instantiate an appropriately-named a gps device for the NTP software to find. (Get a full disk backup first!) Something akin to this +ln -s /dev/whatever /dev/gps0+ command, given that the ntp daemon expects gps devices such as the /dev/gps0, gps1 or gps2 devices. Given you're using 127.127.20.0, the target device ntp will look for here is /dev/gps0, while 127.127.20.1 would seek /dev/gps1, etc. (Again, please make a full disk external backup before you go working with links in /dev given mistakes here can be deadly to OS stability. I'd suggest rebooting immediately after adding the link into /dev, too, to ensure ntp and the rest of the box reboots with happy-bits and not sad-bits.)
done all that before asking here
Once you reboot, try that +ntpq -p+ command, and see if you get non-zero values associated with your selected time base.
I'd guess you might have to play with the mode setting, too. (I'd likely try getting this to work with a one-line server command first, no mode, no other options, etc.)
I guess the problem is more likely in the way OSX Server handles the usbserial device. The exact same configuration works just fine on SnowLeopard 10.6.6 Client. Hmm, the client runs a 32 bit kernel, whereas the Server is in native 64 bit. Maybe the Prolific driver is not complete, in that fcntl(F_SETOWN) does not return the expected results in 64 bit mode. As stated before, ntpd finds the correct serial port, opens it successfully but then fails on the fcntl system call.
Jan 20 09:45:36 schneekoenig org.ntp.ntpd[25567]: refclock_setup fd 5 modem status: 0x6Jan 20 09:45:36 schneekoenig org.ntp.ntpd[25567]: refclock_ioctl: fd 5 flags 0x1
Jan 20 09:45:36 schneekoenig org.ntp.ntpd[25567]: addto_syslog: fcntl(F_SETOWN) fails for clock I/O: Inappropriate ioctl for device
Jan 20 09:45:36 schneekoenig org.ntp.ntpd[25567]: addto_syslog: configuration of 127.127.20.0 failed

How can I show status clock on the screen

hi,
how can I add the status bar clock on the bottom left side of the screen when in progress.
kind regards,
Faisal

You need to insert this FM in between your appropriate
code in Start-of-selection event. Please use text elements for the text and if possible PERFORM and FORM with Using parameters.
call function 'SAPGUI_PROGRESS_INDICATOR'
     exporting
          percentage = 20
          text       = 'Extracting Prepress Materials'.
call function 'SAPGUI_PROGRESS_INDICATOR'
     exporting
          percentage = 40
          text       = 'Extracting Finished Goods Material info'.
call function 'SAPGUI_PROGRESS_INDICATOR'
     exporting
          percentage = 60
          text       = 'Extracting Prepress orders'.
call function 'SAPGUI_PROGRESS_INDICATOR'
     exporting
          percentage = 65
          text       = 'Extracting Order Status and Longtext'.
call function 'SAPGUI_PROGRESS_INDICATOR'
     exporting
          percentage = 80
          text       = 'Extracting Sales orders'.
call function 'SAPGUI_PROGRESS_INDICATOR'
     exporting
          percentage = 85
          text       = 'Extracting FG orders'.
call function 'SAPGUI_PROGRESS_INDICATOR'
     exporting
          percentage = 90
          text       = 'Build list and filter'.
call function 'SAPGUI_PROGRESS_INDICATOR'
     exporting
          percentage = 95
          text       = 'Display Output'.
Edited by: senthil kumar on Oct 28, 2008 9:39 PM

Transfer Structure Status - Clock Symbol

I have data in my ODS and have moved that data to the cube. I have lost some of that data in the cube because of a delete of overlapping conditions. I need to get that data back into the cube from the ODS. I was going to load it from the ODS, but when I did, it only loaded a small portion of the packages from the ODS. The reason is because after our ERP upgrade, we had to activate the InfoSource. Now when you look at the Reconstruct tab in the ODS, the normal double green check marks have now been replaced with one check mark and a clock symbol. It appears this data cannot be recovered. Does anyone know if it is possible to recover this data and be able to move it to the cube.
Thanks, Keith J

Hi Keith,
When ever there is change to transfer structure in re construction tab we will get that clock symbol. In your case as you are loading data from ODS to CUBE , from your first load from ODS to recent load there is change in your ODS object structure,that is the reason u are seeing clock symbol.if u are trying to reconstruct your requests it will pop up a message stating that to ignore the request click no,I think it will upload that request again,if not do an init load from ODS again and schedule your deltas regularly
Regards
KK

NTP - clock unsynchronized

Hello Guys,
Why it is showing as unsynchronized? Could you please recommend me any free NTP server? Thx.
I have also tried with :
0.ch.pool.ntp.org
VOICE_1#show ntp associations
address ref clock st when poll reach delay offset disp
192.168.0.2 192.168.0.1 2 44 64 1 5.423 1046323 7937.5
~134.170.185.211 10.20.229.51 2 35 64 1 173.43 52356.2 7945.3
192.168.0.252 192.168.0.1 2 19 64 1 1.157 1046324 7937.7
192.168.0.253 192.168.0.1 2 7 64 1 1.849 1046319 7937.8
192.168.0.254 192.168.0.1 2 25 64 1 2.910 1046322 7937.6
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured
VOICE_1#show ntp status
Clock is unsynchronized, stratum 16, no reference clock
nominal freq is 250.0000 Hz, actual freq is 249.9933 Hz, precision is 2**24
reference time is D899CF76.87BD1EC1 (17:59:34.530 GTM+1 Thu Feb 26 2015)
clock offset is 0.0000 msec, root delay is 0.00 msec
root dispersion is 4.47 msec, peer dispersion is 0.00 msec
loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.000026765 s/s
system poll interval is 64, last update was -739 sec ago.
VOICE_1#sh run | s ntp
ntp server time.windows.com

VOICE_1#sh run | s ntp
ntp server time.windows.com
Never use a Windows device as an NTP source. Microsoft's implementation of NTP is not of the IEEE standard.
If you want an outside NTP source, make sure your firewall allows you to. Worldwide NTP pools can be found HERE.

ASA5500 using Windows 7 computer as NTP server

I have an ASA5510 connected to a computer running Windows 7 (the NTP Server) on its "inside" interface.
Using the ASDM, I have configured the ASA5510 to use the Windows 7 as its NTP server (my architecture forces me to use a local machine as an NTP server):
     -IP address: 192.0.99.1 (the ASA5510 has an IP address of 192.0.99.40)
     -Interface: inside
     -Key number: None
     -Enable NTP authentication: no.
I have other Windows computers on the "inside" interface using the NTP Server, so NTP traffic is relayed without any problem. But somehow, the ASA5510 is not able to synchronize with the NTP Server.
I see the following log entry:
     -Source IP: 192.0.99.1
     -Source Port: 123
     -Destination IP: 192.0.99.40
     -Destination port: 65535
     -Description: Teardown UDP connection 3905 for inside: 192.0.99.1/123 to identity: 192.0.99.40/65535 duration 0:02:01 bytes 96
so it seems like the ASA5510 sends a request to the NTP Server, but I am not sure whether the reply doesn't get processed correctly, or the connection stays open too long (my UDP connection timeout is the default, 2 minutes).
I had trouble getting SonicWALL NSA2400s to use Windows 7 devices as NTP servers. I had to get a firmware version where there was no MD5 authentication (which I think is OK in this case), and change a setting in the Windows registry (HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/services/W32Time/Config/AnnounceFlags: from 0xa to 0x5)
any insight is welcome.
Pedro

I have turned on all ntp debugging, and run "show ntp status" and "show ntp assoc":
CCG-SHIP-FWL(config)# show debug
debug ntp adjust enabled at level 1
debug ntp authentication enabled at level 1
debug ntp events enabled at level 1
debug ntp packets enabled at level 1
debug ntp params enabled at level 1
debug ntp select enabled at level 1
debug ntp sync enabled at level 1
debug ntp validity enabled at level 1
CCG-SHIP-FWL(config)# show ntp status
Clock is unsynchronized, stratum 16, no reference clock
nominal freq is 99.9984 Hz, actual freq is 99.9984 Hz, precision is 2**6
reference time is 00000000.00000000 (06:28:16.000 GMT Thu Feb 7 2036)
clock offset is 0.0000 msec, root delay is 0.00 msec
root dispersion is 0.00 msec, peer dispersion is 0.00 msec
CCG-SHIP-FWL(config)# show ntp assoc
      address         ref clock     st when poll reach delay offset    disp
~192.16.99.1      .LOCL.            1   380 1024 337    73.0 255671    71.0
* master (synced), # master (unsynced), + selected, - candidate, ~ configured
CCG-SHIP-FWL(config)# NTP: xmit packet to 192.16.99.1:
leap 3, mode 3, version 3, stratum 0, ppoll 1024
rtdel 0000 (0.000), rtdsp 10400 (1015.625), refid 00000000 (0.0.0.0)
ref 00000000.00000000 (06:28:16.000 GMT Thu Feb 7 2036)
org d34ac42f.4609d99d (20:21:03.273 GMT Tue May 1 2012)
rec d34a6050.3598360c (13:14:56.209 GMT Tue May 1 2012)
xmt d34a6250.22e73ba2 (13:23:28.136 GMT Tue May 1 2012)
NTP: rcv packet from 192.16.99.1 to OWN_FWL_LAN_PORT on inside:
leap 0, mode 4, version 3, stratum 1, ppoll 1024
rtdel 0000 (0.000), rtdsp a0bf4 (10046.692), refid 4c4f434c (76.79.67.76)
ref d34abbb0.bb426e39 (19:44:48.731 GMT Tue May 1 2012)
org d34a6250.22e73ba2 (13:23:28.136 GMT Tue May 1 2012)
rec d34ac62f.3977adb6 (20:29:35.224 GMT Tue May 1 2012)
xmt d34ac62f.3977adb6 (20:29:35.224 GMT Tue May 1 2012)
inp d34a6250.233258a0 (13:23:28.137 GMT Tue May 1 2012)
NTP: nlist 0, allow 0, found 0, low 0.000000, high 0.000000
NTP: no select intersection
NTP: synchronization lost

NTP server unreachable through ASA firewall

Hi all,
I've configured a DMZ switch to point to an NTP server on on the Inside, but I get a debug message on the switch that says:
NTP: <NTP server IP address> unreachable
I'm confident that the NTP server is configured properly, as there are more than a dozen other hosts using it, successfully. The difficulty here is that the NTP packets are having to flow from the DMZ to the Inside. I have a rule set on the firewall that permits the IP address of the switch to connect to the IP address of the NTP server as follows:
access-list intdmz1_acl extended permit udp host <IP address of switch> host <IP address of NTP server> eq ntp
I can see the hit counter on this rule incrementing.
The firewall can ping the NTP server, and the NTP server can ping the switch, so I think routing is OK.
Output from the DMZ switch:
switch#show ntp associations
      address         ref clock     st when poll reach delay offset    disp
~192.168.65.254   0.0.0.0          16     -    64    0     0.0    0.00 16000.
* master (synced), # master (unsynced), + selected, - candidate, ~ configured
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**17
reference time is 00000000.00000000 (00:00:00.000 GMT Mon Jan 1 1900)
clock offset is 0.0000 msec, root delay is 0.00 msec
root dispersion is 0.00 msec, peer dispersion is 0.00 msec
PRNLN-DMZ-SW01#sh run | inc ntp
ntp source Vlan138
ntp server 192.168.65.254
ukhvdc00vs01#sh run | inc ntp
ntp source Vlan65
ntp master 3
ntp update-calendar
ntp server 0.uk.pool.ntp.org
ntp server 1.uk.pool.ntp.org
PRNLN-DMZ-SW01#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**17
reference time is 00000000.00000000 (00:00:00.000 GMT Mon Jan 1 1900)
clock offset is 0.0000 msec, root delay is 0.00 msec
root dispersion is 0.00 msec, peer dispersion is 0.00 msec
Does the firewall rule need to permit more than UDP/123 for this to work perhaps?
NTPconfig on DMZ switch:
switch#sh run | inc ntp
ntp source Vlan138
ntp server <IP address of NTP server>
===================
NTP config on NTP server:
NTP_Server#sh run | inc ntp
ntp source Vlan65
ntp master 3
ntp update-calendar
ntp server 0.uk.pool.ntp.org
ntp server 1.uk.pool.ntp.org
Any guidance welcomed.
Thank you,
Olly

Hi Julio,
Hi Julio,
For the purposes of this information:
DMZ switch IP = 5.6.7.8
NTP server IP = 10.1.1.1
Here's the output from the show commands:
ciscoasa# show capture NTPCAPTUREDMZ
11 packets captured
   1: 16:22:05.271500 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
   2: 16:23:09.276185 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
   3: 16:24:13.274033 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
   4: 16:24:57.272813 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
   5: 16:24:58.279480 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
   6: 16:24:59.277817 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
   7: 16:25:00.275971 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
   8: 16:25:01.275559 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
   9: 16:25:02.272599 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
10: 16:25:03.279129 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
11: 16:25:04.277710 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
11 packets shown
ciscoasa# show capture NTPCAPTUREINSIDE
0 packet captured
0 packet shown
ciscoasa# show capture NTPASP | include 10.1.1.1
419: 16:24:13.274171 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
1820: 16:24:57.272904 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
1841: 16:24:58.279587 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
1876: 16:24:59.277909 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
1934: 16:25:00.276062 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
2027: 16:25:01.275651 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
2068: 16:25:02.272690 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
2095: 16:25:03.279221 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
2129: 16:25:04.277802 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
2200: 16:25:05.275849 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
2233: 16:25:06.274094 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
2275: 16:25:07.273606 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
2327: 16:25:08.280182 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
2347: 16:25:09.277222 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
2373: 16:25:10.275467 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
2399: 16:25:11.273759 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
2414: 16:25:12.273347 802.1Q vlan#138 P6 5.6.7.8.123 > 10.1.1.1.123: udp 48
I'm guessing we should see some packets in the second capture, but we're not...
Does this help?
Thanks!
Olly

Ntp server connection

Hello,
have a problem connecting to the ntp server please see below:
dslrouter#show ntp associations
address ref clock st when poll reach delay offset disp
~130.88.203.12 0.0.0.0 16 - 64 0 0.0 0.00 16000.
* master (synced), # master (unsynced), + selected, - candidate, ~ configured
dslrouter#show ntp status
Clock is unsynchronized, stratum 16, no reference clock
nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**16
reference time is 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)
clock offset is 0.0000 msec, root delay is 0.00 msec
root dispersion is 0.00 msec, peer dispersion is 0.00 msec
any reasons as this is the first time I am trying to synch to an NTP server.
on the wan inbound I have permitted the destination udp 123 port through the access-list

Do you have any ACL input in Gateway...disable one moment for test...it could be a problem from your ISP or ISP filter/Firewall input/output?? Could you try with another NTP server...

Linux ntp server with cisco 3850

hi all
i'm trying to make sync with linux ntp with cisco 3850 here is the what i did
linux centos 6.5 (on the ucs virtual machin) . this is a ntp server
ip 10.1.1.251
===================================================
For more information about this file, see the man pages
# ntp.conf(5), ntp_acc(5), ntp_auth(5), ntp_clock(5), ntp_misc(5), ntp_mon(5).
driftfile /var/lib/ntp/drift
# Permit time synchronization with our time source, but do not
# permit the source to query or modify the service on this system.
restrict default kod nomodify notrap nopeer noquery
restrict -6 default kod nomodify notrap nopeer noquery
# Permit all access over the loopback interface. This could
# be tightened as well, but to do so would effect some of
# the administrative functions.
restrict 127.0.0.1
restrict -6 ::1
# Hosts on local network are less restricted.
restrict 10.1.1.0 mask 255.255.255.0 nomodify notrap
# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html)
#server 1.centos.pool.ntp.org iburs
#server 2.centos.pool.ntp.org iburst
#server 3.centos.pool.ntp.org iburst
server 127.127.1.0
fudge 127.127.1.0 stratum 2
#broadcast 192.168.1.255 autokey        # broadcast server
#broadcastclient                        # broadcast client
#broadcast 224.0.1.1 autokey            # multicast server
#multicastclient 224.0.1.1              # multicast client
#manycastserver 239.255.254.254         # manycast server
#manycastclient 239.255.254.254 autokey # manycast client
# Enable public key cryptography.
#crypto
includefile /etc/ntp/crypto/pw
# Key file containing the keys and key identifiers used when operating
# with symmetric key cryptography.
keys /etc/ntp/keys
# Specify the key identifiers which are trusted.
#trustedkey 4 8 42
# Specify the key identifier to use with the ntpdc utility.
#requestkey 8
# Specify the key identifier to use with the ntpq utility.
#controlkey 8
# Enable writing of statistics records.
#statistics clockstats cryptostats loopstats peerstats
and cisco 3850 configured this one
ntp server 10.1.1.241
and
show ntp status
clock is unsynchronized, stratum 16, reference is null
why...didn't work.. somebody help me..

Is there a typo in your post or configuration? You show the NTP server IP address as 10.1.1.251, but the router configured to use 10.1.1.241.
Regards

Cisco 3750X wont sync to ntp server

sh version
Switch Ports Model SW Version SW Image
* 1 30 WS-C3750X-24 15.0(2)SE5 C3750E-UNIVERSALK9-M
nsi.swcore01#sho ntp associations
address ref clock st when poll reach delay offset disp
~192.168.68.254 .INIT. 16 - 1024 0 0.000 0.000 15937.
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured
nsi.swcore01#sh 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**17
reference time is 00000000.00000000 (08:00:00.000 GMT Mon Jan 1 1900)
clock offset is 0.0000 msec, root delay is 0.00 msec
root dispersion is 46985.14 msec, peer dispersion is 0.00 msec
loopfilter state is 'FSET' (Drift set from file), drift is 0.000000000 s/s
system poll interval is 64, never updated.
I tried to manually set the time so that the ntp server and the switch will have almost identical time, and btw NTP Server is a firewall, IP of the switch is allowed, and im actually seeing logs on the firewall side(watchguard) that it is trying to sync w/ the ntp server

NTP server is watchguard firewall, other devices such as AD, ubuntu server is pointed on it and using its time sychronization and its working, i dont know why im having an issue w/ cisco 3750x

NTP setup

Hi,
my customer has following NTP setup:
On C6500:
ntp clock-period 17180036
ntp source Vlan1
ntp master 2
ntp update-calendar
ntp peer 195.146.147.3 prefer
on ASA:
ntp server 217.118.109.178 source Outside prefer
I made same show commands to view current status:
C6500:
Central-C6506-E#show ntp status
Clock is synchronized, stratum 2, reference is 127.127.7.1
nominal freq is 250.0000 Hz, actual freq is 249.9975 Hz, precision is 2**18
reference time is CDECBB11.66582776 (16:47:45.399 GMT Wed Jun 24 2009)
clock offset is 0.0000 msec, root delay is 0.00 msec
root dispersion is 0.02 msec, peer dispersion is 0.02 msec
Central-C6506-E#show ntp associations
address ref clock st when poll reach delay offset disp
*~127.127.7.1 .LOCL. 1 55 64 377 0.0 0.00 0.0
~195.146.147.3 0.0.0.0 16 - 1024 0 0.0 0.00 16000.
* master (synced), # master (unsynced), + selected, - candidate, ~ configured
Central-C6506-E#show clock detail
16:48:46.860 GMT Wed Jun 24 2009
Time source is NTP
Summer time starts 02:00:00 GMT Sun Mar 29 2009
Summer time ends 03:00:00 GMT Sun Oct 25 2009
on ASA:
ASA# show ntp status
Clock is unsynchronized, stratum 16, no reference clock
nominal freq is 99.9984 Hz, actual freq is 100.0188 Hz, precision is 2**6
reference time is cd7dafda.e4f5dbf6 (11:18:18.894 CEDT Wed Apr 1 2009)
clock offset is -2.3843 msec, root delay is 0.50 msec
root dispersion is 52.11 msec, peer dispersion is 22.64 msec
ASA# show ntp associations
address ref clock st when poll reach delay offset disp
~217.118.109.178 194.160.23.2 2 84d 64 0 -0.0 -2.38 16000.
* master (synced), # master (unsynced), + selected, - candidate, ~ configured
ASA# show clock detail
16:46:11.870 CEDT Wed Jun 24 2009
Time source is NTP
Summer time starts 02:00:00 CEST Sun Mar 29 2009
Summer time ends 03:00:00 CEDT Sun Oct 25 2009
Then i made clock comparison:
Real time was: 16:37:30
On C6500:
Central-C6506-E#show clock
16:41:46.716 GMT Wed Jun 24 2009
On ASA:
ASA# show clock
16:38:36.094 CEDT Wed Jun 24 2009
So the time on ASA is shifted front to one minute and on C6500 four minutes.
My questions:
Whats are reasons that the time is shifted?
How to setup time/change actual setting that the time will be right on this machines?
Many thanks.

Because it is a customer system and i can't to change actual philosophy.
I want to synchronize it with external server but if i am right c6500 is always synchronized with himself at first.
C6506-E#show ntp associations
address ref clock st when poll reach delay offset disp
*~127.127.7.1 .LOCL. 1 55 64 377 0.0 0.00 0.0
~195.146.147.3 0.0.0.0 16 - 1024 0 0.0 0.00 16000.
* master (synced), # master (unsynced), + selected, - candidate, ~ configured
So how to setup c6500 that will be synchronized from external internet server and at the same time provide clock synchronization for all other devices on network?
Thanks.

NTP Issue on cisco 3560 switch

Hi all
Here is my ntp configuration
clock timezone GMT 4
clock summer-time UAE recurring
ntp server 192.168.10.254 version 2 prefer
end
sh 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**17
reference time is 00000000.00000000 (04:00:00.000 GMT Mon Jan 1 1900)
clock offset is 0.0000 msec, root delay is 0.00 msec
root dispersion is 0.00 msec, peer dispersion is 0.00 msec
-SW1#sh ntp associations
address ref clock st when poll reach delay offset disp
~192.168.10.254 0.0.0.0 16 - 64 0 0.0 0.00 16000.
* master (synced), # master (unsynced), + selected, - candidate, ~ configured
-SW1#
Please help me what i have did wrong
regards
raja

You are still not answering the question.
Is the appliance, with IP Address 192.168.10.254, synchronized with a valid SNTP/NTP address or not.
Even if you enable NTP Master (which I personally don't recommend) and your appliance is NOT synchronized to a valid NTP source, then the appliance 192.168.10.254 can potentially broadcast the WRONG time to all the appliance. Since you've forced all downstream appliances to synchronize with a source that has the wrong NTP data (using the command "ntp master") all your network equipment will be sporting the wrong time.

NTP Status: Clock is unsynchronized

Similar Messages

Maybe you are looking for