Ntp via finder? and nmb via finder?

Can anyone suggest a good reason why my OS is constantly, and that's not an exaggeration, constantly contacting, or attempting to contact these services.
I have Little Snitch installed, and I've had it for a long time. This is the indicator where I see the attempts, or successful contacts to ntp (contacting time.apple.com), and 800 bytes coming back to my OS. This appears to be normal, but this goes on many times per minute. I've got a new machine with a fresh battery, so there is no reason why time.apple.com should be check so frequently, is there?
Then, at times, I also see nmb via Mach-Kernel! On and on the strangeness goes.
Any thoughts?
Thanks in advance for your ideas.
Ken (real name)

Please e-mail me.

Similar Messages

Need to synch NTP on 2100 and 4400 Wireless LAN Controllers

I have 5 WLC's (3-2100, 2-4400) and need to synch the NTP server ip addresses on them. I know how to do this but have a question. Using the gui, once I apply the change to the NTP ip address and save the changes, will the WLCs need to be rebooted for them to complete synchronization?

No, you don't have to reboot the controllers. They should sync right up.

NTP on Nexus5k and 3560

I have begun moving NTP from our 6500 to 4 Nexus 5k as part of a core upgrade. The Nexus will act as our internal NTP server for all switches. Any switches that are on the same vlan as the Nexus have no issues syncing NTP from them. However any switch that has to have the traffice routed to the Nexus is showing that the time source as insane.
The configuration on our Nexus is as follows the Nexus are .11,12,13 and 14:
ntp peer 172.24.1.12
ntp peer 172.24.1.13
ntp peer 172.24.1.14
ntp server 192.43.244.18
clock timezone CST -6 0
clock summer-time CDT 2 Sun Mar 2:00 1 Sun Nov 2:00 60
Here is the configuration on one of our 3560's:
clock timezone CST -6
clock summer-time CDT recurring
ntp server 172.24.1.11
ntp server 172.24.1.13
ntp server 172.24.1.12
ntp server 172.24.1.14
This same configuration worked when the switches were configured as NTP Peers to our 6500 (172.24.1.1). The ip for the 6500 has been moved to an HSRP address across the Nexus so I have pointed the switches at the individual IP for each Nexus.
Here is a debug ntp packet ouput from one of the 3560s:
.Mar 7 17:21:22: NTP: xmit packet to 172.24.1.11:
.Mar 7 17:21:22: leap 3, mode 3, version 3, stratum 0, ppoll 64
.Mar 7 17:21:22: rtdel 2445 (141.678), rtdsp C804D (12501.175), refid AC180101
(172.24.1.1)
.Mar 7 17:21:22: ref D2F4A4F5.9CBFA919 (06:32:53.612 CST6 Sun Feb 26 2012)
.Mar 7 17:21:22: org 00000000.00000000 (18:00:00.000 CST6 Thu Dec 31 1899)
.Mar 7 17:21:22: rec 00000000.00000000 (18:00:00.000 CST6 Thu Dec 31 1899)
.Mar 7 17:21:22: xmt D3021792.8D0B8963 (11:21:22.550 CST6 Wed Mar 7 2012)

Thanks for your reply.
My issue may be a little different than you encountered. In my configuration I am able to get some, but not all, SVIs on Nexus 5548s to funciton as NTP servers.
I have two Nexus 5548 vPC peers configured (N5K-1 and N5K-2) for HSRP and as NTP servers. A downstream 2960S switch stack (STK-7) is the NTP client. STK-7 is connected to N5K-1 and N5K-2 with a physical link each bundled into a port channel (multi-chassis Etherchannel on the STK-7 stack and vPC on the 5548 peers).
When the STK-7 NTP client is configure for NTP server IP addresses on the same network as the switch stack (10.3.0.0 in the diagram below) all possible IP addresses work (IP addresses in green), the “real” IP addresses of each SVI on the 5548s (10.3.0.111 & 10.3.0.112) as well as the HSRP IP address (10.3.0.1).
When the STK-7 NTP client is configured for NTP server IP addresses on a different network than the switch stack (10.10.0.0 in the diagram below) only the “real” IP address of the SVI on the 5548 to which the Etherchannel load-balancing mechanism directs the client to server NTP traffic (N5K-2) works. In the diagram above the client to server NTP traffic is sent on the link to N5K-2. In the diagram below NTP server 10.10.0.112 is reported as sane but NTP servers 10.10.0.111 and 10.10.0.1 are reported as insane (in red).
I am concerned that the issue is related to my vPC configuration.
Cisco TAC has indicated that this behavior is normal.

