SET TIME/CLUSTER and NTP / DTSS

[Jan v.d. Boogaard]

Hello,
Can SET TIME /CLUSTER give problems when using NTP or DTSS ? Or can they coexist ?

[Wim Van den Wyngaert]

Set time is not enabled when using DTSS.
Hope NTP reacts the same.

(help/mes TIMENOTSET)

Wim

[Ian Miller.]

NTP does not seem to stop SET TIME (unlike DTSS) so it is possible to set the time and then NTP attempt to change the time back to what it thinks the correct time is.

[Petr Spisek]

Hi,
it is not good idea to change time when time-synchronization is runnig. If you really need to change time, stop these services before.

Petr

[Michael D. Feeney · Accepted solution]

You really shouldn't have to set the time once you get NTP or DTSS configured on the cluster. They will keep your system clocks synchronized.

If your time is too far off, you should stop NTP or DTSS like Petr said and then set the time.

You aren't running both NTP and DTSS are you? You should only have one of them running.

Mike

[Ian Miller.]

NTP can be a time provider to DTSS.

[Michael D. Feeney]

Ok, What I mean is that you should have only one of those applications synchronize the clock on any particular node.

If your cluster has only one node that can run NTP and the other nodes are running DECnet, you can use the NTP node to sync with an internet time server. Your other nodes then use DTSS to sync with the NTP node.

But that is two application that you have to manage. If all of your nodes can run NTP, then you only have one application to manage.

Mike

[Jan v.d. Boogaard]

Thanks.
We're running NTP on all nodes in the cluster. We;'re not running DTSS. My conclusion is that SET TIME/CLUSTER is not necessary in that situation.

[Petr Spisek]

If you have running NTP on all cluster members, you don't need synchronize by command SET TIME/CLUSTER.

Petr