Synchronization of NTP in VSS

Hi,
Can anyone say with certainty that NTP is fully synchronized across a VSS system? In other words, if I point all of my non-core devices at an IP residing on my network core boxes (the network management VLAN IP shared by the VSS components) for NTP, are there any implications of a failover in the VSS?
Thanks much!
Scott

While I was waiting I contacted customer support in Italian "chat" by the help of CreativeCloudDesktop I solved the problem.
This is the interview in Italian:
David: quando effettua la sincronizzazione riceve un errore?
Maurizio Barut: Nessun messaggio di errore, ho reinstallato il sistema Maverick sul MacBook air e quindi il CC Desktop a nuovo, ma mi scarica e aggiorna le applicazioni, mi crea la cartella CC ma nella cartella non ci sono i file che ho già sul CCCloud e che vedo sull'altro computer e sul Iphone.
David: haprovato a ricreare la cartella?
Maurizio Barut: L'ho chiusa, l'ho riaperta dalle preferenze, l'ho spostata, ma niente.
David: le conviene eliminarla e ricrearla
Maurizio Barut: Come faccio?
David: con la stessa procedura utilizzata in porecedenza
David: http://helpx.adobe.com/it/creative-cloud/help/sync-files.html
Maurizio Barut: Non capisco, io le sto parlano della cartella « Creative Cloud Files » che di solito viene creata nella pagina Home dell'utente.
David: vede che sotto la voce "sincronizzazione File" del link che le ho appena fornito c'e "crea cartella"?
Maurizio Barut: Certo, ma quello è riferito a « caricare i file direttamente nella pagina File Creative Cloud », quindi da un browser! Io non vedo i files cho ho già nel CCCloud (2,83 GB di 20GB) nella cartella Creative Cloud Files nell'hard disk del computer!
David: ok
David: le do due indicazioni per risolvere
David: provi con la cancellazione di queste cartelle
David: cartella HOSTS : Aprire il Finder --->cliccare nella barra superiore dello schermo su 'Vai' ---> cliccare su'Vai a cartella' ---> digitare '/etc' ---> selezionare il file Hosts
David: Mac OS X : Macintosh HD>Library>Applciation support>Adobe>OOBE .
So I did, and so now it works!

Similar Messages

WLC not synchronize with NTP

Hi,
I need some help, I have configured my ntp server server in my WLC but i jut noticed that the time is not syncronized. I am able to ping the ntp server in my WLC. Appreciate if someone can help me to correct this problem.
Thanks,
Jong

Hi Jong,
There are some good examples and troubleshooting ideas in this doc;
NTP Configuration and Synchronization for Unified Wireless Network Devices
http://www.cisco.com/en/US/products/ps6366/products_configuration_example09186a0080811274.shtml#setup-wlc
Hope this helps!
Rob

NTP time server failed

Hi all,
In oracle 11.2.0.1.0,
$ 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 "xntpd"
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.
If i manually check the time,its synchronized.
Also the result was successful here. But why it shows PRVF errors.
Could you suggest.
Thanks,
Abdur Raoof

PRVF-05410: Check of common NTP Time Server failed
Cause: The NTP query command showed there is no common time server among all of the nodes in the cluster.
Action: At least one common NTP Time Server is required for a successful Clock Synchronization check. Reconfigure all of the nodes in the cluster to synchronize with at least one common NTP Time Server. If you plan to use CTSS for time synchronization then NTP configuration should be uninstalled on all nodes of the cluster. Refer to "Preparing Your Cluster" of "Oracle Database 2 Day+ Real Application Clusters Guide".
http://download.oracle.com/docs/cd/E14072_01/server.112/e10880/prvfmsg.htm
Regards
Asif Kabir

Time synchronization using SNTP

