NTP offset

LittleMaster · 05-25-2013, 09:10 PM

Hi

I've been facing the issue Ntp Client is not syncing the ntp server .

Crossed check firewall setting on both ntp client & ntp server .Traffic flows has been allowed to flow between ntp client & ntp server

Need help whether there is any configuration error on my ntp configuration file

Quote:

root:beetel# cat /etc/ntp.conf
# Permit time synchronization with our time source, but do not
# permit the source to query or modify the service on this system.
restrict default kod nomodify notrap nopeer noquery
restrict -6 default kod nomodify notrap nopeer noquery

# Permit all access over the loopback interface. This could
# be tightened as well, but to do so would effect some of
# the administrative functions.
restrict 127.0.0.1
restrict -6 ::1

# Hosts on local network are less restricted.
#restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap

# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).
server be
server porsche.example.com
server porsche.example.com

# Undisciplined Local Clock. This is a fake driver intended for backup
# and when no outside source of synchronized time is available.
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10

# Drift file. Put this in a directory which the daemon can write to.
# No symbolic links allowed, either, since the daemon updates the file
# by creating a temporary in the same directory and then rename()'ing
# it to the file.
driftfile /var/lib/ntp/drift

# Key file containing the keys and key identifiers used when operating
# with symmetric key cryptography.
keys /etc/ntp/keys

# Specify the key identifiers which are trusted.
#trustedkey 4 8 42

# Specify the key identifier to use with the ntpdc utility.
#requestkey 8

# Specify the key identifier to use with the ntpq utility.
#controlkey 8
restrict porsche.example.com nomodify notrap
restrict porsche.example.com nomodify notrap
restrict porsche.example.com nomodify notrap

restrict default ignore
root:beetel#

Ntp client

Quote:

root:beetel# /usr/sbin/ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
porsche.example. .INIT. 16 u - 64 0 0.000 0.000 4000.00
porsche.example. .INIT. 16 u - 64 0 0.000 0.000 4000.00
porsche.example. .INIT. 16 u - 64 0 0.000 0.000 4000.00
LOCAL(0) LOCAL(0) 10 l 50 64 1 0.000 0.000 0.004

Quote:

root:beetel# ntpstat
unsynchronised
time server re-starting
polling server every 64 s
root:beetel#

Quote:

root:beetel# /usr/sbin/ntpdc -c loopinfo
offset: 0.000000 s
frequency: 0.000 ppm
poll adjust: 0
watchdog timer: 74 s

Quote:

root:beetel# /usr/sbin/ntpdc -c kerninfo
pll offset: 0 s
pll frequency: 0.000 ppm
maximum error: 0.02359 s
estimated error: 1e-06 s
status: 0001 pll
pll time constant: 2
precision: 1e-06 s
frequency tolerance: 512 ppm
pps frequency: 0.000 ppm
pps stability: 512.000 ppm
pps jitter: 0.0002 s
calibration interval: 4 s
calibration cycles: 0
jitter exceeded: 0
stability exceeded: 0
calibration errors: 0

acid_kewpie · 05-26-2013, 03:31 AM

the servers (which have the same name??? that's clearly nuts) are not reachable. there is some networking issue, or other, that is stopping any contact between the two, and no obvious problem in NTP itself.

LittleMaster · 05-27-2013, 12:43 AM

I've adjusted the MTU size and checked out but too no success at all.

Previous network was configured in normal mode.I've enabled to promisc mode to make all the packets that flows through the network card.

Any other thing i can try.

Quote:

[root@beetel ~]# ntpq
ntpq> ass

ind assID status conf reach auth condition last_event cnt
===========================================================
1 48068 8000 yes yes none reject
2 48069 8000 yes yes none reject
3 48070 8000 yes yes none reject
4 48071 9614 yes yes none sys.peer reachable 1

Quote:

ntpq> rv
assID=0 status=0544 leap_none, sync_local_proto, 4 events, event_peer/strat_chg,
version="ntpd 4.2.0a@1.1190-r Thu May 12 04:29:06 EDT 2010 (1)"?,
processor="i686", system="Linux/2.6.9-89.ELsmp", leap=00, stratum=11,
precision=-18, rootdelay=0.000, rootdispersion=11.993, peer=48071,
refid=LOCAL(0),
reftime=d54d6f3b.a320a73f Mon, May 27 2013 1:35:55.637, poll=10,
clock=0xd54d6f41.a29fadaf, state=4, offset=0.000, frequency=0.000,
noise=0.000, jitter=0.004, stability=0.000

Quote:

ntpq> peers
remote refid st t when poll reach delay offset jitter
==============================================================================
porsche.example. .INIT. 16 u - 1024 0 0.000 0.000 4000.00
porsche1.example. .INIT. 16 u - 1024 0 0.000 0.000 4000.00
porsche2.example. .INIT. 16 u - 1024 0 0.000 0.000 4000.00
*LOCAL(0) LOCAL(0) 10 l 19 64 377 0.000 0.000 0.004
ntpq>

Quote:

ntpq> delay
delay 20 ms

acid_kewpie · 05-27-2013, 05:33 AM

MTU size? Promisc?? the devices just don't appear to be reachable at a basic network level. Doubt there's any need for that at all. Possibly the NTP servers are choosing not to respond based on their own config, but a server listed as Strata 16 just means that it's never ever replied.