DTSS Issue

[Wim Van den Wyngaert]

IMO the servers have nothing to do with the problem because time change is local to the machine.

Make sure that all DTS processes are gone when you restart.

There also was a problem that "default" is shown when the next change was not in the current year. You could wait for next year and see if it improves.

Wim

[Oswald Knoppers_1]

10.900 is a node on your network confugured als DTSS server.

However this node is not sure about the correct time:

Current Time = 2009-10-26-09:33:23.450+01:00Iinf

The 'inf' behind the 'I' (Inaccuracy) means that your time source has no idea as to how accuratute its time is.

Your nodes do get the clocks synchronized.

Oswald

[Superstar]

Hi Volker,

I have totally 5 servers among that 2 are DTSS servers and and other 3 are clerk, this is output taken from one of the server and you see here the server required is 3, will it be the cause of this issue?

Can you please tell me who do adjust this server parameter?

Node 0 DTSS
at 2009-10-26-14:07:35.255+01:00Iinf

Status

Local Time Differential Factor = +0-01:00:00.000Iinf
Acting DECnet Courier Role = Courier
Time Provider Present = False
Next TDF Change =
Current Time = 2009-10-26-14:07:35.255+01:00Iinf
Uid = A4CBE991-C163-11DE-87C4-AA000400872B
Last Synchronization = 2009-10-26-14:00:19.510+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
Maximum Inaccuracy = +0-00:00:00.200Iinf
Servers Required = 3
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
DECnet Courier Role = Backup 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 = DTSS_GlobalTimeServers
Automatic TDF Change = True
Clock Resolution = 1048500

Counters

Creation Time = 2009-10-25-12:40:57.832+01:00Iinf
Local Times Not Intersecting = 0
Server Times Not Intersecting = 0
Different Epochs Detected = 0
Too Few Servers Detected = 317
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 = 0
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 = 808
Global Responses Sent = 0

John

[Superstar]

Hi Oswald,

Till last time I noticed next tdf value changes automaticall after time change but not this time thats Y I am concerned.

John

[Volker Halle]

John,

this node is a DTSS Server. It is set to require a total of 3 DTSS servers on the lan to correctly synch it's time. If you only have 2 DTSS servers on your LAN, you need to modify this in SYS$MANAGER:NET$DTSS_SERVER_STARTUP.NCL by adding a line:

SET DTSS SERVERS REQUIRED = 2

and restarting DTSS. This will also eliminate the DTSS OPCOM messages complaining about insufficient DTSS servers.

Volker.

[Superstar]

Hi Volker,

Rightly said if we have mistach in server count we will get opcom message but I couldn't see any and do you have any idea from where its takes the required server count as 3? Also, will a non vms server (say unix server)can act as a dtss server for vms?

John.

[Volker Halle]

John,

Servers Required = 3 is the installation default. Only systems implemeting DECnet-Plus and DTSS can act as DTSS servers, so this excludes U*X systems.

OpenVMS TCPIP also supportes NTP, this may be an alternative to DTSS. It would require setting the system parameter AUTO_DLIGHT_SAV=1 (available in OpenVMS Alpha V7.3 or higher) for DST switching.

Volker.

[Superstar]

Hi Volker,

Yes that is the alternative I am also thinking of now as Auto_DLIGHT_SAV doesn't have any relation with DTSS isn't it? but I am curious to know what went wrong with DTSS all of a sudden after yesterday DST change.

John

[Volker Halle]

John,

note that both systems you've shown running DTSS never completed any synchronizations (as shown by Synchronizations Completed = 0).

I've checked a couple of OpenVMS V7.3-2 systems running DECnet-Plus and DTSS and I've found this:

DECnet-Plus V7.3-2 un-patched and ECO 2 show

DECnet-Plus V7.3-2 ECO 3 shows correct next TDF change time.

I didn't check the OpenVMS patch level, but I would suggest, that you upgrade to the latest DECnet-Plus V7.3-2 ECO 3.

Volker.

[Superstar]

Hi Volker,

Any idea where can I get the kits?

John