Hello all,
I my trying to set up SNTP synchronization of my cRIO to NTP server. To do that, I followed instructions in: http://digital.ni.com/public.nsf/allkb/F2B057C72B537EA2862572D100646D43
When I did reboot on my cRIO, time synchronization was successful. Then I changed the clock on cRIO manually to be 2 minutes ahead of that on NTP server. In this way I wanted to test the time synchronization, but nothing happened, i.e. after 30 minutes of waiting clock on the cRIO is still 2 minutes ahead (synchronization interval is set to 5 seconds).
My question is - if I set the clock on cRIO manually to be 2 minutes ahead, will it always be 2 minutes ahead, i.e. will it be synchronized like that? Or SNTP synchronization is not working well?
If synchronization is working well (i.e. it synchronizes 2 minutes ahead because of my manual intervention), how can I test that synchronization is working well during runtime?
Also, I've read somewhere that after synchronization fails to connect with SNTP server 5 times, it won't try ever again. Is this true, and if it is how can I change this?
Best,
Marko.

UPDATE:
I did a test with 2 cRIO devices. Both of them are configured to synchronize with NTP server, and they synchronized successfully on reboot. Then I manually changed times on both of them (not long after reboot), where I set the first cRIO to be 20 seconds ahead NTP server time, and the second cRIO to be 20 seconds behind NTP server time. After 12 hours of runtime, times on both cRIO devices are still 20 seconds ahead/behind NTP server time. Time synchronization update interval was set to 10 seconds on both of them.
Now I'm confued how time synchronization works on cRIO devices. As I see it, there are two possibilites: (i) clocks were synchronized on reboot, and shortly after that I manually changed the clocks to be 20 seconds ahead/behind NTP server time - maybe cRIO now "thinks" that this is normal situation, i.e. to be 20 seconds ahead/behind; or (ii) NTP time synchronization works only on reboot.
In another thread, I read that after 5 failed attemtps to connect to the NTP server, cRIO will quit trying. I'm not sure what does this mean. If it means that cRIO will never again try to connect to the NTP server, this is not good since there is no possibility to define a backup NTP server using ni-rt.ini configuration file. If it means that the cRIO will, at each update event (in my case every 10 seconds), try to connect up to 5 times then this is OK.
If I really have a problem with "automatic" time synchronization using NTP via ni-rt.ini configuration file, would you suggest that I do this synchronization programmatically? What is the expected time synchronization accuracy in this case? Another upside of this approach is possibility of defining backup NTP servers. There are few good threads explaining how to do this: https://decibel.ni.com/content/docs/DOC-36432 , https://decibel.ni.com/content/docs/DOC-26987
I'm sorry to have so much questions, but the documentation on NI TimeSync via SNTP is very poor. All I was able to find was this: http://digital.ni.com/public.nsf/allkb/F2B057C72B537EA2862572D100646D43
Best,
Marko.

Cisco CUCM NTP documentation/requirements

Hello all,
Just wondering about the "actual" NTP clock Stratum version requirements when
installing Cisco CUCM. As the three sources below show varying results;
So first we have the install guides;
Note
Cisco recommends that you use an external NTP server to ensure accurate system time on the first node. Ensure the external NTP server is stratum 9 or higher (meaning stratums 1-9). Subsequent nodes in the cluster will get their time from the first node.When you are installing Cisco Unity Connection on a virtual machine, you must specify an external NTP server.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/8_6_1/install/cmins861.html#wp804989
Then the SRND;
Unified CM automatically synchronizes the NTP time of all subscribers in the cluster to the publisher. During installation, each subscriber is automatically configured to point to an NTP server running on the publisher. The publisher considers itself to be a master server and provides time for the cluster based on its internal hardware clock unless it is configured to synchronize from an external server. Cisco highly recommends configuring the publisher to point to a Stratum-1, Stratum-2, or Stratum-3 NTP server to ensure that the cluster time is synchronized with an external time source.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/netstruc.html#wpxref14097
And finally the NTP White Paper;
For Cisco Unified CallManager Versions 5.0 and later:
– Manual configuration of the ntpd.conf file is not allowed.
– Cisco Unified CallManager prompts the administrator to specify the external NTP server at publisher installation and automatically populates the ntpd.conf file on the publisher server.
– The ntpd.conf files of all other cluster servers are automatically configured to point to the publisher as the NTP source.
• Configure the publisher to point to a traceable stratum 1 clock source.
• Configure network latency between the publisher and the dedicated clock source so that it is within 40 milliseconds round-trip time (RTT).
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6788/vcallcon/ps556/prod_white_paper0900aecd8037fdb5.html
Thanks for any light you can shed on this.
Cheers!
Rob
"Spend your life waiting,
for a moment that just don't come,
Well, don't waste your time waiting"
-Springsteen

