From: tops@gmx.net
Date: Wed Aug 04 2004 - 03:43:55 EDT
Hi all,
I have a "time" Problem on a SUN Cluster 3.0 with two SUN Fire 480 Servers.
If I follow the SUN Manuals it does not say how to properly setup the NTP
configuration if the cluster is to be synchronized to external servers. As
out cluster drifts about 1 Minute per month (we have reached about 5 Minutes
now), and I'm about to change this back by using the date -a command
simultaneously on both machines (which both run xntpd in peer mode). The
first machine is using the undisciplined local clock (127.127.1.0). Now I
would like to change this and use a real NTP Server as Time Master. But I
have the following doubts about this.
The SUN Manuals warn not to do any steps in time, so I wonder what will
happen at daylight saving change? We do use MET as Timezone.
My ntp.conf would look like :
server [NTPSERVER 1]
server [NTPSERVER 2]
server 127.127.1.0
fudge 127.127.1.0 stratum 10
peer clusternode1-priv prefer
peer clusternode2-priv
driftfile /var/ntp/ntp.drift
filegen peerstats file peerstats type day enable
filegen loopstats file loopstats type day enable
filegen clockstats file clockstats type day enable
Is this correct. This is a productive System, so I'll get only one shoot to
do it right. Does anybody have a SUN CLUSTER 3.0 System working with a real
NTP Time Master (not local) with Daylight Saving changes?
Best Regards
Andy
-- NEU: WLAN-Router f|r 0,- EUR* - auch f|r DSL-Wechsler! GMX DSL = superg|nstig & kabellos http://www.gmx.net/de/go/dsl _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:29:12 EDT