topic Re: DTSS Issue in Operating System - OpenVMS

DTSS Issue

Superstar — Mon, 26 Oct 2009 08:05:08 GMT

In all our OpenVMS V7.3-2 servers after the recect DST time change Next TDF Value in DTSS shows as

Node 0 DTSS
at 2009-10-26-09:33:23.450+01:00Iinf

Status

Local Time Differential Factor = +0-01:00:00.000Iinf
Next TDF Change =
Current Time = 2009-10-26-09:33:23.450+01:00Iinf
Uid = 7B87D285-C11C-11DE-957A-00101810010B
Last Synchronization = 2009-10-26-09:33:11.271+01:00Iinf
State = On

Characteristics

Error Tolerance = +0-00:10: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:10:00.000Iinf
Type = Clerk
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 = LOCAL:.DTSS_GlobalTimeServers
Automatic TDF Change = True
Clock Resolution = 976500

Counters

Creation Time = 2009-10-25-04:11:34.335+01:00Iinf
Local Times Not Intersecting = 0
Too Few Servers Detected = 0
Too Many Servers Detected = 0
Protocol Mismatches Detected = 0
Time Representation Mismatches Detected = 0
Invalid Messages Detected = 0
Clock Settings = 1
Time Differential Factor Settings = 0
System Errors Detected = 0
Synchronizations Completed = 0
Enable Directives Completed = 1
Disable Directives Completed = 0
Insufficient Resources Detected = 0

I ran net$configure and tried to redifine the time logicals but of no use can someone please help to fix this issue

Re: DTSS Issue

Wim Van den Wyngaert — Mon, 26 Oct 2009 08:16:38 GMT

mc ncl show impl
sh log *timez*
sh log *dts*

Found this in eco 3.

This release has a fix to display the value of the
"Next TDF change" field as "" when there
is no Daylight Saving Time (DST) for the configured
subregion and to display the time for the next TDF
change when DST is present.

Is your DST setting correct ?

Wim

Re: DTSS Issue

Superstar — Mon, 26 Oct 2009 10:23:34 GMT

Hi,

As far as I know all looks ok for me apart from next tdf and this the first time I see this issue till last time everything was just perfect. There was no changes done on the system.

John>mc ncl show imple
Implementation =
{
[
Name = OpenVMS Alpha ,
Version = "V7.3-2 "
] ,
[
Name = HP DECnet-Plus for OpenVMS ,
Version = "V7.3-2 ECO02 20-OCT-2005 01:56:23.03"
]
}

John>sh log *timez*
"SYS$TIMEZONE_DAYLIGHT_SAVING" = "0"
"SYS$TIMEZONE_DIFFERENTIAL" = "3600"
"SYS$TIMEZONE_NAME" = "MET"
"SYS$TIMEZONE_RULE" = "MET-1MET DST-2,M3.5.0/02,M10.4.0/03"

John>sh log *dts*
(LNM$PROCESS_TABLE)

(LNM$JOB_817B6A40)

(LNM$GROUP_000001)

(LNM$SYSTEM_TABLE)

"ACLEDTSHR_TV" = "ACLEDTSHR"
"DTSCREENSAVERLIST" = "StartDtscreenSwarm StartDtscreenQix StartDtscreenFlame
StartDtscreenHop StartDtscreenImage StartDtscreenLife StartDtscreenRotor StartDt
screenPyro StartDtscreenWorm StartDtscreenBlank"
"DTSS$_SERVICE_ACTIVE" = "DECdts V2.0"
"EDTSHR_TV" = "EDTSHR"

(LNM$SYSCLUSTER_TABLE)

(DECW$LOGICAL_NAMES)

John

Re: DTSS Issue

Volker Halle — Mon, 26 Oct 2009 11:21:12 GMT

John,

you're still at DECnet-Plus V7.3-2 ECO 2. The fix described by Wim is from ECO 3, which you have not yet installed.

Volker.

Re: DTSS Issue

Volker Halle — Mon, 26 Oct 2009 11:24:52 GMT

John,

you may try to restart DTSS:

$ MC NCL DISABLE DTSS
$ MC NCL DELETE DTSS
$ @SYS$STARTUP:DTSS$STARTUP

Volker.

Re: DTSS Issue

Superstar — Mon, 26 Oct 2009 11:43:18 GMT

Hi Volker,

I tried to stop and start DTSS but it doesn't help. I am also not able to locate global server, as I could see required servers is set as 3 in DTSS will be the cause of the issue?

> mc ncl show dtss decnet global server *

Node 0 DTSS Decnet Global Servers *
at 2009-10-26-13:32:25.906+01:00Iinf

command failed due to:
no such object instance

John

Re: DTSS Issue

Volker Halle — Mon, 26 Oct 2009 11:48:06 GMT

John,

GLOBAL SERVER is something else.

Your local servers on your LAN should show up with

NCL> show dtss decnet local server * address

Volker.

Re: DTSS Issue

Oswald Knoppers_1 — Mon, 26 Oct 2009 11:48:24 GMT

You can configure a global server in sys$manager:dtss$config.dat. But you probably do not have one.

Do you have any local servers (i.e. on your local lan)?

Oswald

Re: DTSS Issue

Superstar — Mon, 26 Oct 2009 11:59:30 GMT

Hi Both,

I get this for local server.

> mc ncl show dtss decnet local server *

Node 0 DTSS Decnet Local Servers AA-00-04-00-84-2B (10.900)
at 2009-10-26-13:50:52.186+01:00Iinf

Identifiers

ADDRESS = AA-00-04-00-84-2B (10.900)

John

Re: DTSS Issue

Volker Halle — Mon, 26 Oct 2009 12:02:24 GMT

John,

so you have ONE DTSS server on your local LAN, this is enough as Server Required is 1.

Volker.

Re: DTSS Issue

Wim Van den Wyngaert — Mon, 26 Oct 2009 12:06:58 GMT

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

Re: DTSS Issue

Oswald Knoppers_1 — Mon, 26 Oct 2009 12:07:13 GMT

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

Re: DTSS Issue

Superstar — Mon, 26 Oct 2009 12:26:07 GMT

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

Re: DTSS Issue

Superstar — Mon, 26 Oct 2009 12:35:40 GMT

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

Re: DTSS Issue

Volker Halle — Mon, 26 Oct 2009 12:37:04 GMT

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.

Re: DTSS Issue

Superstar — Mon, 26 Oct 2009 13:06:21 GMT

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.

Re: DTSS Issue

Volker Halle — Mon, 26 Oct 2009 13:14:48 GMT

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.

Re: DTSS Issue

Superstar — Mon, 26 Oct 2009 14:58:31 GMT

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

Re: DTSS Issue

Volker Halle — Mon, 26 Oct 2009 15:43:28 GMT

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.

Re: DTSS Issue

Superstar — Tue, 27 Oct 2009 05:23:46 GMT

Hi Volker,

Any idea where can I get the kits?

John