[j-nsp] NTP service
Paul Goyette
pgoyette@juniper.net
Tue, 3 Sep 2002 12:15:21 -0700
This is a multi-part message in MIME format.
------=_NextPart_000_0072_01C25343.92C69FC0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
RE: [j-nsp] NTP serviceYour offset is -355644 millisecs, or 355.6 seconds.
since
the field is limited to 7 chars including the - sign, I
much rather suspect that the offset is really 3556 seconds,
or just under 1 hour.
Make sure your manual setting of the time accomodates any
time zone and/or summertime/dalight saving time adjustment.
-----Original Message-----
From: juniper-nsp-admin@puck.nether.net
[mailto:juniper-nsp-admin@puck.nether.net]On Behalf Of Javier Alvira
Sent: Tuesday, September 03, 2002 11:55 AM
To: juniper-nsp@puck.nether.net
Cc: Josef Buchsteiner; lediaz@eurocomercial.es
Subject: RE: [j-nsp] NTP service
Thanks to all of you for your answers.
The truth is that I already manually set the time in order to be <128 secs
close to the NTP reference server (10.128.0.20), which actually is just a
NTP server. Other devices querying it are properly in sync...
The "show ntp association" shows this:
remote refid st t when poll reach delay offset
jitter
============================================================================
==
10.128.0.20 .GPS. 1 u 40 64 177 6.716 -355644
4000.00
Thanks in advance for your comments,
Javier
-----Original Message-----
From: Josef Buchsteiner [mailto:josefb@juniper.net]
Sent: martes, 03 de septiembre de 2002 17:22
To: lediaz@eurocomercial.es; Alvira, Javier [CAST:2541:EXCH];
juniper-nsp@puck.nether.net
Subject: RE: [j-nsp] NTP service
At 05:38 PM 9/3/2002, Luis Eduardo Díaz Zazo wrote:
>Hello:
>
>I think the problem does exist. Although Asim and Yi-Kuo suggest the
reason
>is that 128 seconds difference, if I understood Javier, he already took
that
>in mind and made himself sure that the difference didn't exist.
>
>I tried it in my company's bench and found the same problem as Javier
did.
>
>I think the problem is as follows: while trying to synchronize a juniper
to
>another juniper, the server always answers with an NTP response packet
with
>its reference clock field set to zero, according to the packet analysis I
>did. So the client doesn't accept it as a good clock. But I tried to
>synchronize a juniper to another vendor's router that did answer with an
NTP
>response packet with a non-zero reference clock and it did synchronize.
>
>I presume it's a software bug in the server.
Luis,
Juniper can not act as a reference Server on it's own.
So you need to have a proper reference server to be
able to synchronize. This is how it is working since
day one and not a software bug.
I don't know if this was the case in the initial email.
regards
Josef
> I'm using 5.1R2.4 worldwide.
>
>Unfortunately enough, one can't trace this with juniper's trace flags,
since
>there isn't any for NTP.
>
>Regards,
>
>-----------------------------------------------------------
>Luis Eduardo Díaz Zazo Tel: +34 914 359 687
>Eurocomercial I&C S.A. Fax: +34 914 313 240
>Valentín Beato 5 mailto:lediaz@eurocomercial.es
>E-28037 Madrid
>España - Spain http://www.eurocomercial.es
>-----------------------------------------------------------
>
>
>-----Mensaje original-----
>De: juniper-nsp-admin@puck.nether.net
>[mailto:juniper-nsp-admin@puck.nether.net]En nombre de Javier Alvira
>Enviado el: lunes 2 de septiembre de 2002 17:52
>Para: juniper-nsp@puck.nether.net
>Asunto: [j-nsp] NTP service
>
>
>Hi all
>I would like to know whether there is something special when configuring
a
>NTP server in a Juniper (M-10, 5.0R1.4). This is what I configured:
>
>
>time-zone Europe/Lisbon;
>ntp
>
> boot-server 10.128.0.20;
> server 10.128.0.20;
>}
>-------------------------------------
>
>
>The "monitor traffic interface fe-0/0/0" shows this (10.128.0.20 is the
NTP
>server, inside customer's network):
>15:25:48.737589 Out xx.yy.zzz.44.ntp > 10.128.0.20.ntp: v3 client strat
0
>poll 6 prec -20 [tos 0x10]
>15:25:48.745207 In No-L2-hdr 10.128.0.20.ntp > xx.yy.zzz.44.ntp: v3
server
>strat 1 poll 6 prec -19
>-----------------------------------
>
>
>But this is the output for "show ntp status":
>
>
>status=c011 sync_alarm, sync_unspec, 1 event, event_restart,
>processor="i386", system="JUNOS5.0R1.4", leap=11, stratum=16,
>precision=-20, rootdelay=0.000, rootdispersion=6.105, peer=0,
>refid=0.0.0.0, reftime=00000000.00000000 Thu, Feb 7 2036 6:28:16.000,
>poll=6, clock=c119f9e3.d22c343b Fri, Aug 30 2002 15:04:19.820, state=1,
>phase=0.000, frequency=0.000, jitter=0.000, stability=0.000
>-----------------------------------------------------------
>
>
>So it seems it's not working... In fact, the initial difference of 16
secs
>(<128) has widened to 36 secs in 4 days...
>Any input will be welcome!
>Thanks,
>Javier
>
>_______________________________________________
>juniper-nsp mailing list juniper-nsp@puck.nether.net
>http://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp
------=_NextPart_000_0072_01C25343.92C69FC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: [j-nsp] NTP service</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4915.500" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D535401319-03092002><FONT face=3D"Courier New" =
size=3D2>Your offset=20
is -355644 millisecs, or 355.6 seconds. since</FONT></SPAN></DIV>
<DIV><SPAN class=3D535401319-03092002><FONT face=3D"Courier New" =
size=3D2>the field is=20
limited to 7 chars including the - sign, I</FONT></SPAN></DIV>
<DIV><SPAN class=3D535401319-03092002><FONT face=3D"Courier New" =
size=3D2>much rather=20
suspect that the offset is really 3556 seconds,</FONT></SPAN></DIV>
<DIV><SPAN class=3D535401319-03092002><FONT face=3D"Courier New" =
size=3D2>or just=20
under 1 hour.</FONT></SPAN></DIV>
<DIV><SPAN class=3D535401319-03092002><FONT face=3D"Courier New"=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D535401319-03092002><FONT face=3D"Courier New" =
size=3D2>Make sure=20
your manual setting of the time accomodates any</FONT></SPAN></DIV>
<DIV><SPAN class=3D535401319-03092002><FONT face=3D"Courier New" =
size=3D2>time zone=20
and/or summertime/dalight saving time adjustment.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B>=20
juniper-nsp-admin@puck.nether.net=20
[mailto:juniper-nsp-admin@puck.nether.net]<B>On Behalf Of </B>Javier=20
Alvira<BR><B>Sent:</B> Tuesday, September 03, 2002 11:55 =
AM<BR><B>To:</B>=20
juniper-nsp@puck.nether.net<BR><B>Cc:</B> Josef Buchsteiner;=20
lediaz@eurocomercial.es<BR><B>Subject:</B> RE: [j-nsp] NTP=20
service<BR><BR></FONT></DIV>
<P><FONT size=3D2>Thanks to all of you for your answers.</FONT> </P>
<P><FONT size=3D2>The truth is that I already manually set the time in =
order to=20
be <128 secs close to the NTP reference server (10.128.0.20), which =
actually is just a NTP server. Other devices querying it are properly =
in=20
sync...</FONT></P>
<P><FONT size=3D2>The "show ntp association" shows this:</FONT> </P>
<P><FONT size=3D2> =20
remote =20
refid st t when poll reach =20
delay offset jitter</FONT> <BR><FONT=20
=
size=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D</FONT>=20
<BR><FONT size=3D2> 10.128.0.20 =20
=
.GPS. =
1=20
u 40 64 177 =
6.716 =20
-355644 4000.00</FONT> </P><BR>
<P><FONT size=3D2>Thanks in advance for your comments,</FONT> </P>
<P><FONT size=3D2>Javier</FONT> </P><BR>
<P><FONT size=3D2>-----Original Message-----</FONT> <BR><FONT =
size=3D2>From: Josef=20
Buchsteiner [<A=20
=
href=3D"mailto:josefb@juniper.net">mailto:josefb@juniper.net</A>]</FONT> =
<BR><FONT size=3D2>Sent: martes, 03 de septiembre de 2002 17:22</FONT> =
<BR><FONT=20
size=3D2>To: lediaz@eurocomercial.es; Alvira, Javier =
[CAST:2541:EXCH];</FONT>=20
<BR><FONT size=3D2>juniper-nsp@puck.nether.net</FONT> <BR><FONT =
size=3D2>Subject:=20
RE: [j-nsp] NTP service</FONT> </P><BR>
<P><FONT size=3D2>At 05:38 PM 9/3/2002, Luis Eduardo D=EDaz Zazo =
wrote:</FONT>=20
<BR><FONT size=3D2>>Hello:</FONT> <BR><FONT size=3D2>></FONT> =
<BR><FONT=20
size=3D2>>I think the problem does exist. Although Asim and Yi-Kuo =
suggest=20
the reason</FONT> <BR><FONT size=3D2>>is that 128 seconds =
difference, if I=20
understood Javier, he already took that</FONT> <BR><FONT =
size=3D2>>in mind=20
and made himself sure that the difference didn't exist.</FONT> =
<BR><FONT=20
size=3D2>></FONT> <BR><FONT size=3D2>>I tried it in my company's =
bench and=20
found the same problem as Javier did.</FONT> <BR><FONT =
size=3D2>></FONT>=20
<BR><FONT size=3D2>>I think the problem is as follows: while trying =
to=20
synchronize a juniper to</FONT> <BR><FONT size=3D2>>another =
juniper, the=20
server always answers with an NTP response packet with</FONT> =
<BR><FONT=20
size=3D2>>its reference clock field set to zero, according to the =
packet=20
analysis I</FONT> <BR><FONT size=3D2>>did. So the client doesn't =
accept it as=20
a good clock. But I tried to</FONT> <BR><FONT size=3D2>>synchronize =
a juniper=20
to another vendor's router that did answer with an NTP</FONT> =
<BR><FONT=20
size=3D2>>response packet with a non-zero reference clock and it =
did=20
synchronize.</FONT> <BR><FONT size=3D2>></FONT> <BR><FONT =
size=3D2>>I=20
presume it's a software bug in the server.</FONT> </P>
<P><FONT size=3D2>Luis,</FONT> </P>
<P><FONT size=3D2>Juniper can not act as a reference Server on it's =
own.</FONT>=20
<BR><FONT size=3D2>So you need to have a proper reference server to =
be</FONT>=20
<BR><FONT size=3D2>able to synchronize. This is how it is working =
since</FONT>=20
<BR><FONT size=3D2>day one and not a software bug.</FONT> </P>
<P><FONT size=3D2>I don't know if this was the case in the initial =
email.</FONT>=20
</P>
<P><FONT size=3D2>regards</FONT> <BR><FONT size=3D2>Josef</FONT> </P>
<P><FONT size=3D2>> I'm using 5.1R2.4 worldwide.</FONT> =
<BR><FONT=20
size=3D2>></FONT> <BR><FONT size=3D2>>Unfortunately enough, one =
can't trace=20
this with juniper's trace flags, since</FONT> <BR><FONT =
size=3D2>>there isn't=20
any for NTP.</FONT> <BR><FONT size=3D2>></FONT> <BR><FONT=20
size=3D2>>Regards,</FONT> <BR><FONT size=3D2>></FONT> <BR><FONT=20
=
size=3D2>>-----------------------------------------------------------<=
/FONT>=20
<BR><FONT size=3D2>>Luis Eduardo D=EDaz=20
Zazo Tel: +34 914 359 687</FONT> =
<BR><FONT=20
size=3D2>>Eurocomercial I&C =
S.A. Fax:=20
+34 914 313 240</FONT> <BR><FONT size=3D2>>Valent=EDn Beato=20
=
5 =
<A=20
=
href=3D"mailto:lediaz@eurocomercial.es">mailto:lediaz@eurocomercial.es</A=
></FONT>=20
<BR><FONT size=3D2>>E-28037 Madrid</FONT> <BR><FONT =
size=3D2>>Espa=F1a -=20
=
Spain &n=
bsp; =20
<A target=3D_blank=20
=
href=3D"http://www.eurocomercial.es">http://www.eurocomercial.es</A></FON=
T>=20
<BR><FONT=20
=
size=3D2>>-----------------------------------------------------------<=
/FONT>=20
<BR><FONT size=3D2>></FONT> <BR><FONT size=3D2>></FONT> =
<BR><FONT=20
size=3D2>>-----Mensaje original-----</FONT> <BR><FONT =
size=3D2>>De:=20
juniper-nsp-admin@puck.nether.net</FONT> <BR><FONT size=3D2>>[<A=20
=
href=3D"mailto:juniper-nsp-admin@puck.nether.net">mailto:juniper-nsp-admi=
n@puck.nether.net</A>]En=20
nombre de Javier Alvira</FONT> <BR><FONT size=3D2>>Enviado el: =
lunes 2 de=20
septiembre de 2002 17:52</FONT> <BR><FONT size=3D2>>Para:=20
juniper-nsp@puck.nether.net</FONT> <BR><FONT size=3D2>>Asunto: =
[j-nsp] NTP=20
service</FONT> <BR><FONT size=3D2>></FONT> <BR><FONT =
size=3D2>></FONT>=20
<BR><FONT size=3D2>>Hi all</FONT> <BR><FONT size=3D2>>I would =
like to know=20
whether there is something special when configuring a</FONT> <BR><FONT =
size=3D2>>NTP server in a Juniper (M-10, 5.0R1.4). This is what I=20
configured:</FONT> <BR><FONT size=3D2>></FONT> <BR><FONT =
size=3D2>></FONT>=20
<BR><FONT size=3D2>>time-zone Europe/Lisbon;</FONT> <BR><FONT=20
size=3D2>>ntp</FONT> <BR><FONT size=3D2>></FONT> <BR><FONT=20
size=3D2>> boot-server 10.128.0.20;</FONT> =
<BR><FONT=20
size=3D2>> server 10.128.0.20;</FONT> =
<BR><FONT=20
size=3D2>>}</FONT> <BR><FONT=20
size=3D2>>-------------------------------------</FONT> <BR><FONT=20
size=3D2>></FONT> <BR><FONT size=3D2>></FONT> <BR><FONT =
size=3D2>>The=20
"monitor traffic interface fe-0/0/0" shows this (10.128.0.20 is the =
NTP</FONT>=20
<BR><FONT size=3D2>>server, inside customer's network):</FONT> =
<BR><FONT=20
size=3D2>>15:25:48.737589 Out xx.yy.zzz.44.ntp > =
10.128.0.20.ntp: v3=20
client strat 0</FONT> <BR><FONT size=3D2>>poll 6 prec -20 [tos =
0x10]</FONT>=20
<BR><FONT size=3D2>>15:25:48.745207 In No-L2-hdr =
10.128.0.20.ntp >=20
xx.yy.zzz.44.ntp: v3 server</FONT> <BR><FONT size=3D2>>strat =
1 poll 6=20
prec -19</FONT> <BR><FONT=20
size=3D2>>-----------------------------------</FONT> <BR><FONT=20
size=3D2>></FONT> <BR><FONT size=3D2>></FONT> <BR><FONT =
size=3D2>>But this=20
is the output for "show ntp status":</FONT> <BR><FONT =
size=3D2>></FONT>=20
<BR><FONT size=3D2>></FONT> <BR><FONT size=3D2>>status=3Dc011 =
sync_alarm,=20
sync_unspec, 1 event, event_restart,</FONT> <BR><FONT=20
size=3D2>>processor=3D"i386", system=3D"JUNOS5.0R1.4", leap=3D11,=20
stratum=3D16,</FONT> <BR><FONT size=3D2>>precision=3D-20, =
rootdelay=3D0.000,=20
rootdispersion=3D6.105, peer=3D0,</FONT> <BR><FONT =
size=3D2>>refid=3D0.0.0.0,=20
reftime=3D00000000.00000000 Thu, Feb 7 2036 =20
6:28:16.000,</FONT> <BR><FONT size=3D2>>poll=3D6, =
clock=3Dc119f9e3.d22c343b =20
Fri, Aug 30 2002 15:04:19.820, state=3D1,</FONT> <BR><FONT=20
size=3D2>>phase=3D0.000, frequency=3D0.000, jitter=3D0.000, =
stability=3D0.000</FONT>=20
<BR><FONT=20
=
size=3D2>>-----------------------------------------------------------<=
/FONT>=20
<BR><FONT size=3D2>></FONT> <BR><FONT size=3D2>></FONT> =
<BR><FONT=20
size=3D2>>So it seems it's not working... In fact, the initial =
difference of=20
16 secs</FONT> <BR><FONT size=3D2>>(<128) has widened to 36 secs =
in 4=20
days...</FONT> <BR><FONT size=3D2>>Any input will be =
welcome!</FONT>=20
<BR><FONT size=3D2>>Thanks,</FONT> <BR><FONT =
size=3D2>>Javier</FONT>=20
<BR><FONT size=3D2>></FONT> <BR><FONT=20
size=3D2>>_______________________________________________</FONT> =
<BR><FONT=20
size=3D2>>juniper-nsp mailing list =
juniper-nsp@puck.nether.net</FONT>=20
<BR><FONT size=3D2>><A target=3D_blank=20
=
href=3D"http://puck.nether.net/mailman/listinfo/juniper-nsp">http://puck.=
nether.net/mailman/listinfo/juniper-nsp</A></FONT>=20
</P>
<P><FONT =
size=3D2>_______________________________________________</FONT>=20
<BR><FONT size=3D2>juniper-nsp mailing list =
juniper-nsp@puck.nether.net</FONT>=20
<BR><FONT size=3D2><A target=3D_blank=20
=
href=3D"http://puck.nether.net/mailman/listinfo/juniper-nsp">http://puck.=
nether.net/mailman/listinfo/juniper-nsp</A></FONT>=20
</P></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0072_01C25343.92C69FC0--