[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference smurf::ase

Title:	ase

Moderator:	SMURF::GROSSO

Created:	Thu Jul 29 1993
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2114
Total number of notes:	7347

1883.0. "Again on ntp. what about high availability clock?" by GRIFUN::BENVI () Fri Feb 14 1997 08:51

Hi all,
	I have a configuration made by two AlphaServers in DECSafe and several client
Workstations. Time must be synchronzied inthe above configuartion and we thouhgt to use
NTP.
I read in note 390 that is possible to have the two AlphaServer synchronized by defining 
both NTP CLIENTS and on as a LOCAL REFERENCE CLOCK. I assume that the client workatstion
can be defined NTP CLIENTS as well.
What happens if the LOCAL REFERENCE CLOCK system fails?
How can be the other AlphaServer and client workstations be synchronized?

Is there the possibility to have both the AlphaServer be REFERENCE TIME?

Or simply, I'm looking for a way to have both the server synchronized and the workstations
synchronized by the servers.

Is it possible?
How?

Thanks ain advance
Angelo

T.R Title User Personal
Name Date Lines

1883.1 ... BACHUS::DEVOS Manu Devos DEC/SI Brussels 856-7539 Mon Feb 17 1997 07:33 29

T.R	Title	User	Personal Name	Date	Lines
1883.1	...	BACHUS::DEVOS	Manu Devos DEC/SI Brussels 856-7539	`Mon Feb 17 1997 07:33`	29
	Hi, > What happens if the LOCAL REFERENCE CLOCK system fails? Then, all the clients simply keep their clock running without any reference. Once the local reference clock is up again, then the clients begins to align their time on it. > How can be the other AlphaServer and client workstations be synchronized? They are NOT synchronised during the time the local reference clock is down. But, as we are speaking of an ASE CLUSTER, I dont anticipate that the down time will be longer than one or two days, and the accuracy of the today's clock chips is high enough to keep the clients in a reasonable time synchronisation. > Is there the possibility to have both the AlphaServer be REFERENCE TIME? No, you can have only ONE local reference clock. > I'm looking for a way to have both the server synchronized and the workstations synchronized by the servers. You can still declare the two ASE members as "peers" and define all the clients to use the TWO ASE members as "SERVER", but my experience of having the two ASE as normal peer shows me that some time difference between each server is frequent. Hope it helps, Manu.

Hi,

> What happens if the LOCAL REFERENCE CLOCK system fails?

Then, all the clients simply keep their clock running without any reference.
Once the local reference clock is up again, then the clients begins to align
their time on it.

> How can be the other AlphaServer and client workstations be synchronized?

They are NOT synchronised during the time the local reference clock is down.
But, as we are speaking of an ASE CLUSTER, I dont anticipate that the down 
time will be longer than one or two days, and the accuracy of the today's 
clock chips is high enough to keep the clients in a reasonable time
synchronisation.

> Is there the possibility to have both the AlphaServer be REFERENCE TIME?

No, you can have only ONE local reference clock.

> I'm looking for a way to have both the server synchronized and the
  workstations synchronized by the servers.

You can still declare the two ASE members as "peers" and define all the
clients to use the TWO ASE members as "SERVER", but my experience of having
the two ASE as normal peer shows me that some time difference between each
server is frequent.

Hope it helps, Manu.