xntpd Time Server 2

[khalidaaa]

Hi Guys,

We have two P5 570s machines with 12 LPARs. I'm trying to create a Time Server on two of the LPARs (one for each system) and letting the other LPARs synchronize the time with them.

That's the /etc/ntp.conf on the Server

#broadcastclient
server 127.127.1.0
fudge 127.127.1.0 stratum 10
#peer 10.1.1.150
#server 10.1.1.200
peer 10.1.1.151
driftfile /etc/ntp.drift
tracefile /etc/ntp.trace

and that's the ntp.conf for one of the clients:

#broadcastclient
server 127.127.1.0
fudge 127.127.1.0 stratum 10
server 10.1.1.150
server 10.1.1.151
driftfile /etc/ntp.drift
tracefile /etc/ntp.trace

I started the xntpd daemon from smitty xntpd and now its running.

now my question how do i know that what i did is working! and the main question is how to integrate what i did with a Windows Time server that we have in our Active Directory network.

I was trying to use the IP (10.1.1.200) for the Windows AD Time Server but i don't know whether it was working or not! It might not work because my LPARs are not authenticated on the AD.

Any Information is appreciated.

Thanks,

Regards,
Khalid

 

[khalidaaa]

I'm really really thankful for your support Gloups

I did it with xntpd -ddd but it didn't work so i increase the d's till i reach 5 ds then something but i still don't know how to translate that!?!

systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000048992 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000049139 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000049286 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000049432 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000049579 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000049726 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000049872 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000050019 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000050166 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000050312 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000050459 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000050606 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000050752 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000050899 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000051046 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000051192 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000051339 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000051486 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000051633 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000051779 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000051926 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000052073 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000052219 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000052366 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000052513 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000052659 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000052806 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000052953 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000053099 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000053246 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000053393 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000053539 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000053686 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000053833 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000053979 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000054126 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000054273 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000054420 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000054566 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000054713 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000054860 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000055006 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000055153 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000055300 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000055446 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000055593 sec
systime: adjtv = 0.000000 sec, adjts = 0.000000000 sec, sys_clock_offset = 0.000055740 sec

as i see the sys_clock_offset is increasing every time but i don't know what that means?!?

I ran this command on one of the AIX servers with stratum 9 that should communicate with the Active Directory Time Server with Stratum 1 I believe

Any comments will be appreciated

Regards,
Khalid

 

[khalidaaa]

on one of the clients I issued xntpdc -i and did the following

# xntpdc -i
xntpdc> host
current host is loopback
xntpdc> host s2cdbs
current host set to s2cdbs
xntpdc> peers
     remote           local      st poll reach  delay   offset    disp
=======================================================================
=LOCAL(0)        127.0.0.1        9   64  377 0.00000  0.000000 0.01001
*10.1.1.200      10.1.1.151       1   64  377 0.00040  0.015308 0.01530
+s1cdbp          10.1.1.151      10   64    0 0.00102 -33.31641 16.0000
xntpdc> host localhost
current host set to loopback
xntpdc> peers
     remote           local      st poll reach  delay   offset    disp
=======================================================================
=LOCAL(0)        127.0.0.1       10   64  377 0.00000  0.000000 0.01001
*s2cdbs          10.1.1.152       2   64  377 0.00044 33.319654 0.00011
=s1cdbp          10.1.1.152      10   64    0 0.00038 -0.000075 16.0000

but on the server (AIX time server) s2cdbs i issued the same command but got errors when i did the following:

xntpdc> listpeers
10.1.1.200: timed out, nothing received
***Request timed out
xntpdc> peers
10.1.1.200: timed out, nothing received
***Request timed out
xntpdc> host
current host is 10.1.1.200
xntpdc> host localhost
current host set to loopback
xntpdc> listpeers
client    LOCAL(0)
client    10.1.1.200
sym_active s1cdbp
xntpdc> peers
     remote           local      st poll reach  delay   offset    disp
=======================================================================
=LOCAL(0)        127.0.0.1        9   64  377 0.00000  0.000000 0.01001
*10.1.1.200      10.1.1.151       1   64  377 0.00034  0.010293 0.00423
+s1cdbp          10.1.1.151      10   64    0 0.00102 -33.31641 16.0000

I'm getting more confused

Regards,
Khalid

 

[khalidaaa]

I found this on the internet

http://mailgate.supereva.com/comp/comp.protocols.time.ntp/msg08309.html

poll - 1024 - means that the remote is being queried once every 1024
seconds, the normal for a stable system

reach - 377 - means 100% connectivity with the remote source (it's an
octal value)

Your value of poll (256) suggests that ntpd hasn't yet reached stability.

Your reach values (340 200) means there has been no contact with the
server for the last few poll intervals.

Your values of delay (290 310) suggest the servers are two satellite hops
away - could you not find nearer ones?

This is just a starting point.  I am not an expert on this, but I am more
Windows biased than many of the group members.  I am surprised no-one else
has jumped in, quite honestly.

my output is this:

# ntpq -p               
     remote           refid      st t when poll reach   delay   offset    disp
==============================================================================
 LOCAL(0)        LOCAL(0)         9 l   53   64  377     0.00    0.000   10.01
 s1cdbp          s2cdbs           3 u   19   64  377     0.00   -5.396    1.51
#10.1.1.200      .LOCL.           1 u   51   64  377     0.40   -0.430    1.75

so shall i assume that because i've got reach of 377 means i is for sure 100% communication with the AD time server?

Regards,
Khalid

 

[khalidaaa]

You gave up this time Gloups

But i really appreciate your help and i think you deserve more than just one star

Regards,
Khalid

 

[davinator]

Khalid,

This thread is a little old, but I hope you read it anyway. Windows AD runs SNTP, not NTP. SNTP is a subset of NTP so NTP clients (which expect the full protocol) won't sync well (or at all) with Windows AD servers.

However, the reverse works fine. Windows servers can sync to any NTP server. You might want to have your Windows servers sync to your p570s. Also, the clocks on your p570s are more stable than a PC. Windows time sync isn't designed to be more accurate than something like 5 minutes. Unix systems, on the other hand, usually need sub-second accuracy.

2 of your p570 LPARs, one on each macine, could sync off the public time servers and the rest of your network could sync to that. If that's not acceptable, there are 1U NTP servers made of specalized harware that can be purchased relatively inexpensively - compared to your p570s....

Davin

 

[khalidaaa]

Thank you very much davinator for the addition of course i will read that even if it is old!

well, to be honest i'm not sure if it is still taking the time accurately from the AD time server but i guess it was doing the job when i checked it!

I don't remember this issue for now as it has been along time for my setup. But i will try to go later on and revisit my config and i will let you know! unfortunatly i'm on vacation for now but i will be able to check that after a week!

Thanks again
Khalid