| Title: | DTSS_NOTE |
| Moderator: | TUXEDO::BARYIAMES |
| Created: | Mon Jul 31 1989 |
| Last Modified: | Wed May 28 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 624 |
| Total number of notes: | 2671 |
I have a customer with an Inaccuracy problem, he has some system which
have the Inaccuracy value permantly set to Infinity:
Example of UNIX system:
-----------------------
ncl> show dtss all
Node 0 DTSS
AT 1997-03-04-09:40:35.805+01:00I-----
Status
Local Time Differential Factor = +0-01:00:00.000I-----
Acting DECnet Courier Role = NonCourier
Time Provider Present = True
Next TDF Change =1997-03-30-03:00:00.000+02:00I0.000
Current Time =1997-03-04-09:40:35.800+01:00I-----
Uid =18E66184-93D3-11D0-9104-08002B3B6C5D
Last Synchronization =1997-03-04-09:40:24.071+01:00I1.879
State = On
Characteristics
Advertisement Interval = +0-01:30:00.000I-----
Check Interval = +0-01:30:00.000I-----
Epoch Number = 0
Error Tolerance = +0-00:10:00.000I-----
Maximum Inaccuracy = +0-00:00:00.200I-----
Servers Required = 3
Query Attempts = 3
LAN Timeout = +0-00:00:05.000I-----
WAN Timeout = +0-00:00:15.000I-----
Synchronization Hold Down = +0-00:05:00.000I-----
Type = Server
DECnet Courier Role = Backup Courier
Clock Adjustment Rate = 10000000 nsec/sec
Maximum Clock Drift Rate = 100000 nsec/sec
DNA Version = V1.0.0
DTSS Version = V1.1.0
Time Representation Version = V1.0.0
Global Directory = ANDY:.DTSS_GlobalTimeServers
Automatic TDF Change = False
Clock Resolution = 1552000 nsec
Counters
Local Times Not Intersecting = 0
Server Times Not Intersecting = 0
Different Epochs Detected = 0
Too Few Servers Detected = 0
Too Many Servers Detected = 0
Protocol Mismatches Detected = 0
Time Representation Mismatches Detected = 0
Invalid Messages Detected = 0
No Global Servers Detected = 1
Servers Not Responding = 0
Clock Settings = 1
Epoch Changes Completed = 0
Time Differential Factor Settings = 0
System Errors Detected = 0
Synchronizations Completed = 1116
Updates Initiated = 0
Enable Directives Completed = 1
Disable Directives Completed = 0
Insufficient Resources Detected = 0
Time Provider Failures Detected = 0
Local Responses Sent = 2345
Global Responses Sent = 0
Creation Time =1997-03-03-15:33:25.855+01:00I138.711
Example of OpenVMS system:
--------------------------
ncl> show dtss all
Node 0 DTSS
at 1997-03-03-14:50:00.016+01:00Iinf
Status
Current Time =1997-03-03-14:50:00.016+01:00Iinf
Uid =97A4F4C0-9191-11D0-8007-AA0004000228
Last Synchronization =1997-03-03-14:48:43.152+01:00Iinf
State = On
Characteristics
Advertisement Interval = +0-01:30:00.000Iinf
Check Interval = +0-01:30:00.000Iinf
Epoch Number = 0
Error Tolerance = +0-00:10:00.000Iinf
Local Time Differential Factor = +0-01:00:00.000Iinf
Maximum Inaccuracy = +0-00:00:00.200Iinf
Servers Required = 1
Query Attempts = 3
LAN Timeout = +0-00:00:05.000Iinf
WAN Timeout = +0-00:00:15.000Iinf
Synchronization Hold Down = +0-00:05:00.000Iinf
Type = Server
Courier Role = Backup Courier
Acting Courier Role = Courier
Clock Adjustment Rate = 10000000
Maximum Clock Drift Rate = 100000
DNA Version = V1.0.0
DTSS Version = V2.0.0
Time Representation Version = V1.0.0
Global Directory = EBS:.DTSS_GlobalTimeServers
Time Provider Present = False
Automatic TDF Change = True
Next TDF Change =1997-03-30-01:59:59.999+01:00I0.000
Clock Resolution = 10000000
Counters
Creation Time =1997-02-28-17:39:29.200+01:00Iinf
Local Times Not Intersecting = 0
Server Times Not Intersecting = 0
Different Epochs Detected = 0
Too Few Servers Detected = 0
Too Many Servers Detected = 0
Protocol Mismatches Detected = 0
Time Representation Mismatches Detected = 0
Invalid Messages Detected = 0
No Global Servers Detected = 0
Servers Not Responding = 0
Clock Settings = 1
Epoch Changes Completed = 0
Time Differential Factor Settings = 0
System Errors Detected = 0
Synchronizations Completed = 0
Updates Initiated = 0
Enable Directives Completed = 1
Disable Directives Completed = 0
Insufficient Resources Detected = 0
Time Provider Failures Detected = 0
Local Responses Sent = 5316
Global Responses Sent = 429
On the UNIX system is running the /usr/examples/dtss/dtss_ntp_provider
program.
Does the syntax "1997-03-04-09:40:35.800+01:00I-----" mean that the
Inaccuracy is Infinity ?
What does Inaccuracy=Infinity mean and when can I have this value ?
Tank you very much for the answers.
Kind regards
Andrea.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 621.1 | His TP is broken | TWICK::PETTENGILL | mulp | Wed Mar 05 1997 00:11 | 10 |
This is the key to the problem (from your posting):
Time Provider Present = True
It would appear that an inaccuracy is being computed and then wiped out.
Current Time =1997-03-04-09:40:35.800+01:00I-----
Last Synchronization =1997-03-04-09:40:24.071+01:00I1.879
The thing you need to do is get the event logging enabled for all DTSS
events and take a look at the event log. I'm sure that it will have
some interesting information in it.
| |||||
| 621.2 | ZURCLO::LUONGO | Fri Mar 07 1997 04:41 | 2 | ||
| |||||
| 621.3 | event dispatcher output | ZURCLO::LUONGO | Fri Mar 07 1997 04:50 | 52 | |
I have followed the istractions and the output of the event dispatcher
on the DUNIX 4.0a system (with dtss_ntp_provider) is:
...
Event: Clock Set
from: Node ANDY:.m8sole DTSS
at : 1997-03-07-10:33:58.660+01:00I2.786
Old Time = <undefined>
New Time = <undefined>
Event: Synchronization Completed
from: Node ANDY:.m8sole DTSS
at : 1997-03-07-10:34:02.745+01:00I2.786
Computed time = 1997-03-07-10:34:02.739+01:00I2.785
Clock Adjustment = -0-00:00:00.000I0.000
Event: Synchronization Completed
from: Node ANDY:.m8sole DTSS
at : 1997-03-07-10:34:03.643+01:00I2.786
Computed time = 1997-03-07-10:34:03.637+01:00I2.785
Clock Adjustment = -0-00:00:00.001I0.000
Event: Clock Set
from: Node ANDY:.m8sole DTSS
at : 1997-03-07-10:34:03.643+01:00I2.786
Old Time = <undefined>
New Time = <undefined>
Event: Synchronization Completed
from: Node ANDY:.m8sole DTSS
at : 1997-03-07-10:34:24.868+01:00I2.786
Computed time = 1997-03-07-10:34:24.861+01:00I2.785
Clock Adjustment = -0-00:00:00.000I0.000
...
Please, can you explain me this output ?
Andrea.
| |||||
| 621.4 | TWICK::PETTENGILL | mulp | Fri Mar 14 1997 01:54 | 10 | |
My explanation is that something is broken. I don't know whether the problem is DU, DECnet for DU, or something else. It might be that your setup of the node has somehow triggered some bug so that correcting the setup might fix the problem, but off hand, some bit of software is broken. Can you do ? ncl sho all ncl sho dtss all | |||||