From: Naresh (cknaresh@yahoo.com)
Date: Tue Aug 26 2003 - 06:15:40 EDT
Hi All ,
This is my server config , I wanna configure
it according to the time server 137.92.140.80 . I hav
configured the server , the client is also done with .
But when I start the client and check for associations
I hav it as cause value 16 .
server config is ,
server 137.92.140.80
server 127.127.1.0 prefer
fudge 127.127.1.0 stratum 0
broadcast 224.0.1.1 ttl 4
enable auth monitor
driftfile /etc/ntp.drift
statsdir /var/ntp/ntpstats/
filegen peerstats file peerstats type day enable
filegen loopstats file loopstats type day enable
filegen clockstats file clockstats type day enable
keys /etc/inet/ntp.keys
trustedkey 0
requestkey 0
controlkey 0
client config is ,
server 203.127.115.118 prefer
driftfile /etc/ntp.drift
where 203.127.115.118 is the server .
Kindly suggest asap .
This is the error from server ,
ntpq> peers
remote refid st t when poll reach
delay offset disp
==============================================================================
137.92.140.80 0.0.0.0 16 - - 64 0
0.00 0.000 16000.0
LOCAL(0) .LCL. 0 l 14 64 1
0.00 0.000 15885.0
224.0.1.1 0.0.0.0 16 - - 64 0
0.00 0.000 16000.0
ntpq>
what is error 16 ?
cheers ,
Naresh.
--- Subhash Gupta <SubhashG@hclcomnet.co.in> wrote:
> Hi , Below is a old summary for setting up NTP
> server. I hope it will be
> useful for u
> subhash
>
> Summary:Setting up NTP Server
> Sun solaris mailto:sunsolaris7_2000@yahoo.com
> Mon, 18 Jun 2001 17:23:07 -0700 (PDT)
>
> Previous message: Summary: Printing to Novell Print
> Queues from Solaris.
> Next message: SUMMARY: Long usernames
> Messages sorted by: [ date ] [ thread ] [ subject ]
> [ author ]
>
>
----------------------------------------------------------------------------
> ----
>
> hi,
>
> I got a number of good replies, thanks to all who
> replied. Here i am putting 2 of the good replies.
>
> Just add this to /etc/ntp.conf
>
> server navobs1.usnogps.navy.mil #
> 204.34.198.40 (tick)
> server navobs2.usnogps.navy.mil #
> 204.34.198.41 (tock)
> server time-b.timefreq.bldrdoc.gov #
> 132.163.135.131
> server ntp0.mcs.anl.gov #
> 140.221.8.88
> server 127.127.1.0 # local clock
> fudge 127.127.1.0 stratum 10
>
> then mkdir /etc/ntp
> touch /etc/ntp/drift
>
> 2nd reply:
>
> Pretty straightforward... ensure your
> /etc/inet/ntp.conf has content
> approx thus:
>
> # /etc/inet/ntp.conf
> # for local tier-2 time-servers refer to the URL,
> # http://www.eecis.udel.edu/~mills/ntp/clock2.htm
> # and choose one that is geographically close to
> you.
> #
> server time.server.ip.address prefer minpoll 8
> maxpoll
> 12
> server time.server2.ip.address minpoll 8 maxpoll 12
> #
> # have as many external servers specified as you
> want
> for
> # redundancy - just be sure to flag one with
> "prefer"...
> #
> #server time.server3.ip.address minpoll 8 maxpoll 12
>
> # and apparently, we can always fall back to the
> local
> clock.
> server 127.127.1.0
> fudge 127.127.1.0 stratum 9
>
> # keep local logs so clock can self-adjust based on
> known
> (self-observed) drift:
> enable auth monitor
> driftfile /var/ntp/ntp.drift
> statsdir /var/ntp/ntpstats/
> filegen peerstats file peerstats type day enable
> filegen loopstats file loopstats type day enable
> filegen clockstats file clockstats type day enable
>
>
> --end--
>
> Note that minpoll, maxpoll help specify how often
> you
> want to hit the
> NTP server for a time-check. Default is 64 seconds
> (2^6) I believe. If
> you are not so concerned about the time synch then
> increase your
> minpoll
> value - which is why I've increased minpoll to 2^8=>
> 256 seconds;
> maxpoll of 2^12 seconds. As your local machine "self
> calibrates" and
> drifts less from the external source, the poll
> frequency will gradually
> drop off from Minpoll--->Maxpoll. Ultimately it will
> never poll less
> frequently than specified by maxpoll (in my case,
> once
> ever 2^12
> seconds
> or 4096 seconds AKA once every ~68 minutes.)
>
> Also note that your local clients can synch against
> a
> single "local
> master" - just provide the "local master" IP as the
> "server" instead of
> the external NTP time source. Hence, in my network
> here we have a
> single
> NTP server "master" for each subnet which synchs
> against an external
> source ; then all other machines are configured to
> use
> these local
> masters as their NTP servers. Keeps all clocks
> nicely
> synched and
> minimizes the burden on the external time servers.
>
> Be warned: When first setting things up --- NTP will
> not synch if the
> time is "too far off". You may have to tweak things
> with the "date"
> command to get it within +/- 60 seconds. I typically
> allow "a few
> hours"
> (overnight) to be sure that it is / isn't working.
>
> The command, "ntpq -p" is very handy to evaluate if
> it
> is really
> working. (if things are good, a "*" will appear next
> to the name of the
> external NTP server being used.
>
>
>
> Oh yes. NTP servers provide up GMT I believe. It is
> purely a reference.
> Other issues such as time zone, daylight saving, etc
> are all dealt with
> locally by the OS. Think of NTP as a way to synch
> your
> GMT clock with
> another GMT clock.
>
>
> original question:
>
> Hi,
>
> I am setting up NTP Server & would like to
> synchronize time with external remote time server.
> Can somebody guide me for doing this.
> My servers are located in Central timezone, USA.
> Do I need to refer any specific timeservers to
> synchronize ?
> What are the IP address of those servers ?
>
> Can somebody point me some link where i will get
> list
> of standard time servers ?
> What would be the entries in /etc/inet/ntp.conf
> file.
>
> Any help in this regard would be highly
> appreciated.
>
> Thanks in advance
>
>
>
>
>
>
> -----Original Message-----
> From: Naresh [mailto:cknaresh@yahoo.com]
> Sent: Tuesday, August 26, 2003 3:15 PM
> To: lkapoor@hss.hns.com; sunmanagers@sunmanagers.org
> Subject: ntp configuration
>
>
> Hi ,
>
> I wanna configure ntp(Network Time protocol )
> services to 7 machines . I wanna have one machine as
> the server and the others as the client , Kindly get
> me the simple procedures for the same .
> It will be greatly helpful if u guys can help me on
> this .
>
> Machines are sun netra sparc with solaris 7 as the
> OS
> .
>
> Kindly help .
>
>
=== message truncated ===
--- lkapoor@hss.hns.com wrote:
> Hi Admins,
>
> For IKE on Solaris 9, we are configuring the
> following information for IKE
> Configuration File.
>
------------------------------------------------------------
> # The Default Configuration File for IKE Phase 1
> Security Associations (SA)
> ## File Starts ##
> ##
> ## Phase 1 Transform Identifiers for Main Mode
> ##
> p1_lifetime_secs 270
> p2_lifetime_secs 30000
> p1_nonce_len 20
> ##
> ## Phase 1 Transform Identifiers for Quick Mode
> ##
> local_id_type ipv4
> p2_nonce_len 20
> ##
> ## Policy Rules for IKE
> {
> label "default rule"
> local_addr 192.168.212.251
> remote_addr 192.168.212.93
> p2_lifetime_secs 30000
> p2_pfs 0
> ##
> p1_xform
> { auth_method preshared oakley_group 1 auth_alg
> md5 encr_alg des }
> }
> ##
> ## File Ends ##
>
>
------------------------------------------------------------
> Whatever value we change the "p2_lifetime_secs"
> parameter to, in the final IPSec association created
> it is
> still always 28,800 seconds (default). Here is part
> of the output of the
> "ipseckey get esp spi 0xda3b3487 dst 192.168.212.93"
> command
>
>
------------------------------------------------------------
> SLT: 28500 seconds of post-add lifetime.
> SLT: 0 seconds of post-use lifetime.
> SLT: Soft expiration occurs in 27736 seconds, at Tue
> Aug 26 01:54:20 2003.
> HLT: Hard lifetime information: 0 bytes of
> lifetime, 0 allocations.
> HLT: 28800 seconds of post-add lifetime.
> HLT: 0 seconds of post-use lifetime.
> HLT: Hard expiration occurs in 28036 seconds, at Tue
> Aug 26 01:59:20 2003.
>
>
> Best Regards,
> Lalit Kapoor
> Senior Systems Engineer
>
>
>
>
>
>
> "DISCLAIMER: This message is proprietary to Hughes
> Software Systems Limited
> (HSS) and is intended solely for the use of the
> individual to whom it is
> addressed. It may contain privileged or
> confidential information and
> should not be circulated or used for any purpose
> other than for what it is
> intended. If you have received this message in
> error, please notify the
> originator immediately. If you are not the intended
> recipient, you are
> notified that you are strictly prohibited from
> using, copying, altering, or
> disclosing the contents of this message. HSS accepts
> no responsibility for
> loss or damage arising from the use of the
> information transmitted by this
> email including damage from virus."
> _______________________________________________
> sunmanagers mailing list
> sunmanagers@sunmanagers.org
>
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
_______________________________________________
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:26:59 EDT