RE: Timestamp

["Kenneth Goodwin" <kgoodwin datamarktech com>]

www.cisco.com  technical support

++> -----Original Message-----
++> From: enigma-list-admin redhat com
++> [mailto:enigma-list-admin redhat com]On Behalf Of Nataniel Klug
++> Sent: Friday, November 22, 2002 4:53 AM
++> To: enigma-list redhat com
++> Subject: Re: Timestamp
++> 
++> 
++>     Kenneth,
++> 
++>     I actualy have a Cisco 1600 Router in my ISP. Where can 
++> I find information about
++> configuring my Cisco as a clock server?
++> 
++> Nataniel
++> 
++> ----- Original Message -----
++> From: "Kenneth Goodwin" <kgoodwin datamarktech com>
++> To: <enigma-list redhat com>
++> Sent: Thursday, November 21, 2002 12:15 PM
++> Subject: RE: Timestamp
++> 
++> 
++> : actually, make one  of your servers a Primary stratum 
++> level 2 or 3 clock
++> : source and sync itself to a couple of stratum level one 
++> or preferably level
++> : TWO clock sources (Search for NTPD for more info and 
++> manuals and a list of
++> : stratum
++> : level one and two clock providers out on the Internet)
++> :
++> : Sync two others in a stratum level 2 or 3 cluster with 
++> the primary and have
++> : them use Multicast or Broadcast
++> : services to provide clock time to your other hosts. This 
++> is a three node
++> : time cluster that will sync with itself
++> : even if the internet source goes down.
++> :
++> : Then setup NTPD on the rest of the boxes as clients using 
++> multicast or
++> : broadcast to Receive the time updates from the primary 
++> server and it's two
++> : secondarys.
++> :
++> : NTPDATE is too one time to use in CRON and takes a while 
++> to resolve times.
++> : Also one clock source server only configs tend to be 
++> prone to failures
++> : elsewhere when they crash, better to have few main local 
++> clock sources
++> : synching to each other and a couple of others out on the Internet.
++> :
++> : If you have a cisco router on your internet, it can setup 
++> to be a stratum 2
++> : primary NTP clock server and also filter via access lists 
++> time protocol
++> : packets such that they are only allowed from designated 
++> source IP's.
++> :
++> :
++> : ++> -----Original Message-----
++> : ++> From: enigma-list-admin redhat com
++> : ++> [mailto:enigma-list-admin redhat com]On Behalf Of 
++> Nataniel Klug
++> : ++> Sent: Thursday, November 21, 2002 7:06 AM
++> : ++> To: enigma-list redhat com
++> : ++> Subject: Re: Timestamp
++> : ++>
++> : ++>
++> : ++>     Andrew,
++> : ++>
++> : ++>     You mean that if I use one of my boxes as a clock
++> : ++> server, I will have a perfect
++> : ++> syncronize in the others? I will try this.
++> : ++>
++> : ++> Nataniel
++> : ++>
++> : ++> ----- Original Message -----
++> : ++> From: "Andrew Kelly" <akelly transparency org>
++> : ++> To: <enigma-list redhat com>
++> : ++> Sent: Thursday, November 21, 2002 8:44 AM
++> : ++> Subject: Re: Timestamp
++> : ++>
++> : ++>
++> : ++> : What about using ntpd instead? Run the deamon on 
++> one box, pointing
++> : ++> : at a stratum 1 server. Then you can call ntpdate on that box
++> : ++> : (now stratum 2) using cron.
++> : ++> :
++> : ++> :
++> : ++> : Nataniel Klug wrote:
++> : ++> : >
++> : ++> : >     Hello,
++> : ++> : >
++> : ++> : >     I syncronize my boxes using rdate. I to a 
++> comand likle this:
++> : ++> : >
++> : ++> : > File: /etc/crontab
++> : ++> : > 30 6 * * * root rdate -s ntp0.fau.de
++> : ++> : > 31 6 * * * root /usr/sbin/setclock
++> : ++> : >
++> : ++> : >     But in one of my box I receive a message that
++> : ++> external machines can not determine
++> : ++> the
++> : ++> : > clock of that box, so they can not syncronize files or
++> : ++> anything. It is generatin an
++> : ++> error
++> : ++> : > in my MRTG Monitoring Tool with the timestamp wrong.
++> : ++> Can I solve this?
++> : ++> : >
++> : ++> : > Best regards,
++> : ++> : >
++> : ++> : > Nataniel Klug
++> : ++> : > www.cnett.com.br
++> : ++> :
++> : ++> : --
++> : ++> : Andrew Kelly
++> : ++> : IT
++> : ++> : Transparency International
++> : ++> : Otto-Suhr-Allee 97/99
++> : ++> : 10585 Berlin, Germany
++> : ++> : Tel: +4930 3438 2026, Fax: +4930 3470 3912
++> : ++> : AKelly transparency org
++> : ++> :
++> : ++> :
++> : ++> :
++> : ++> : _______________________________________________
++> : ++> : enigma-list mailing list
++> : ++> : enigma-list redhat com
++> : ++> : https://listman.redhat.com/mailman/listinfo/enigma-list
++> : ++> :
++> : ++>
++> : ++>
++> : ++>
++> : ++>
++> : ++> _______________________________________________
++> : ++> enigma-list mailing list
++> : ++> enigma-list redhat com
++> : ++> https://listman.redhat.com/mailman/listinfo/enigma-list
++> : ++>
++> :
++> :
++> :
++> : _______________________________________________
++> : enigma-list mailing list
++> : enigma-list redhat com
++> : https://listman.redhat.com/mailman/listinfo/enigma-list
++> :
++> 
++> 
++> 
++> 
++> _______________________________________________
++> enigma-list mailing list
++> enigma-list redhat com
++> https://listman.redhat.com/mailman/listinfo/enigma-list
++>