Time sync issue controllers, CS to Controller vers 6.1 red
Hi!
The sync structure is like this:
A firewall act as an external time source.
An external program NetTime is installed on the CS-servers (CS1-1, CS1-2) collecting the time from the firewall.
The CS-servers Time Server Client Configuration are setup to Allow To Set Time, no other nodes.
We have 3 controllers.
Controller 1 setup:
CS CNCP Clockmaster Order No: 1 CS Protocol Type: SNTP CS Time Set Enabled: False CS Synch Interval: 20 CS SNTP ServerAddr 1: 172.16.80.15 (CS1-1)
CS SNTP ServerAddr 1: 172.16.80.16 (CS1-2)
Controller 2 setup:
CS CNCP Clockmaster Order No: 2 CS Protocol Type: SNTP CS Time Set Enabled: False CS Synch Interval: 20 CS SNTP ServerAddr 1: 172.16.80.15 (CS1-1)
CS SNTP ServerAddr 1: 172.16.80.16 (CS1-2)
Controller 3 setup:
CS CNCP Clockmaster Order No: 0 CS Protocol Type: CNCP CS Time Set Enabled: True CS Synch Interval: 20 CS SNTP ServerAddr 1:
CS SNTP ServerAddr 1:
Using the Clock Synch Status tool in CB we can see that the controllers Mean Diff Time goes between 700-1500us.
Is this normal?
On another site we have Mean Diff Time on the controllers around 50-90us. Never over 100us.
Another question: Under Time Service there is a Special configuration. Here you can enable an external clock master function.
Would this be the same as using the external NetTime program?
BRs Asp
The sync structure is like this:
A firewall act as an external time source.
An external program NetTime is installed on the CS-servers (CS1-1, CS1-2) collecting the time from the firewall.
The CS-servers Time Server Client Configuration are setup to Allow To Set Time, no other nodes.
We have 3 controllers.
Controller 1 setup:
CS CNCP Clockmaster Order No: 1 CS Protocol Type: SNTP CS Time Set Enabled: False CS Synch Interval: 20 CS SNTP ServerAddr 1: 172.16.80.15 (CS1-1)
CS SNTP ServerAddr 1: 172.16.80.16 (CS1-2)
Controller 2 setup:
CS CNCP Clockmaster Order No: 2 CS Protocol Type: SNTP CS Time Set Enabled: False CS Synch Interval: 20 CS SNTP ServerAddr 1: 172.16.80.15 (CS1-1)
CS SNTP ServerAddr 1: 172.16.80.16 (CS1-2)
Controller 3 setup:
CS CNCP Clockmaster Order No: 0 CS Protocol Type: CNCP CS Time Set Enabled: True CS Synch Interval: 20 CS SNTP ServerAddr 1:
CS SNTP ServerAddr 1:
Using the Clock Synch Status tool in CB we can see that the controllers Mean Diff Time goes between 700-1500us.
Is this normal?
On another site we have Mean Diff Time on the controllers around 50-90us. Never over 100us.
Another question: Under Time Service there is a Special configuration. Here you can enable an external clock master function.
Would this be the same as using the external NetTime program?
BRs Asp
Asked 4 months ago
Voted best answer
1
The AC 800M SNTP engine run with high accuracy and will easily spot a poor reference. Check if there are messages output to the Controller Log (SNTP TimeDiff ...).
Most computer clocks are "poor" in comparison (quality of oscillator, lack of temperature compensation, etc.)
I believe CS1-1 time is not stable and it is having secondary downstream effect on the controllers' SNTP client performance.
I recommend that you temporarily disable the NetTime program to have CS-1 "floating" but still serving as a time source for the controllers. Then wait some time and study the effects on the AC 800M Clock Sync Status. Make sure AnnounceFlags is set to Always Reliable in W32Time registry (in case this status was raised thru the NetTime program).
If this improves the situation, the problem is either the NetTime program or your external reference clock.
Next, try using Win32Time Service to slave to the external reference (is is described in chapter 7 of the Network Configuration Users Guide, 3BSE034463-610). In short: enable the NtpClient registry key, use w32tm.exe to setup the necessary parameters and force a resync or restart Windows Time service. Study the events output from Time-Service to Windows Event Log. Make sure W32Time is "happy".
Don't use the 800xA AfwTimeService's External Clock Master function, it is lesser proven and only works using an old Microsoft Windows protocol (not SNTP).
Most computer clocks are "poor" in comparison (quality of oscillator, lack of temperature compensation, etc.)
I believe CS1-1 time is not stable and it is having secondary downstream effect on the controllers' SNTP client performance.
I recommend that you temporarily disable the NetTime program to have CS-1 "floating" but still serving as a time source for the controllers. Then wait some time and study the effects on the AC 800M Clock Sync Status. Make sure AnnounceFlags is set to Always Reliable in W32Time registry (in case this status was raised thru the NetTime program).
If this improves the situation, the problem is either the NetTime program or your external reference clock.
Next, try using Win32Time Service to slave to the external reference (is is described in chapter 7 of the Network Configuration Users Guide, 3BSE034463-610). In short: enable the NtpClient registry key, use w32tm.exe to setup the necessary parameters and force a resync or restart Windows Time service. Study the events output from Time-Service to Windows Event Log. Make sure W32Time is "happy".
Don't use the 800xA AfwTimeService's External Clock Master function, it is lesser proven and only works using an old Microsoft Windows protocol (not SNTP).
Add new comment