NTP on Cat2900XL and Cat3500XL switches

Can these switches be configured using NTP with "ntp server x.x.x.x"? The Configuration guide was saying that it can configure this but the command reference did not have this command, only "ntp broadcast client"! It's kinda confusing and I do not have a switch (of these series) on hand to confirm it.
Please advise. Thank you.

Hi,
It is possible to configure NTP on XL switches. I am using a 3500XL switch and ntp is configured in it.
Might differ with the IOS being used.
3500XL#sh ver
Cisco Internetwork Operating System Software
IOS (tm) C3500XL Software (C3500XL-C3H2S-M), Version 12.0(5)XU, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2000 by cisco Systems, Inc.
Compiled Mon 03-Apr-00 17:31 by swati
Image text-base: 0x00003000, data-base: 0x00301398
ROM: Bootstrap program is C3500XL boot loader
System image file is "flash:c3500XL-c3h2s-mz-120.5-XU.bin"
cisco WS-C3548-XL (PowerPC403) processor (revision 0x01) with 16384K/1024K bytes of memory.
Processor board ID 0x17, with hardware revision 0x00
Last reset from power-on
Processor is running Enterprise Edition Software
Cluster command switch capable
Cluster member switch capable
48 FastEthernet/IEEE 802.3 interface(s)
2 Gigabit Ethernet/IEEE 802.3 interface(s)
32K bytes of flash-simulated non-volatile configuration memory.
Configuration register is 0xF
#### NTP Config ###
ntp authentication-key 11111 md5 1234567
ntp authenticate
ntp trusted-key 11111
ntp clock-period 11259058
ntp server x.x.x.x key 11111
### NTP Association status ###
3500XL#sh ntp assoc
address ref clock st when poll reach delay offset disp
*~x.x.x.x y.y.y.y 2 4 64 377 1.6 -0.43 1.3
* master (synced), # master (unsynced), + selected, - candidate, ~ configured
3500XL#
thanks,
Naveen V

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

NTP sets SMB clients to wrong time

Hi
The Server (Mac OS 10.6 server) is set as a time server for the domain but from yesterday reset most of the Windows clients that logged on via SMB to about 3/4s hr fast with the result that IP address's were dropped (Lease expired) and software relying on a network connection failed, time stamps of saved files were wrong and emails had the wrong time. In one case the month was changed to October so the guy went on holiday! Seriously, this is a big problem.
I've tried resetting the time locale, NTP time server and got rid of "LocalTime" which was a folder instead of a simlink but clients are still reporting time anomalies.
Thanks

ntp isn't particularly related to smb/cifs/samba, nor to dhcp, and ntp doesn't implement local time; ntp uses utc/gmt as the time base, and the local boxes adjust their time and timezones based on the client-local timezone definitions.
It could be that ntp is misconfigured, that something has gone seriously wacky with the ntp time base (hardware error? software error? network error? time-based attack? etc), or there's a rogue ntp server running.
Have a look at the ntp chatter in the system.log console log on the ntp server as a starting point, and at whatever passes for logging on the ntp clients, and at the settings for ntp. Out-of-the-box, there can be the requirement to tweak the ntp client or daemon configuration via the /etc/ntp.conf file, for instance.

NTP(Network Time Protocol) Error whil installing Oracle 11gR2 RAC

