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