From: Gérard Henry (ghenry@cmi.univ-mrs.fr)
Date: Mon Mar 31 2008 - 11:56:50 EST
thanks to Darren Dunham and Rich Kuliawec who point the real problem,
that the t2000 cannot act as a server if it isn't sync.
important inforamtion:
stratum 16, precision -14, leap 11, trust 000
Stratum 16 tells us that the t2000 is not synced up, so it's not
possible to use it for sync.
i have to go to my campus administrators, and ask them to repair the
swith that initially deliver the time sync.
original post:
> due to firewall restrictions, i want to configure a solaris machine as
> ntp server, and all others solaris machines as ntp clients
> According to this document:
> http://www.sun.com/blueprints/0801/NTPpt2.pdf
>
> "No special configuration is required for a machine with a running NTP
> daemon to be used by other network nodes as a standard server (as
> opposed to a broadcast server or peer).
> "
>
> so i use a t2000 as a ntp server, and test it from a ultra 20:
> root@ultra20:~# ntpdate -s t2000
> root@ultra20:~# dmesg
> ...
> Mar 31 10:11:18 ultra20 ntpdate[1180]: [ID 831711 daemon.error] no
> server suitable for synchronization found
>
> root@ultra20:~# snoop udp port 123
> Using device nge0 (promiscuous mode)
> ultra20.cmi.univ-mrs.fr -> t2000.cmi.univ-mrs.fr NTP client [st=0]
> (2008-03-31 10:18:35.27198)
> t2000.cmi.univ-mrs.fr -> ultra20.cmi.univ-mrs.fr NTP server [st=0]
> (2008-03-31 10:23:00.24194)
>
> As you can see, the ultra 20 receives the correct date, but the date
> isn't corrected on the ultra20.
> Where am i wrong?
_______________________________________________
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:42:53 EDT