Dear Friends,
I have installed oracle 11gr2 clusterware software in two node RAC. While i run the CLUVFY.SH, It shows error in NTP configuration.
1)I add "-x" parameter in "/etc/sysconfig/ntp" configuration file. and start the ntpd service and run the cluvfy.sh . then i got the below error.
Check: CTSS state
Node Name State
rac2 Observer
rac1 Observer
CTSS is in Observer state. Switching over to clock synchronization checks using NTP
Starting Clock synchronization checks using Network Time Protocol(NTP)...
NTP Configuration file check started...
The NTP configuration file "/etc/ntp.conf" is available on all nodes
NTP Configuration file check passed
Checking daemon liveness...
Check: Liveness for "ntpd"
Node Name Running?
rac2 no
rac1 no
Result: Liveness check failed for "ntpd"
PRVF-5415 : Check to see if NTP daemon is running failed
Result: Clock synchronization check using Network Time Protocol(NTP) failed
PRVF-9652 : Cluster Time Synchronization Services check failed
Post-check for cluster services setup was unsuccessful on all the nodes.
=============================================================================================
2)Down the ntpd service in both nodes and run the CLUVFY.SH.
Check: CTSS state
Node Name State
rac2 Observer
rac1 Observer
CTSS is in Observer state. Switching over to clock synchronization checks using NTP
Starting Clock synchronization checks using Network Time Protocol(NTP)...
NTP Configuration file check started...
The NTP configuration file "/etc/ntp.conf" is available on all nodes
NTP Configuration file check passed
Checking daemon liveness...
Check: Liveness for "ntpd"
Node Name Running?
rac2 no
rac1 yes
Result: Liveness check failed for "ntpd"
PRVF-5415 : Check to see if NTP daemon is running failed
Result: Clock synchronization check using Network Time Protocol(NTP) failed
PRVF-9652 : Cluster Time Synchronization Services check failed
Post-check for cluster services setup was unsuccessful on all the nodes.
==========================================================================
3)Based on some website advice, I down the ntpd service and move the "/etc/ntpd.conf" to another location.Then i got the below error.
Result: Query of CTSS for time offset passed
Check CTSS state started...
Check: CTSS state
Node Name State
rac2 Observer
CTSS is in Observer state. Switching over to clock synchronization checks using NTP
Starting Clock synchronization checks using Network Time Protocol(NTP)...
NTP Configuration file check started...
ERROR:
PRVF-5402 : Warning: Could not find NTP configuration file "/etc/ntp.conf" on node "rac2"
PRVF-5405 : The NTP configuration file "/etc/ntp.conf" does not exist on all nodes
rac2
PRVF-5414 : Check of NTP Config file failed on all nodes. Cannot proceed further for the NTP tests
Result: Clock synchronization check using Network Time Protocol(NTP) failed
PRVF-9652 : Cluster Time Synchronization Services check failed
=============================================================
What should i do to solve this issue?? Please help me ...

Hi,
I start the ntpd start the service in both node and done the CLUVFY.SH.
The output is below,
Checking if CTSS Resource is running on all nodes...
Check: CTSS Resource running on all nodes
Node Name Status
rac2 passed
rac1 passed
Result: CTSS resource check passed
Querying CTSS for time offset on all nodes...
Result: Query of CTSS for time offset passed
Check CTSS state started...
Check: CTSS state
Node Name State
rac2 Observer
rac1 Observer
CTSS is in Observer state. Switching over to clock synchronization checks using NTP
Starting Clock synchronization checks using Network Time Protocol(NTP)...
NTP Configuration file check started...
The NTP configuration file "/etc/ntp.conf" is available on all nodes
NTP Configuration file check passed
Checking daemon liveness...
Check: Liveness for "ntpd"
Node Name Running?
rac2 yes
rac1 yes
Result: Liveness check passed for "ntpd"
Checking NTP daemon command line for slewing option "-x"
Check: NTP daemon command line
Node Name Slewing Option Set?
rac2 yes
rac1 yes
Result:
NTP daemon slewing option check passed
Checking NTP daemon's boot time configuration, in file "/etc/sysconfig/ntpd", for slewing option "-x"
Check: NTP daemon's boot time configuration
Node Name Slewing Option Set?
rac2 yes
rac1 yes
Result:
NTP daemon's boot time configuration check for slewing option passed
NTP common Time Server Check started...
PRVF-5410 : Check of common NTP Time Server failed
PRVF-5416 : Query of NTP daemon failed on all nodes
Result: Clock synchronization check using Network Time Protocol(NTP) passed
Oracle Cluster Time Synchronization Services check passed
========================================================================================
[oracle@rac1 ~]$ /u01/app/grid/oracle/product/10.2.0/db_1/bin/cluvfy comp clocksync
Verifying Clock Synchronization across the cluster nodes
Checking if Clusterware is installed on all nodes...
Check of Clusterware install passed
Checking if CTSS Resource is running on all nodes...
CTSS resource check passed
Querying CTSS for time offset on all nodes...
Query of CTSS for time offset passed
Check CTSS state started...
CTSS is in Observer state. Switching over to clock synchronization checks using NTP
Starting Clock synchronization checks using Network Time Protocol(NTP)...
NTP Configuration file check started...
NTP Configuration file check passed
Checking daemon liveness...
Liveness check passed for "ntpd"
NTP daemon slewing option check passed
NTP daemon's boot time configuration check for slewing option passed
NTP common Time Server Check started...
PRVF-5410 : Check of common NTP Time Server failed
PRVF-5416 : Query of NTP daemon failed on all nodes
Clock synchronization check using Network Time Protocol(NTP) passed
Oracle Cluster Time Synchronization Services check passed
Verification of Clock Synchronization across the cluster nodes was successful.
[oracle@rac1 ~]$
================================================================================
I hope the problem solved. Am i correct??

