[j-nsp] NTP service
Javier Alvira
jalvira@nortelnetworks.com
Tue, 3 Sep 2002 19:55:28 +0100
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C2537B.78A04A6E
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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
=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
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=EDaz 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=EDaz Zazo Tel: +34 914 359 687
>Eurocomercial I&C S.A. Fax: +34 914 313 240
>Valent=EDn Beato 5 mailto:lediaz@eurocomercial.es
>E-28037 Madrid
>Espa=F1a - 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=3Dc011 sync_alarm, sync_unspec, 1 event, event_restart,
>processor=3D"i386", system=3D"JUNOS5.0R1.4", leap=3D11, stratum=3D16,
>precision=3D-20, rootdelay=3D0.000, rootdispersion=3D6.105, peer=3D0,
>refid=3D0.0.0.0, reftime=3D00000000.00000000 Thu, Feb 7 2036 =
6:28:16.000,
>poll=3D6, clock=3Dc119f9e3.d22c343b Fri, Aug 30 2002 15:04:19.820, =
state=3D1,
>phase=3D0.000, frequency=3D0.000, jitter=3D0.000, stability=3D0.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_001_01C2537B.78A04A6E
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [j-nsp] NTP service</TITLE>
</HEAD>
<BODY>
<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 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...</FONT></P>
<P><FONT SIZE=3D2>The "show ntp association" shows =
this:</FONT>
</P>
<P><FONT SIZE=3D2> =
remote =
refid st t when poll reach =
delay offset jitter</FONT>
<BR><FONT =
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>
<BR><FONT SIZE=3D2> 10.128.0.20 =
.GPS. =
1 u 40 64 177 =
6.716 -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 Buchsteiner [<A =
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 SIZE=3D2>To: lediaz@eurocomercial.es; Alvira, Javier =
[CAST:2541:EXCH];</FONT>
<BR><FONT SIZE=3D2>juniper-nsp@puck.nether.net</FONT>
<BR><FONT SIZE=3D2>Subject: 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>
<BR><FONT SIZE=3D2>>Hello:</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>I think the problem does exist. Although Asim =
and Yi-Kuo suggest the reason</FONT>
<BR><FONT SIZE=3D2>>is that 128 seconds difference, if I understood =
Javier, he already took that</FONT>
<BR><FONT SIZE=3D2>>in mind and made himself sure that the =
difference didn't exist.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>I tried it in my company's bench and found the =
same problem as Javier did.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>I think the problem is as follows: while trying =
to synchronize a juniper to</FONT>
<BR><FONT SIZE=3D2>>another juniper, the server always answers with =
an NTP response packet with</FONT>
<BR><FONT SIZE=3D2>>its reference clock field set to zero, according =
to the packet analysis I</FONT>
<BR><FONT SIZE=3D2>>did. So the client doesn't accept it as a good =
clock. But I tried to</FONT>
<BR><FONT SIZE=3D2>>synchronize a juniper to another vendor's router =
that did answer with an NTP</FONT>
<BR><FONT SIZE=3D2>>response packet with a non-zero reference clock =
and it did synchronize.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>I 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>
<BR><FONT SIZE=3D2>So you need to have a proper reference server to =
be</FONT>
<BR><FONT SIZE=3D2>able to synchronize. This is how it is working =
since</FONT>
<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>
</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 SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>Unfortunately enough, one can't trace this with =
juniper's trace flags, since</FONT>
<BR><FONT SIZE=3D2>>there isn't any for NTP.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>Regards,</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT =
SIZE=3D2>>-----------------------------------------------------------=
</FONT>
<BR><FONT SIZE=3D2>>Luis Eduardo D=EDaz =
Zazo Tel: +34 914 359 687</FONT>
<BR><FONT SIZE=3D2>>Eurocomercial I&C =
S.A. Fax: +34 914 313 240</FONT>
<BR><FONT SIZE=3D2>>Valent=EDn Beato =
5  =
; <A =
HREF=3D"mailto:lediaz@eurocomercial.es">mailto:lediaz@eurocomercial.es</=
A></FONT>
<BR><FONT SIZE=3D2>>E-28037 Madrid</FONT>
<BR><FONT SIZE=3D2>>Espa=F1a - =
Spain &=
nbsp; <A HREF=3D"http://www.eurocomercial.es" =
TARGET=3D"_blank">http://www.eurocomercial.es</A></FONT>
<BR><FONT =
SIZE=3D2>>-----------------------------------------------------------=
</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>-----Mensaje original-----</FONT>
<BR><FONT SIZE=3D2>>De: juniper-nsp-admin@puck.nether.net</FONT>
<BR><FONT SIZE=3D2>>[<A =
HREF=3D"mailto:juniper-nsp-admin@puck.nether.net">mailto:juniper-nsp-adm=
in@puck.nether.net</A>]En nombre de Javier Alvira</FONT>
<BR><FONT SIZE=3D2>>Enviado el: lunes 2 de septiembre de 2002 =
17:52</FONT>
<BR><FONT SIZE=3D2>>Para: juniper-nsp@puck.nether.net</FONT>
<BR><FONT SIZE=3D2>>Asunto: [j-nsp] NTP service</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>Hi all</FONT>
<BR><FONT SIZE=3D2>>I would like to know 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 configured:</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>time-zone Europe/Lisbon;</FONT>
<BR><FONT SIZE=3D2>>ntp</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> boot-server =
10.128.0.20;</FONT>
<BR><FONT SIZE=3D2>> server =
10.128.0.20;</FONT>
<BR><FONT SIZE=3D2>>}</FONT>
<BR><FONT SIZE=3D2>>-------------------------------------</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>The "monitor traffic interface =
fe-0/0/0" shows this (10.128.0.20 is the NTP</FONT>
<BR><FONT SIZE=3D2>>server, inside customer's network):</FONT>
<BR><FONT SIZE=3D2>>15:25:48.737589 Out xx.yy.zzz.44.ntp > =
10.128.0.20.ntp: v3 client strat 0</FONT>
<BR><FONT SIZE=3D2>>poll 6 prec -20 [tos 0x10]</FONT>
<BR><FONT SIZE=3D2>>15:25:48.745207 In No-L2-hdr =
10.128.0.20.ntp > xx.yy.zzz.44.ntp: v3 server</FONT>
<BR><FONT SIZE=3D2>>strat 1 poll 6 prec -19</FONT>
<BR><FONT SIZE=3D2>>-----------------------------------</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>But this is the output for "show ntp =
status":</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>status=3Dc011 sync_alarm, sync_unspec, 1 event, =
event_restart,</FONT>
<BR><FONT SIZE=3D2>>processor=3D"i386", =
system=3D"JUNOS5.0R1.4", leap=3D11, stratum=3D16,</FONT>
<BR><FONT SIZE=3D2>>precision=3D-20, rootdelay=3D0.000, =
rootdispersion=3D6.105, peer=3D0,</FONT>
<BR><FONT SIZE=3D2>>refid=3D0.0.0.0, =
reftime=3D00000000.00000000 Thu, Feb 7 2036 =
6:28:16.000,</FONT>
<BR><FONT SIZE=3D2>>poll=3D6, clock=3Dc119f9e3.d22c343b Fri, =
Aug 30 2002 15:04:19.820, state=3D1,</FONT>
<BR><FONT SIZE=3D2>>phase=3D0.000, frequency=3D0.000, =
jitter=3D0.000, stability=3D0.000</FONT>
<BR><FONT =
SIZE=3D2>>-----------------------------------------------------------=
</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>So it seems it's not working... In fact, the =
initial difference of 16 secs</FONT>
<BR><FONT SIZE=3D2>>(<128) has widened to 36 secs in 4 =
days...</FONT>
<BR><FONT SIZE=3D2>>Any input will be welcome!</FONT>
<BR><FONT SIZE=3D2>>Thanks,</FONT>
<BR><FONT SIZE=3D2>>Javier</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT =
SIZE=3D2>>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>>juniper-nsp mailing list =
juniper-nsp@puck.nether.net</FONT>
<BR><FONT SIZE=3D2>><A =
HREF=3D"http://puck.nether.net/mailman/listinfo/juniper-nsp" =
TARGET=3D"_blank">http://puck.nether.net/mailman/listinfo/juniper-nsp</A=
></FONT>
</P>
<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>juniper-nsp mailing list =
juniper-nsp@puck.nether.net</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://puck.nether.net/mailman/listinfo/juniper-nsp" =
TARGET=3D"_blank">http://puck.nether.net/mailman/listinfo/juniper-nsp</A=
></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C2537B.78A04A6E--