Leo,
Do you have reference for this.
Still murky waters:
In 9.1 release Stratum 5 no longer enforced.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/9_1_1/CUCM_BK_RD7D4696_00_cucm-release-notes-911a/CUCM_BK_RD7D4696_00_release-notes-for-cisco-unified_chapter_0110.html
External NTP Server Requirements
The procedure "Set up first node" has been updated to remove the requirement that the external NTP server be Stratum 5 or higher. When you configure the first node, Cisco recommends configuring the publisher to point to a Stratum 1, Stratum 2, or Stratum 3 NTP server to ensure that the cluster time is synchronized with an external time source.

OAM Webgate 10.1.4.2 BP7 installation on RHEL5 2.6.18-92.el5 x86_64 ?

Hello,
Is it possible to install OAM Webgate 10.1.4.2.0 Bundle Patch 7 on Linux RHEL5 X86_64 (2.6.12-92.el5 x86_64 ?.
If yes what is the procedure to follow?
The “Oracle Identity Management 10g Release 3 (10.1.4.x) Certification Matrix .xls” claims it’s certified but we are not able to complete the installation.
During the first installation with the 10.1.4.0.1 media (Oracle_Access_Manager10_1_4_0_1_linux_APACHE2_Webgate) the installer said it was unable to configure the WebGate … So we continue anyway apply the Oracle_Access_Manager_10_1_4_2_0_Patch_linux_APACHE2_WebGate patch set and after the Oracle_Access_Manager_10_1_4_2_0_BP07_Patch_linux_APACHE2_WebGate bundle patch.
After patches application we tried to launch oblix/tools/start_configureWegate but we had a “cannot open shared object file” on libnsl.so.1..
Commenting the “export LD_ASSUME_KERNEL=2.4.19” allows the tools to be launched but after generating the certificate (simple mode) it stays stuck on “Preparing to connect to Access Server. Please wait”…
Best regards,
EDIT:
After a long time waiting on "Preparing to connect to Access Server. Please wait" the configureWebGate finally returned: "Access Server you specified ins currently down. Pleas check your Access Server"
Well looking at the Diagnostics in System management console shows the corresponding Access Server up ...
So I'm afraid it is not possible to make Webgate working on RHEL5 x86_64 :(
If someone makes it work please tell me !
Edited by: Laurent_ch1258 on May 22, 2009 4:09 PM

Hello,
Thanks Pramod for your advice,
You were right the first issue was due to a clock difference (I didn't figure out the NTP synchronisation was broken with our RHEL5 64bit test VM)
Well after correctly configuring clock synchronization with NTP, I run the configurewebgate and successfully configure it :)
Anyway after configuring my Apache (64bits) to handle the webgage I received the following error when starting it:
../oblix/apps/webgate/bin/webgatessl.so: wrong ELF class: ELFCLASS32
--> webgate.so / webgatessl.so are compiled with 32bits libs
I tried several time the installation and I'm sure I provided the 64bits libgcc_s.so.1 and libstdc++.so.5 during the initial install... but even before applying the patchs an ldd on webgate.so / webgatessl.so shows they are linked to the 32 bits libs...
I browse metalink to see if there is a dedicated 64bits patch for BP7 or BP8... but I found nothing
So I'm still not able to make it works on a RHEL5 64 bits... so I do not see why it is certified in oracle_access_manager_certification_10.1.4_r3_matrix.xls in webgate sheet.
I will open a call and let you know...
Best regards,

How to configure time synchronization for two NTP servers

We have IOSXR 4.2.1 on routers CRS3 and ASR9K with all recomended SMUs; we need to configure the time synchronization for two NTP servers with the configuration below, but the routers became unstable; synchronize with one NTP servers for some time, then switch to other NTP server, and keep doing this. Anyone know why this behavior?
ntp
authentication-key 1 md5 encrypted 01070F074F0A05
authenticate
trusted-key 1
server 10.192.32.32 prefer
server 10.192.32.33
source Loopback50
update-calendar
RP/0/RP0/CPU0:DFCRSDTC1#sh log | i ntp
Wed Jul 10 09:37:04.621 BRSPO
RP/0/RP0/CPU0:Jul 4 21:29:18 : ntpd[256]: %IP-IP_NTP-5-SYNC_LOSS : Synchronization lost : 10.192.32.32 : Peer unreachable or clock selection failed
RP/0/RP0/CPU0:Jul 4 21:29:18 : ntpd[256]: %IP-IP_NTP-5-HP_CONN_LOST : High priority NTP peer connection lost - Stratum 2->15.
RP/0/RP0/CPU0:Jul 4 21:29:18 : ntpd[256]: %IP-IP_NTP-5-ALL_CONN_LOST : All NTP peer connections failed.
RP/0/RP0/CPU0:Jul 4 21:29:27 : ntpd[256]: %IP-IP_NTP-5-HP_CONN_RECOVERED : High priority NTP peer connection recovered - Stratum 15->2.
RP/0/RP0/CPU0:Jul 4 21:30:21 : ntpd[256]: %IP-IP_NTP-5-SYNC_LOSS : Synchronization lost : 10.192.32.32 : Peer unreachable or clock selection failed
RP/0/RP0/CPU0:Jul 4 21:30:21 : ntpd[256]: %IP-IP_NTP-5-HP_CONN_LOST : High priority NTP peer connection lost - Stratum 2->15.
RP/0/RP0/CPU0:Jul 4 21:30:21 : ntpd[256]: %IP-IP_NTP-5-ALL_CONN_LOST : All NTP peer connections failed.
RP/0/RP0/CPU0:Jul 4 21:31:36 : ntpd[256]: %IP-IP_NTP-5-HP_CONN_RECOVERED : High priority NTP peer connection recovered - Stratum 15->2.
RP/0/RP0/CPU0:Jul 4 21:35:56 : ntpd[256]: %IP-IP_NTP-5-SYNC_LOSS : Synchronization lost : 10.192.32.33 : Peer unreachable or clock selection failed
RP/0/RP0/CPU0:Jul 4 21:35:56 : ntpd[256]: %IP-IP_NTP-5-HP_CONN_LOST : High priority NTP peer connection lost - Stratum 2->15.
RP/0/RP0/CPU0:Jul 4 21:35:56 : ntpd[256]: %IP-IP_NTP-5-ALL_CONN_LOST : All NTP peer connections failed.
RP/0/RP0/CPU0:Jul 4 21:40:11 : ntpd[256]: %IP-IP_NTP-5-HP_CONN_RECOVERED : High priority NTP peer connection recovered - Stratum 15->2.
RP/0/RP0/CPU0:Jul 4 21:50:52 : ntpd[256]: %IP-IP_NTP-5-SYNC_LOSS : Synchronization lost : 10.192.32.33 : System clock selection failed
RP/0/RP0/CPU0:Jul 4 21:50:52 : ntpd[256]: %IP-IP_NTP-5-HP_CONN_LOST : High priority NTP peer connection lost - Stratum 2->6.
RP/0/RP0/CPU0:Jul 4 21:59:26 : ntpd[256]: %IP-IP_NTP-5-HP_CONN_RECOVERED : High priority NTP peer connection recovered - Stratum 6->2.
RP/0/RP0/CPU0:Jul 4 22:25:07 : ntpd[256]: %IP-IP_NTP-5-SYNC_LOSS : Synchronization lost : 10.192.32.33 : System clock selection failed
RP/0/RP0/CPU0:Jul 4 22:25:07 : ntpd[256]: %IP-IP_NTP-5-HP_CONN_LOST : High priority NTP peer connection lost - Stratum 2->6.
RP/0/RP0/CPU0:Jul 4 22:56:16 : ntpd[256]: %IP-IP_NTP-5-SYNC_LOSS : Synchronization lost : 10.192.32.33 : Peer unreachable or clock selection failed
RP/0/RP0/CPU0:Jul 4 22:56:16 : ntpd[256]: %IP-IP_NTP-5-ALL_CONN_LOST : All NTP peer connections failed.

Hi Claudio, that ddts is pretty generic to be honest but yes it is filed to address sync issues in the XR NTP algo.
The thing is that XR ntp clock selection is a bit different then iOS and follows the specs very closely which results in this erroneous loss behavior.
For instance, you could also see this issue with a sync loss if the update time is only 500msec off what it was before and that will result in a ntp sync loss rather then adjusting to it.
Also I wanted to mention that the ntp prefer is a bit of a misnomer in XR (since it follows the specs differently then IOS) and this knob was taken over from IOS really.
You might get some joy if you set it to one server only and see if that helps?
regards
xander

Synchronize with External NTP server.

Dear All Good morning,
Environment:
SunOS CSF-2 5.10 Generic_138888-03 sun4u sparc SUNW, Sun-Fire-V245 system.
Sun Cluster 3-2 Two node.
Question:
How to Synchronize Cluster timing with external NTP server/device? If external NTP device is down will have any impact in the cluster setup?

epmuneer wrote:
Question:
How to Synchronize Cluster timing with external NTP server/device?The configuration for NTP on Solaris Cluster is explained here:
[http://docs.sun.com/app/docs/doc/820-4676/cacbdgeg?l=en&a=view|http://docs.sun.com/app/docs/doc/820-4676/cacbdgeg?l=en&a=view]
and
[http://docs.sun.com/app/docs/doc/820-4677/cbhijhbh?l=en&a=view|http://docs.sun.com/app/docs/doc/820-4677/cbhijhbh?l=en&a=view]
If external NTP device is down will have any impact in the cluster setup?You should configure the cluster nodes as peers as well as getting the time from the external NTP server.
If the external NTP server fails, then time will drift, but at least the cluster nodes keep themselves in sync to have a consistent view.
Regards
Thorsten

Synchronize RT target using NTP

Hello,
I would like to synchronize my system, composed of several RT target running Pharlap OS, with a NTP server located on a Windows 7 host computer.
I found some examples about how to do it using System Configuration Set Time VI.
I am considering calling this VI in a model or a Custom Device. Is it a right way to do it or is there better ?
More generally, is there any disadvantage of adjusting the clock during execution ?

If you can use LV2010 then use Network Streams, otherwise consider making your own tcpip communications vi. I would package up the data with a SOF,Payload, EOF, CRC and then require the receiver to return a verification message to complete the transfer.

NTP synchronization, slewing for large period of time ?

Hi to all
First to all I have to say thet I'm new to solaris,
I have the following problem :
I have to change the server's time , but changing it at one time via date or rdate commands is not an option because there are a lot of statistics going on there and it will make a mess ,
I have to move the clock about 1/2 hour forward and that's a big difference to do it at one time .
So I read about slewing and thought about using adjtime() , which is a function (and I could not get it how to use it , it's not a command !),
I think this is the way to solve my problem : to change the time in a bigger period of time : a couple of days or more, so the mashine to be able to make it more polite : to catch up the difference.
The machine is also NTP server.
So any help will be appreciated
Thanks in advance

man date

(S)NTP synchronization on SG300 access switches?

Hi,
In our network two Domain Controllers are configured as the central (S)NTP Servers. For a switch in Layer 3 mode it is quit easy to synchronise with these (S)NTP Servers. But what is actually the best approach for access switches in layer 2 mode, that are connected to the layer 3 switch? The only IP Address they have are part of the management VLAN ID 1 which is not routable. I am actually looking for something like a broadcast without having to put a NTP Server in management vLAN.
Boudewijn

Is your layer 3 switch the gateway for your vlans? Vlan 1 can be routed, the only restriction to this would be if you do not have any routes for vlan1. If your NTP server and layer 2 switch points their default gateway at your layer 3 switch, the layer 3 switch can route traffic across that way.
It really depends how you have the network setup and what device is handling the routing for you on the local network.

About License synchronization on 4507R-E

hello ,everyone.
i got a mission that i need to sychronous a license from an old SUP7-E to a new one, the license level is ipbase ,and it has been installed on the chassis 4507-E,then i looked up the documents from cisco.com and find a way to make a license synchronization in my case.
step 1.
change the license boot level from ipbase to lanbase
conf t
no license boot level ipbase
step2.
backup the license to a usb disk
license save usb0:ipbase.lic
license save cre usb0:ipbase1.lic
then check it out to make sure its avaliability .
more usb0:ipbase.lic
more usb0:ipbase1.lic
delete the license after reload it.
reload
license clear ipbase
yes
write memory
reload
then wait the two supervisors to became a RPR mode.
install license on active SUP7-E and restore its licence boot level
license install usb0:ipbase.lic
license install usb0:ipbase1.lic
conf t
license boot level ipbase
exit
write memory
after they have been completely synchronizd to RPR mode,reload standby Supervisor.
hw module 4 reload
after the two supervisors finish the synchronization once again,
reload the active supervisor
reload
press ctrl+c during the period of active supervisor restart to make the system enter rommon prompt.
connect the console cable to the standby supervisor ,and excute the following commands:
conf t
redundancy
mode sso
exit
no license boot level ipbase
end
write memory
reload
in this case ,the 4507R-E is running VSS with one other 4507R-E which also has one SUPE-7 ,i need to use one of them
to synchronous ipbase license with a new SUP7-E .do i need to convert it from VSS mod to switch mode at first?then make it
with the above mentioned method. thanks.

I still have not found anything on this matter. Anyone?

Windows 2008 R2 Domain Controller (PDC) - NTP server - time showing local CMOS clock

I'm having issues setting an external source on a Windows 2008 R2 domain controller (PDC emulator role for the domain)
Here is the output showing its source is the Local CMOS clock.
C:\Windows\System32>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 1 (primary reference - syncd by radio clock)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0000000s
Root Dispersion: 10.0000000s
ReferenceId: 0x4C4F434C (source name: "LOCL")
Last Successful Sync Time: 06/11/2014 15:44:15
Source: Local CMOS Clock
Poll Interval: 6 (64s)
1) I have performed the following on the DC with the PDC role:
net stop w32time
w32tm /config /syncfromflags:manual /manualpeerlist:"0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org"
w32tm /config /reliable:yes
net start w32time
w32tm /query /configuration
[Configuration]
EventLogFlags: 2 (Local)
AnnounceFlags: 5 (Local)
TimeJumpAuditOffset: 28800 (Local)
MinPollInterval: 6 (Local)
MaxPollInterval: 10 (Local)
MaxNegPhaseCorrection: 172800 (Local)
MaxPosPhaseCorrection: 172800 (Local)
MaxAllowedPhaseOffset: 300 (Local)
FrequencyCorrectRate: 4 (Local)
PollAdjustFactor: 5 (Local)
LargePhaseOffset: 50000000 (Local)
SpikeWatchPeriod: 900 (Local)
LocalClockDispersion: 10 (Local)
HoldPeriod: 5 (Local)
PhaseCorrectRate: 7 (Local)
UpdateInterval: 100 (Local)
[TimeProviders]
NtpClient (Local)
DllName: C:\Windows\System32\w32time.DLL (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)
AllowNonstandardModeCombinations: 1 (Local)
ResolvePeerBackoffMinutes: 15 (Local)
ResolvePeerBackoffMaxTimes: 7 (Local)
CompatibilityFlags: 2147483648 (Local)
EventLogFlags: 1 (Local)
LargeSampleSkew: 3 (Local)
SpecialPollInterval: 3600 (Local)
Type: NTP (Local)
NtpServer: 0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org (Local)
NtpServer (Local)
DllName: C:\Windows\System32\w32time.DLL (Local)
Enabled: 1 (Local)
InputProvider: 0 (Local)
AllowNonstandardModeCombinations: 1 (Local)
VMICTimeProvider (Local)
DllName: C:\Windows\System32\vmictimeprovider.dll (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)
But still showing the output:
C:\Windows\System32>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 1 (primary reference - syncd by radio clock)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0000000s
Root Dispersion: 10.0000000s
ReferenceId: 0x4C4F434C (source name: "LOCL")
Last Successful Sync Time: 06/11/2014 15:58:45
Source: Local CMOS Clock
Poll Interval: 6 (64s)
2. If I resync and rediscover the following error appears:
w32tm /resync /rediscover
Sending resync command to local computer
The computer did not resync because no time data was available.
3. I've also clearing the current time config, by
net stop w32time
w32tm /unregister
w32tm /register
net start w32time
But no change, it still shows the Local CMOS clock.
4. This event is showing
Log Name: System
Source: Microsoft-Windows-Time-Service
Date: 06/11/2014 15:43:30
Event ID: 12
Task Category: None
Level: Warning
Keywords:
User: LOCAL SERVICE
Computer: domaincontroller1
Description:
Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source.
It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy.
If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" />
<EventID>12</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-11-06T15:43:30.465619200Z" />
<EventRecordID>77295</EventRecordID>
<Correlation />
<Execution ProcessID="256" ThreadID="2056" />
<Channel>System</Channel>
<Computer>domaincontroller1</Computer>
<Security UserID="SID" />
</System>
<EventData Name="TMP_EVENT_DOMAIN_HIERARCHY_ROOT">
</EventData>
</Event>
5. If I perform the below it appears DC2 is having problems but I'm not sure if related.
C:\w32tm /monitor
DC1.domain.local *** PDC ***[192.168.1.1:123]:
ICMP: 0ms delay
NTP: +0.0000000s offset from DC1.domain.local
RefID: 'LOCL' [0x4C434F4C]
Stratum: 1
DC2.domain.local[192.168.1.2:123]:
ICMP: 0ms delay
NTP: -110.4925481s offset from DC1.domain.local
RefID: (unspecified / unsynchronized) [0x00000000]
Stratum: 0
DC3.domain.local[192.168.2.1:123]:
ICMP: 0ms delay
NTP: -0.0256084s offset from DC1.domain.local
RefID: DC1.domain.local [192.168.1.1]
Stratum: 2
DC4.domain.local[192.168.2.4:123]:
ICMP: 0ms delay
NTP: -0.0011524s offset from DC1.domain.local
RefID: 80.84.77.86.rev.sfr.net [86.77.84.80]
Stratum: 2
Warning:
Reverse name resolution is best effort. It may not be
correct since RefID field in time packets differs across
NTP implementations and may not be using IP addresses.
Any help would be much appreciated. Thanks.
Craig Brand

I suspected some issue with AV so uninstalled.
To resolve the Access Denied I followed these steps:
stop w32time
w32tm /unregister
reboot
regsvr32 /u w32time.dll
w32tm /register
sc query w32time -- you should see that the service is set to
shared mode -- this is presumably how it should be -- if you try to start right now, you'll get the expected 1290 SID-related error
reboot
w32time should now automatically start at boot up and be running -- that was my result -- it's running as shared, started on its own, and I can do the w32tm /query commands successfully
After rebooting the time service started.
I then repeated the steps:
net stop w32time
w32tm /config /syncfromflags:manual /manualpeerlist:"0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org"
w32tm /config /reliable:yes
net start w32time
w32tm /query /configuration
And all worked. I'll wait a short while to see if this fixes the issue. I also have am SA case with MS so will confirm fix when resolved.
Craig Brand

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?

C4500 VSS quad - incorrect config synchronisation

Testing two C4510R+E chassis VSS in quad supervisor 7-E configuration.
All 4 sups. had the same basic configuration – converted to VSS and added VSL ports (same in each chassis).
During testing I inserted one more linecard to each chassis and added one port from the card to VSL. All worked fine. Then I removed active sup., booted previously ROMMON booted sup. to IOS and config was synchronized from ACTIVE to STANDBY sup. and VSL config was updated. Again, all worked fine.
But the I realized incorrect seting of calendar so I began to change UTC calendar time from factory to local setting. Change active - active synchronizes to standby, switchover, boot second sup. etc. But after second switchover, on ACTIVE sup console appeared warning, that config was synchronized from STANDBY to ACTIVE!
First I was thinking about version revisions of configuration – higher revision would have higher priority, but did not find any information about it so could the time synchronization be problem.? I was changing approx. +7h from factory settings.
Does anybody have any experience with this behavior?
Note: the log bellow is from Active sup. that had factory time setting and Standby sup. (probably) had updated time.
*Jul 30 07:41:53.631: %C4K_REDUNDANCY-6-MODE: ACTIVE supervisor initializing for sso mode
*Jul 30 07:41:56.632: %C4K_IOSMODPORTMAN-6-MODULEONLINE: Module 5 (WS-X45-SUP7-E S/N: CAT1823L0UY Hw: 2.1) is online
*Jul 30 07:41:56.678: %C4K_REDUNDANCY-6-MODE: ACTIVE supervisor initializing for sso mode
*Jul 30 07:41:57.190: %C4K_REDUNDANCY-3-COMMUNICATION: Communication with the peer Supervisor has been established
*Jul 30 07:42:07.174: %C4K_REDUNDANCY-5-CONFIGSYNC: The bootvar has been successfully synchronized to the standby supervisor
*Jul 30 07:42:07.175: %C4K_REDUNDANCY-5-CONFIGSYNC: The config-reg has been successfully synchronized to the standby supervisor
*Jul 30 07:42:07.176: %C4K_REDUNDANCY-5-CALENDAR: The calendar has been successfully synchronized to the standby supervisor for the first time
*Jul 30 07:42:07.176: %C4K_REDUNDANCY-5-CONFIGSYNC: The startup-config has been successfully synchronized to the standby supervisor
*Jul 30 07:42:07.696: %C4K_REDUNDANCY-5-CONFIGSYNC: The private-config has been successfully synchronized to the standby supervisor
*Jul 30 07:42:08.725: %C4K_REDUNDANCY-5-CONFIGSYNC_RATELIMIT: The vlan database has been successfully synchronized to the standby supervisor
******************** WARNING ********************
* Config on Active changed due to new info *
* from Standby. Saving original config on *
* Active as startup-config.saved_vs-TIMESTAMP. *
switchport
^
% Invalid input detected at '^' marker.
Saved startup config to bootflash: ****
Thanks.
Jarek

Synchronization of NTP in VSS

Similar Messages

Maybe you are looking for