[SOLVED] systemd and ntpd.service

I've just converted to pure systemd according to the wiki. Everything went remarkably well, with just a little blemish. While I'm not notified of any error at startup, when I check systemctl I find that ntpd.service's LOAD/ACTIVE/SUB is loaded/failed/failed.
systemctl status ntpd.service gives me this:
ntpd.service - Network Time Service
Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled)
Active: failed (Result: exit-code) since Thu, 18 Oct 2012 04:16:56 +0200; 6s ago
Process: 1397 ExecStart=/usr/bin/ntpd -g -u ntp:ntp (code=exited, status=0/SUCCESS)
Main PID: 1398 (code=exited, status=255)
CGroup: name=systemd:/system/ntpd.service
Oct 18 04:16:56 mike ntpd[1398]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 1 v6wildcard :: UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 2 lo 127.0.0.1 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 3 eth0 192.168.0.2 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 4 lo ::1 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 5 eth0 fe80::224:1dff:fec4:aebe UDP 123
Oct 18 04:16:56 mike ntpd[1398]: peers refreshed
Oct 18 04:16:56 mike ntpd[1398]: Listening on routing socket on fd #22 for interface updates
Oct 18 04:16:56 mike systemd[1]: Started Network Time Service.
and journalctl pretty much more of the same:
Oct 18 04:16:56 mike ntpd[1397]: ntpd [email protected] Tue Aug 21 15:06:24 UTC 2012 (1)
Oct 18 04:16:56 mike ntpd[1398]: proto: precision = 0.106 usec
Oct 18 04:16:56 mike ntpd[1398]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Oct 18 04:16:56 mike sudo[1394]: pam_unix(sudo:session): session closed for user root
Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 1 v6wildcard :: UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 2 lo 127.0.0.1 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 3 eth0 192.168.0.2 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 4 lo ::1 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 5 eth0 fe80::224:1dff:fec4:aebe UDP 123
Oct 18 04:16:56 mike ntpd[1398]: peers refreshed
Oct 18 04:16:56 mike ntpd[1398]: Listening on routing socket on fd #22 for interface updates
Oct 18 04:16:56 mike systemd[1]: Started Network Time Service.
Oct 18 04:16:56 mike systemd[1]: ntpd.service: main process exited, code=exited, status=255
Oct 18 04:16:56 mike systemd[1]: Unit ntpd.service entered failed state.
Trying to use it manually (eg. ntpd -qg) works, so I'm not sure what's wrong with it exactly. Where else should I look?
Last edited by Mr_Mario (2012-12-06 11:29:57)

slickvguy wrote:I've just started converting to systemd and ran into the same issue. I believe the problem is that you are missing the ntp group from your group file. If you updated your system and merely renamed your group.pacnew to group, it no longer contains the ntp group that was previously added. I just added the ntp group again ( ntp:x:87: ), and ntp started properly and the status is correct. Hope this helps.
That was it. Thank you!

Ntp.conf changes back every restart.

I start ntpd in the daemons section of rc.conf, and if i change the ntp.conf file and do "/etc/rc.d/ntpd restart" everything works well, the config file remains OK, but the next time I reboot (even if it is the next thing i do) the ntp.conf file change back.
I don't know why, but it seems that I am the only one that have that problem, beacouse I did not find anything like that in the forum, so I supose that it may be something that i did wrong.
Sorry about my poor english and thanks in advance.

I have had the problem in the past. I also used the suggestions inhttp://wiki.archlinux.org/index.php/NTP to no avail, so tired of dealing with the problem I created my own solution.
This is what I did and ** it works **
1. Create the ntp.conf file the way you like it.
2. Name it myntp.conf and store it in /etc/myntp.conf
3. Open /etc/rc.local and enter the following:
cp /etc/myntp.conf /etc/ntp.conf
4. Done.
Now when the network replaces your ntp.conf at boot your rc.local will "put it back".
Hope this helps.
R.

KDE, ntpd and drag&drop issues

Hi,
I use KDE and when I install ntpd (the problem disappears when I remove it) and I want to drag something (like windows), the dragging procedure starts after 5-6 seconds, so I have to hold the mouse in the position for 5-6 seconds. (it also happens when I try to select text).
Do you have encountered such a problem? Do you know how to fix the problem?
-nwxxeh

ewaller wrote:
Weird.
Okay, so when kde and ntp are installed, and ntpd is running, where are your processors spending their time? Use htop, or whatever that process monitor thing in KDE is called to find out what, if anything is sucking up processor cycles. Let us know.
Everything seems normal to me (htop).
Also, it happens on XFCE and Gnome, so it may be X11 issue.
Also, when I have ntp and timezone set to GMT+2, when I reboot my time sets to GMT+4 (not timezone, just time)...

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. **

NTP client in Windows 7 Professional Does Not Sync

I have an NTP server running on an Ubuntu Linux box. All of my other linux boxes are able to synchronize to this NTP server. My Windows 7 Professional box is not even after trying multiple steps suggested in these forums.
The NTP server is on the local network; the firewall and anti-virus do not seem to be causing issues. If I test the NTP server connection using the following line:
/stripchart /computer:192.168.2.63 /packetinfo
I see the following information:
Tracking 192.168.2.63 [192.168.2.63:123].
The current time is 1/28/2014 9:05:24 PM.
21:05:24 d:+00.0349180s o:-01.0741307s [ * | ]
[NTP Packet]
Leap Indicator: 0(no warning)
Version Number: 1
Mode: 4 (Server)
Stratum: 1 (primary reference - syncd by radio clock)
Poll Interval: 3 (8s)
Precision: -22 (238.419ns per tick)
Root Delay: 0x0000.0000 (unspecified)
Root Dispersion: 0x0001.DE2F (1.8679047s)
ReferenceId: 0x47505300 (source name: "GPS")
Reference Timestamp: 0xD690FAAE12CA0936 (150871 15:33:02.0733953s - 1/27/2014 10:33:02 AM)
Originate Timestamp: 0xD692E0645BE2FB0C (150873 02:05:24.3589322s - 1/28/2014 9:05:24 PM)
Receive Timestamp: 0xD692E0634D60F136 (150873 02:05:23.3022605s - 1/28/2014 9:05:23 PM)
Transmit Timestamp: 0xD692E0634D6672F1 (150873 02:05:23.3023445s - 1/28/2014 9:05:23 PM)
[non-NTP Packet]
Destination Timestamp: Roundtrip Delay: 34918000 (+00.0349180s)
Local Clock Offset: -1074130700 (-01.0741307s)
Which indicates to me that I am able to see the server and receive NTP packets.
However, if I try to configure the server manually thusly:
w32tm /config /manualpeerlist:192.168.2.63,0x1 /syncfromflags:manual /update
and perform a resync:
w32tm /resync /rediscover
I get the following error:
The computer did not resync because no time data was available.
But -- using wireshark I can see the NTP request go out and what looks like a valid NTP packet return from my server.
What other settings am I missing here? Why would an NTP packet arrive and not be recognized by w32tm?

I turned on the debug logging; I additionally see this information:
150873 02:42:22.3054052s - Reachability: Attempting to contact peer 192.168.2.63,0x1 (ntp.m|0x1|0.0.0.0:123->192.168.2.63:123).
150873 02:42:22.3054052s - PeerPollingThread: WaitTimeout
150873 02:42:22.3054052s - Polling peer 192.168.2.63,0x1 (ntp.m|0x1|0.0.0.0:123->192.168.2.63:123)
150873 02:42:22.3054052s - Sending packet to 192.168.2.63,0x1 (ntp.m|0x1|0.0.0.0:123->192.168.2.63:123) in Win2K detect mode, stage 1.
150873 02:42:22.3054052s - PeerPollingThread: waiting forever
150873 02:42:22.3054052s - PollIntervalChange(192.168.2.63,0x1 (ntp.m|0x1|0.0.0.0:123->192.168.2.63:123)): reclamp: 17 -> 10 (min=4, max=17, sys=10)
150873 02:42:22.3054052s - Peer poll: Max:604800.0000000s (special) Cur:00.0000000s
150873 02:42:22.3054052s - PeerPollingThread: waiting 604800.000s
150873 02:42:22.3364070s - ListeningThread -- DataAvailEvent set for socket 1 (0.0.0.0:123)
150873 02:42:22.3364070s - ListeningThread -- response heard from 192.168.2.63:123 <- 192.168.3.54:123
150873 02:42:22.3364070s - /-- NTP Packet:
150873 02:42:22.3364070s - | LeapIndicator: 0 - no warning; VersionNumber: 3; Mode: 4 - Server; LiVnMode: 0x1C
150873 02:42:22.3364070s - | Stratum: 1 - primary reference (syncd by radio clock)
150873 02:42:22.3364070s - | Poll Interval: 17 - out of valid range; Precision: -22 - 238.419ns per tick
150873 02:42:22.3364070s - | RootDelay: 0x0000.0000s - unspecified; RootDispersion: 0x0001.E6B3s - 1.90117s
150873 02:42:22.3364070s - | ReferenceClockIdentifier: 0x47505300 - source name: "GPS"
150873 02:42:22.3364070s - | ReferenceTimestamp: 0xD690FAAE12CA0936 - 13035310382073395300ns - 150871 15:33:02.0733953s
150873 02:42:22.3364070s - | OriginateTimestamp: 0xD692E90E4E2F0902 - 13035436942305405200ns - 150873 02:42:22.3054052s
150873 02:42:22.3364070s - | ReceiveTimestamp: 0xD692E90D43D54D4D - 13035436941264973500ns - 150873 02:42:21.2649735s
150873 02:42:22.3364070s - | TransmitTimestamp: 0xD692E90D43DA4B0A - 13035436941265049600ns - 150873 02:42:21.2650496s
150873 02:42:22.3364070s - >-- Non-packet info:
150873 02:42:22.3364070s - | DestinationTimestamp: 150873 02:42:22.3364070s - 0xD692E90E561EC4E7150873 02:42:22.3364070s - - 13035436942336407000ns150873 02:42:22.3364070s - - 150873 02:42:22.3364070s
150873 02:42:22.3364070s - | RoundtripDelay: 30925700ns (0s)
150873 02:42:22.3364070s - | LocalClockOffset: -1055894500ns - 0:01.055894500s
150873 02:42:22.3364070s - \--
150873 02:42:22.3364070s - ListeningThread STC:76245282
150873 02:42:22.3364070s - Peer 192.168.2.63,0x1 (ntp.m|0x1|0.0.0.0:123->192.168.2.63:123) is not Win2K. Setting compat flags.
150873 02:42:22.3364070s - Packet test 6 failed (not syncd or bad interval since last sync).
150873 02:42:22.3364070s - Ignoring packet that failed tests from 192.168.2.63,0x1 (ntp.m|0x1|0.0.0.0:123->192.168.2.63:123).
150873 02:42:38.3063204s - W32TmServiceMain: timeout
150873 02:42:38.3063204s - Sample Prepared at 130354369583063204 for peer 192.168.2.63,0x1 (ntp.m|0x1|0.0.0.0:123->192.168.2.63:123)
I've done a little searching on what causes the "Packet test 6 failed" error without too many useful results ... any thoughts?

Using a Cisco Switch as the NTP Master time source for a Windows PDC

Hi all,
We have a closed network (no connectivity to the internet) and we have a Core router setup as the NTP Master for the rest of the network.
All network devices are getting the time synced as intended but we are having issues getting the Primary Domain Controller (PDC) registering to it as a valid NTP time source.
The problem we have is that we are affected by IOS bug CSCed13703 which rejects the PDC as an NTP associated device. Short of changing the IOS on the Router which is the main router feeding 30 other sites I would like to point the PDC at a different switch (an NTP Client switch) as it’s NTP source, rather than it going to the actual NTP Master.
I have changed the values in the PDC to point to a different switch (3750) that has it’s time synced with the NTP master, but the PDC doesn’t want to know. I assume it will only accept the time from an official NTP Master .
Could any of you fine people advise if what I am trying to do is possible and if so how I would go about it. I was thinking of setting the 3750 with the NTP Master command also, but I don’t want to confuse the other cisco devices in the network
Thanks in advance
David

Thanks Marvin,
I can confirm the Stratum on the 3750 is set to 15. This is due to the NTP Time source being an internal router and not an authoritative time source out on the internet. When setting the clock and using the NTP Master command on my internal router it sets the Stratum level to 14.
I have pointed the PDC at the Router (Stratum 14) and it does successfully sync time, but won't trust it as a valid source after the first sync. Upon reading I believed this to be the IOS bug as the symptoms are identical. Your theory of the PDC requiring a Stratum 2 time source is logical (especially in this scenario) but I have seen them use Stratum 4 before and it worked just fine.
I guess I could change the Router acting as a time source for the network to be NTP Master 1 which should force Stratum 1 giving the PDC and all other switches pointing to it a Stratumlevel of 2 which would prove it either way. I don't mind pointing the PDC at the router instead of the switch so long as it gets the time synced and trusts it from that point on.
I was going to make the 3750 switch an NTP Master for the Network and point the PDC to it (as per my previous post) but I have noticed this morning that the NTP Master command isn't available on the 3750 as it has no hardware clock!
Are you aware of any other way of forcing the 3750 to become a time source for the PDC without using the NTP Master command? I have looked at the NTP Peer command and I have ruled this out already and I still need the switch to be a client of the NTP Master Router on the network
Cheers for getting involved,
David

"Local" failover for NTP Server on Solaris 10

I have four Solaris 10 Servers, all syncing their time from an external NTP server ntp.example.com.
Is it possible to configure one of the four servers as a local "pseudo" Failover NTP, i.e. acting as a client to ntp.example.com, as long as it is available, and acting as a NTP server to the remaining three servers in case ntp.example.com is not available, so that at least the four local servers remain synced among themselves?

Shouldn't be any problem. For one thing you can always specify multiple servers in the /etc/inet/ntp.conf file and use one of them as 'prefer', i.e.:
server ntp.example.com prefer
server local.mydomain.com
Then again, perhaps it would just be easier if one of your servers syncs against 'ntp.example.com' and the rest of your servers always synchronizes against that one server?
.7/M.

NTP reverts to local 127.127.1.0 (VMware)

HI. I am experiencing an issue with a LAB deployment of CISCO ISE. I cannot get the NTP to sync and the DB services to start. See output below. Any help will be appreciated
iselab/admin# sh ntp
Configured NTP Servers:
172.16.0.101
synchronised to local net at stratum 11
time correct to within 11 ms
polling server every 1024 s
remote refid st t when poll reach delay offset jitter
==============================================================================
*127.127.1.0 .LOCL. 10 l 26 64 377 0.000 0.000 0.001
172.16.0.101 172.16.0.253 2 u 1630 1024 0 0.000 0.000 0.000
* Current time source, + Candidate
Warning: Output results may conflict during periods of changing synchronization.

The clock sync can take up to 20 minutes to complete. You may also want to ensure that the ESXi server is also using the same NTP server as your ISE VM. Since 127.127.1.0 is the local clock, having the ESXi configured this way will help to ensure the correct time in your VM.
The following quote is taken from the page linked below it:
"For example, NTP uses a pseudo IP address 127.127.8.n to access a Meinberg radio clock installed at the local computer. To access its own system clock, also called the local clock , NTP uses the pseudo IP address 127.127.1.0. This IP address must not be mixed up with 127.0.0.1, which is the IP of the localhost, i.e. the computer's loopback interface."
http://www.meinbergglobal.com/english/info/ntp.htm
Please let me know if this fixes your issue. If it does, please rate this answer and mark your question as Answered.
Charles Moreton

Ntp via finder? and nmb via finder?

Similar Messages

Maybe you are looking for