Mailing List Archive: NTP service

NTP service

Sep 2, 2002, 7:52 AM

Post #1 of 10 (5247 views)

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_01C25298.BE79A528
Content-Type: text/plain;
charset="iso-8859-1"

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

------_=_NextPart_001_01C25298.BE79A528
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>NTP service</TITLE>
</HEAD>
<BODY>

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 


</BODY>
</HTML>
------_=_NextPart_001_01C25298.BE79A528--

NTP service [ In reply to ]

asim at halcyon

Sep 2, 2002, 3:08 PM

Post #2 of 10 (5098 views)

Permalink

Javier,

What is the output of 'show ntp associations"? The fact that sync_alarm is
up and that refid is 0.0.0.0 means that clock syncronization to an
external source was not made.

Also syncing won't take place if the difference is more than 128 seconds.
You may want to set your local router's time (set date) so that it is <128
secs from the time on 10.128.0.20. In addition, I am assuming you rebooted
the router, because otherwise the boot-server statement won't work.

Hope this helps.

--A

On Mon, 2 Sep 2002, Javier Alvira wrote:

> 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
>

NTP service [ In reply to ]

yikuo_chan at yahoo

Sep 2, 2002, 7:03 PM

Post #3 of 10 (5093 views)

Permalink

This is a multi-part message in MIME format.

------=_NextPart_000_007E_01C25339.779AA520
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

NTP servicehi javier :
=20
I just fix this problem last week (same hardware module & =
JUNOS)....
=20
step :
=20
1.under operational mode use set date command to set =
right time first =20
yikuo@TC_CR02> set date ?
Possible completions:
<time> New date and time =
(YYYYMMDDhhmm.ss)
yikuo@TC_CR02> set date 200209031055.00
=20
2.under configuration mode setup ntp server just =
like you done before
=20
=20

hope it can help you...=20
----- Original Message -----=20
From: Javier Alvira=20
To: juniper-nsp@puck.nether.net=20
Sent: Monday, September 02, 2002 11:52 PM
Subject: [j-nsp] NTP service

Hi all=20

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;=20

ntp {=20
boot-server 10.128.0.20;=20
server 10.128.0.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 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 strat 1 poll 6 prec -19=20
-----------------------------------=20

But this is the output for "show ntp status":=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

So it seems it's not working... In fact, the initial difference of 16 =
secs (<128) has widened to 36 secs in 4 days...=20

Any input will be welcome!=20

Thanks,=20

Javier=20

------=_NextPart_000_007E_01C25339.779AA520
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>NTP service</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>hi javier =
:</DIV>
<DIV>          &nbs=
p; =20
</DIV>
<DIV>          &nbs=
p;   I just=20
fix this problem last week (same hardware module & =
JUNOS)....</DIV>
<DIV>    </DIV>
<DIV> =20
         step =
:</DIV>
<DIV>   =20
            &=
nbsp;</DIV>
<DIV>          &nbs=
p;       =20
1.under operational mode use set date command to set=20
right time first  </DIV>
<DIV>          &nbs=
p;         =20
<A href=3D"mailto:yikuo@TC_CR02">yikuo@TC_CR02</A>> set date=20
?            &n=
bsp;        =20
Possible=20
completions:          &nb=
sp;          =20
<time>          &=
nbsp;   =20
New date and time=20
(YYYYMMDDhhmm.ss)         &nbs=
p;           =20
<A href=3D"mailto:yikuo@TC_CR02">yikuo@TC_CR02</A>> set date=20
200209031055.00</DIV>
<DIV>        =20
            </DIV>
<DIV>        =

            2.under =
configuration=20
mode setup ntp server just like you done before</DIV>
<DIV>        =

</DIV>
<DIV>          &nbs=
p;    </DIV>
<DIV> </DIV>
<DIV>        =

    hope it can help you... </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt 新細明體">----- =
Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt =
新細明體; font-color: black">From:=20
<A title=3Djalvira@nortelnetworks.com=20
href=3D"mailto:jalvira@nortelnetworks.com">Javier Alvira</A> </DIV>
<DIV style=3D"FONT: 10pt 新細明體">To: =
<A title=3Djuniper-nsp@puck.nether.net=20
=
href=3D"mailto:juniper-nsp@puck.nether.net">juniper-nsp@puck.nether.net</=
</DIV>
<DIV style=3D"FONT: 10pt =
新細明體">Sent: Monday, September 02, =
2002 11:52=20
PM</DIV>
<DIV style=3D"FONT: 10pt =
新細明體">Subject: [j-nsp] NTP =
service</DIV>
<DIV> </DIV>
Hi all 
I would like to know whether there is =
something=20
special when configuring a NTP server in a Juniper (M-10, 5.0R1.4). =
This is=20
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=20
(10.128.0.20 is the NTP server, inside customer's network): =

15:25:48.737589 Out xx.yy.zzz.44.ntp =
>=20
10.128.0.20.ntp:  v3 client strat 0 poll 6 prec -20 [tos 0x10]=20
 15:25:48.745207  In =
No-L2-hdr=20
10.128.0.20.ntp > xx.yy.zzz.44.ntp:  v3 server strat 1 poll 6 =
prec=20
-19 ----------------------------------- 
But this is the output for "show ntp=20
status": 
status=3Dc011 sync_alarm, sync_unspec, =
1 event,=20
event_restart, processor=3D"i386",=20
system=3D"JUNOS5.0R1.4", leap=3D11, stratum=3D16, precision=3D-20, rootdelay=3D0.000, rootdispersion=3D6.105, =
peer=3D0,=20
 refid=3D0.0.0.0, =
reftime=3D00000000.00000000 =20
Thu, Feb  7 2036  6:28:16.000, poll=3D6, clock=3Dc119f9e3.d22c343b  Fri, Aug 30 2002 =
15:04:19.820,=20
state=3D1, phase=3D0.000, =
frequency=3D0.000,=20
jitter=3D0.000, stability=3D0.000 -----------------------------------------------------------</FON=
T>=20
 
So it seems it's not working... In =
fact, the=20
initial difference of 16 secs (<128) has widened to 36 secs in 4=20
days... 
Any input will be welcome! 
Thanks, 
Javier =
</BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_007E_01C25339.779AA520--

-----------------------------------------------------------------
< ¨C¤Ñ³£ Yahoo!©_¼¯ > www.yahoo.com.tw

NTP service [ In reply to ]

lediaz at eurocomercial

Sep 3, 2002, 7:38 AM

Post #4 of 10 (5093 views)

Permalink

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. 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

NTP service [ In reply to ]

pgoyette at juniper

Sep 3, 2002, 8:14 AM

Post #5 of 10 (5095 views)

Permalink

I think that the answer here is easy:

A Juniper router will not provide a refernce clock field
unless the router itself is synchronized to some other
NTP source. Juniper routers cannot act as independant
(Stratum 0) time servers.

So, if Juniper-1 tries to use Juniper-2 as a time-server,
Juniper-2 must be synchronized with some other authoritative
time server, at Stratum 15 or lower.

-----Original Message-----
From: juniper-nsp-admin@puck.nether.net
[mailto:juniper-nsp-admin@puck.nether.net]On Behalf Of Luis Eduardo Díaz
Zazo
Sent: Tuesday, September 03, 2002 8:39 AM
To: Javier Alvira; juniper-nsp@puck.nether.net
Subject: RE: [j-nsp] NTP service

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. 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

NTP service [ In reply to ]

josefb at juniper

Sep 3, 2002, 8:22 AM

Post #6 of 10 (5092 views)

Permalink

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

NTP service [ In reply to ]

jalvira at nortelnetworks

Sep 3, 2002, 10:55 AM

Post #7 of 10 (5116 views)

Permalink

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>

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 [<A =
HREF=3D"mailto:josefb@juniper.net">mailto:josefb@juniper.net</A>]=

 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           &nbsp=
; <A =
HREF=3D"mailto:lediaz@eurocomercial.es">mailto:lediaz@eurocomercial.es</=
 >E-28037 Madrid
 >Espa=F1a - =
Spain           &=
nbsp;   <A HREF=3D"http://www.eurocomercial.es" =
TARGET=3D"_blank">http://www.eurocomercial.es</A>
 >-----------------------------------------------------------=

 >
 >
 >-----Mensaje original-----
 >De: juniper-nsp-admin@puck.nether.net
 >[<A =
HREF=3D"mailto:juniper-nsp-admin@puck.nether.net">mailto:juniper-nsp-adm=
in@puck.nether.net</A>]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
 ><A =
HREF=3D"http://puck.nether.net/mailman/listinfo/juniper-nsp" =
TARGET=3D"_blank">http://puck.nether.net/mailman/listinfo/juniper-nsp</A=
>


_______________________________________________
 juniper-nsp mailing list =
juniper-nsp@puck.nether.net
 <A =
HREF=3D"http://puck.nether.net/mailman/listinfo/juniper-nsp" =
TARGET=3D"_blank">http://puck.nether.net/mailman/listinfo/juniper-nsp</A=
>


</BODY>
</HTML>
------_=_NextPart_001_01C2537B.78A04A6E--

NTP service [ In reply to ]

pgoyette at juniper

Sep 3, 2002, 11:15 AM

Post #8 of 10 (5110 views)

Permalink

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>Your offset=20
is -355644 millisecs, or 355.6 seconds.  since</DIV>
<DIV>the field is=20
limited to 7 chars including the - sign, I</DIV>
<DIV>much rather=20
suspect that the offset is really 3556 seconds,</DIV>
<DIV>or just=20
under 1 hour.</DIV>
<DIV> </DIV>
<DIV>Make sure=20
your manual setting of the time accomodates any</DIV>
<DIV>time zone=20
and/or summertime/dalight saving time adjustment.</DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft>-----Original Message----- From:=20
juniper-nsp-admin@puck.nether.net=20
[mailto:juniper-nsp-admin@puck.nether.net]On Behalf Of Javier=20
Alvira Sent: Tuesday, September 03, 2002 11:55 =
AM To:=20
juniper-nsp@puck.nether.net Cc: Josef Buchsteiner;=20
lediaz@eurocomercial.es Subject: RE: [j-nsp] NTP=20
service </DIV>
Thanks to all of you for your answers. 
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...
The "show ntp association" shows this: 
    =20
remote          =20
refid      st t when poll reach  =20
delay   offset  jitter <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=20
  10.128.0.20    =20
=
.GPS.            =
1=20
u   40   64  177    =
6.716 =20
-355644 4000.00 
Thanks in advance for your comments, 
Javier 
-----Original Message----- From: Josef=20
Buchsteiner [<A=20
=
href=3D"mailto:josefb@juniper.net">mailto:josefb@juniper.net</A>] =

 Sent: martes, 03 de septiembre de 2002 17:22 =
 <FONT=20
size=3D2>To: lediaz@eurocomercial.es; Alvira, Javier =
[CAST:2541:EXCH];=20
 juniper-nsp@puck.nether.net Subject:=20
RE: [j-nsp] NTP service 
At 05:38 PM 9/3/2002, Luis Eduardo D=EDaz Zazo =
wrote:=20
 >Hello: > =
 <FONT=20
size=3D2>>I think the problem does exist. Although Asim and Yi-Kuo =
suggest=20
the reason >is that 128 seconds =
difference, if I=20
understood Javier, he already took that >in mind=20
and made himself sure that the difference didn't exist. =
 <FONT=20
size=3D2>> >I tried it in my company's =
bench and=20
found the same problem as Javier did. >=20
 >I think the problem is as follows: while trying =
to=20
synchronize a juniper to >another =
juniper, the=20
server always answers with an NTP response packet with =
 <FONT=20
size=3D2>>its reference clock field set to zero, according to the =
packet=20
analysis I >did. So the client doesn't =
accept it as=20
a good clock. But I tried to >synchronize =
a juniper=20
to another vendor's router that did answer with an NTP =
 <FONT=20
size=3D2>>response packet with a non-zero reference clock and it =
did=20
synchronize. > >I=20
presume it's a software bug in the server. 
Luis, 
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. 
I don't know if this was the case in the initial =
email.=20

regards Josef 
>  I'm using 5.1R2.4 worldwide. =
 <FONT=20
size=3D2>> >Unfortunately enough, one =
can't trace=20
this with juniper's trace flags, since >there isn't=20
any for NTP. > <FONT=20
size=3D2>>Regards, > <FONT=20
=
size=3D2>>-----------------------------------------------------------<=
/FONT>=20
 >Luis Eduardo D=EDaz=20
Zazo       Tel: +34 914 359 687 =
 <FONT=20
size=3D2>>Eurocomercial I&C =
S.A.       Fax:=20
+34 914 313 240 >Valent=EDn Beato=20
=
5            =
<A=20
=
href=3D"mailto:lediaz@eurocomercial.es">mailto:lediaz@eurocomercial.es</A=
>=20
 >E-28037 Madrid >Espa=F1a -=20
=
Spain           &n=
bsp;  =20
<A target=3D_blank=20
=
href=3D"http://www.eurocomercial.es">http://www.eurocomercial.es</A></FON=
 <FONT=20
=
size=3D2>>-----------------------------------------------------------<=
/FONT>=20
 > > =
 <FONT=20
size=3D2>>-----Mensaje original----- >De:=20
juniper-nsp-admin@puck.nether.net >[<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 >Enviado el: =
lunes 2 de=20
septiembre de 2002 17:52 >Para:=20
juniper-nsp@puck.nether.net >Asunto: =
[j-nsp] NTP=20
service > >=20
 >Hi all >I would =
like to know=20
whether there is something special when configuring a >NTP server in a Juniper (M-10, 5.0R1.4). This is what I=20
configured: > >=20
 >time-zone Europe/Lisbon; <FONT=20
size=3D2>>ntp > <FONT=20
size=3D2>>     boot-server 10.128.0.20; =
 <FONT=20
size=3D2>>     server 10.128.0.20; =
 <FONT=20
size=3D2>>} <FONT=20
size=3D2>>------------------------------------- <FONT=20
size=3D2>> > >The=20
"monitor traffic interface fe-0/0/0" shows this (10.128.0.20 is the =
NTP=20
 >server, inside customer's network): =
 <FONT=20
size=3D2>>15:25:48.737589 Out xx.yy.zzz.44.ntp > =
10.128.0.20.ntp:  v3=20
client strat 0 >poll 6 prec -20 [tos =
0x10]=20
 >15:25:48.745207  In No-L2-hdr =
10.128.0.20.ntp >=20
xx.yy.zzz.44.ntp:  v3 server >strat =
1 poll 6=20
prec -19 <FONT=20
size=3D2>>----------------------------------- <FONT=20
size=3D2>> > >But this=20
is the output for "show ntp status": >=20
 > >status=3Dc011 =
sync_alarm,=20
sync_unspec, 1 event, event_restart, <FONT=20
size=3D2>>processor=3D"i386", system=3D"JUNOS5.0R1.4", leap=3D11,=20
stratum=3D16, >precision=3D-20, =
rootdelay=3D0.000,=20
rootdispersion=3D6.105, peer=3D0, >refid=3D0.0.0.0,=20
reftime=3D00000000.00000000  Thu, Feb  7 2036 =20
6:28:16.000, >poll=3D6, =
clock=3Dc119f9e3.d22c343b =20
Fri, Aug 30 2002 15:04:19.820, state=3D1, <FONT=20
size=3D2>>phase=3D0.000, frequency=3D0.000, jitter=3D0.000, =
stability=3D0.000=20
 <FONT=20
=
size=3D2>>-----------------------------------------------------------<=
/FONT>=20
 > > =
 <FONT=20
size=3D2>>So it seems it's not working... In fact, the initial =
difference of=20
16 secs >(<128) has widened to 36 secs =
in 4=20
days... >Any input will be =
welcome!=20
 >Thanks, >Javier=20
 > <FONT=20
size=3D2>>_______________________________________________ =
 <FONT=20
size=3D2>>juniper-nsp mailing list =
juniper-nsp@puck.nether.net=20
 ><A target=3D_blank=20
=
href=3D"http://puck.nether.net/mailman/listinfo/juniper-nsp">http://puck.=
nether.net/mailman/listinfo/juniper-nsp</A>=20

_______________________________________________=20
 juniper-nsp mailing list =
juniper-nsp@puck.nether.net=20
 <A target=3D_blank=20
=
href=3D"http://puck.nether.net/mailman/listinfo/juniper-nsp">http://puck.=
nether.net/mailman/listinfo/juniper-nsp</A>=20
</BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0072_01C25343.92C69FC0--

NTP service [ In reply to ]

jalvira at nortelnetworks

Sep 3, 2002, 3:57 PM

Post #9 of 10 (5117 views)

Permalink

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>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!</DIV>
<DIV> </DIV>
<DIV>By the
way, the daylight saving time setting, is configurable
somewhere...?</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV> </DIV>
<DIV>Javier</DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV align=left class=OutlookMessageHeader dir=ltr>-----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 </DIV>
<DIV>Your
offset is -355644 millisecs, or 355.6 seconds.  since</DIV>
<DIV>the field
is limited to 7 chars including the - sign, I</DIV>
<DIV>much
rather suspect that the offset is really 3556 seconds,</DIV>
<DIV>or just
under 1 hour.</DIV>
<DIV> </DIV>
<DIV>Make sure
your manual setting of the time accomodates any</DIV>
<DIV>time zone
and/or summertime/dalight saving time adjustment.</DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV align=left class=OutlookMessageHeader dir=ltr>-----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 </DIV>
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 [<A
href="mailto:josefb@juniper.net">mailto:josefb@juniper.net</A>]
 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             <A
href="mailto:lediaz@eurocomercial.es">mailto:lediaz@eurocomercial.es</A>
 >E-28037 Madrid >España -
Spain              
<A href="http://www.eurocomercial.es"
target=_blank>http://www.eurocomercial.es</A> >-----------------------------------------------------------
 > > >-----Mensaje original----- >De:
juniper-nsp-admin@puck.nether.net >[<A
href="mailto:juniper-nsp-admin@puck.nether.net">mailto:juniper-nsp-admin@puck.nether.net</A>]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
 ><A
href="http://puck.nether.net/mailman/listinfo/juniper-nsp"
target=_blank>http://puck.nether.net/mailman/listinfo/juniper-nsp</A>

_______________________________________________
 juniper-nsp mailing list juniper-nsp@puck.nether.net
 <A
href="http://puck.nether.net/mailman/listinfo/juniper-nsp"
target=_blank>http://puck.nether.net/mailman/listinfo/juniper-nsp</A>
</BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C253A5.B086FDC2--

NTP service [ In reply to ]

pgoyette at juniper

Sep 3, 2002, 4:13 PM

Post #10 of 10 (5094 views)

Permalink

This is a multi-part message in MIME format.

------=_NextPart_000_0012_01C2536D.44AEEB10
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

RE: [j-nsp] NTP serviceDaylight Savings Time is automatically enabled for
the locally
configured timezone, based on the timezone rules.
-----Original Message-----
From: Javier Alvira [mailto:jalvira@nortelnetworks.com]
Sent: Tuesday, September 03, 2002 4:58 PM
To: Paul Goyette; juniper-nsp@puck.nether.net
Cc: Josef Buchsteiner; lediaz@eurocomercial.es
Subject: RE: [j-nsp] NTP service

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!

By the way, the daylight saving time setting, is configurable
somewhere...?

Thanks,

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.

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_0012_01C2536D.44AEEB10
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>Daylight=20
Savings Time is automatically enabled for the =
locally</DIV>
<DIV>configured=20
timezone, based on the timezone rules.</DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft>-----Original Message----- From: Javier Alvira=20
[mailto:jalvira@nortelnetworks.com] Sent: Tuesday, September =
03,=20
2002 4:58 PM To: Paul Goyette;=20
juniper-nsp@puck.nether.net Cc: Josef Buchsteiner;=20
lediaz@eurocomercial.es Subject: RE: [j-nsp] NTP=20
service </DIV>
<DIV><SPAN=20
class=3D238320621-03092002>Thanks Paul, it worked! I had to correct =
the timezone=20
offset... It seems that Juniper itself modified the initial right time =
as soon=20
as I configured the timezone, and I didn't notice it before. Now the =
time is=20
ok (1 hour less), and the Juniper is, at long =
last, in the=20
syncing process!</DIV>
<DIV><SPAN=20
class=3D238320621-03092002> </DIV>
<DIV>By=20
the way, the daylight saving time setting, is configurable=20
somewhere...?</DIV>
<DIV><SPAN=20
class=3D238320621-03092002> </DIV>
<DIV><SPAN=20
class=3D238320621-03092002>Thanks,</DIV>
<DIV><SPAN=20
class=3D238320621-03092002> </DIV>
<DIV><SPAN=20
class=3D238320621-03092002>Javier</DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
size=3D2>-----Original Message----- From: Paul Goyette=20
[mailto:pgoyette@juniper.net] Sent: martes, 03 de =
septiembre de=20
2002 20:15 To: Alvira, Javier [CAST:2541:EXCH];=20
juniper-nsp@puck.nether.net Cc: Josef Buchsteiner;=20
lediaz@eurocomercial.es Subject: RE: [j-nsp] NTP=20
service </DIV>
<DIV>Your=20
offset is -355644 millisecs, or 355.6 seconds. =20
since</DIV>
<DIV>the=20
field is limited to 7 chars including the - sign, =
I</DIV>
<DIV>much=20
rather suspect that the offset is really 3556 =
seconds,</DIV>
<DIV>or just=20
under 1 hour.</DIV>
<DIV> </DIV>
<DIV>Make=20
sure your manual setting of the time accomodates =
any</DIV>
<DIV>time=20
zone and/or summertime/dalight saving time =
adjustment.</DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft>-----Original Message----- From:=20
juniper-nsp-admin@puck.nether.net=20
[mailto:juniper-nsp-admin@puck.nether.net]On Behalf Of =
Javier=20
Alvira Sent: Tuesday, September 03, 2002 11:55 =
AM To:=20
juniper-nsp@puck.nether.net Cc: Josef Buchsteiner;=20
lediaz@eurocomercial.es Subject: RE: [j-nsp] NTP=20
service </DIV>
Thanks to all of you for your answers. =

The truth is that I already manually set the =
time in order=20
to be <128 secs close to the NTP reference server =
(10.128.0.20), which=20
actually is just a NTP server. Other devices querying it are =
properly in=20
sync...
The "show ntp association" shows this: =

    =20
remote           =

refid      st t when poll =
reach  =20
delay   offset  jitter <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=20
  10.128.0.20    =20
=
.GPS.            =
1=20
u   40   64  177    =
6.716 =20
-355644 4000.00 
Thanks in advance for your comments, 
Javier 
-----Original Message----- From:=20
Josef Buchsteiner [<A=20
=
href=3D"mailto:josefb@juniper.net">mailto:josefb@juniper.net</A>] =

 Sent: martes, 03 de septiembre de 2002 =
17:22=20
 To: lediaz@eurocomercial.es; Alvira, Javier=20
[CAST:2541:EXCH]; <FONT=20
size=3D2>juniper-nsp@puck.nether.net Subject: RE:=20
[j-nsp] NTP service 
At 05:38 PM 9/3/2002, Luis Eduardo D=EDaz Zazo =
wrote:=20
 >Hello: > <FONT=20
size=3D2>>I think the problem does exist. Although Asim and =
Yi-Kuo=20
suggest the reason >is that 128 =
seconds=20
difference, if I understood Javier, he already took that =
 <FONT=20
size=3D2>>in mind and made himself sure that the difference =
didn't=20
exist. > >I tried it=20
in my company's bench and found the same problem as Javier =
did.=20
 > >I think the =
problem is=20
as follows: while trying to synchronize a juniper to =
 <FONT=20
size=3D2>>another juniper, the server always answers with an =
NTP response=20
packet with >its reference clock =
field set to=20
zero, according to the packet analysis I >did.=20
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=20
did answer with an NTP >response =
packet with a=20
non-zero reference clock and it did synchronize. <FONT=20
size=3D2>> >I presume it's a =
software bug in=20
the server. 
Luis, 
Juniper can not act as a reference Server on =
it's=20
own. So you need to have a proper =
reference server=20
to be able to synchronize. This is how =
it is=20
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. =
 <FONT=20
size=3D2>> >Unfortunately enough, =
one can't=20
trace this with juniper's trace flags, since <FONT=20
size=3D2>>there isn't any for NTP. >=20
 >Regards, >=20
 <FONT=20
=
size=3D2>>-----------------------------------------------------------<=
/FONT>=20
 >Luis Eduardo D=EDaz=20
Zazo       Tel: +34 914 359 =
687=20
 >Eurocomercial I&C=20
S.A.       Fax: +34 914 313 =
240=20
 >Valent=EDn Beato=20
=
5            =
=20
<A=20
=
href=3D"mailto:lediaz@eurocomercial.es">mailto:lediaz@eurocomercial.es</A=
>=20
 >E-28037 Madrid >Espa=F1a -=20
=
Spain           &n=
bsp;  =20
<A target=3D_blank=20
=
href=3D"http://www.eurocomercial.es">http://www.eurocomercial.es</A></FON=
 <FONT=20
=
size=3D2>>-----------------------------------------------------------<=
/FONT>=20
 > > =
 <FONT=20
size=3D2>>-----Mensaje original----- >De:=20
juniper-nsp-admin@puck.nether.net >[<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 >Enviado el: =
lunes 2 de=20
septiembre de 2002 17:52 >Para:=20
juniper-nsp@puck.nether.net >Asunto: =
[j-nsp]=20
NTP service > <FONT=20
size=3D2>> >Hi all =
 <FONT=20
size=3D2>>I would like to know whether there is something =
special when=20
configuring a >NTP server in a =
Juniper (M-10,=20
5.0R1.4). This is what I configured: >=20
 > >time-zone=20
Europe/Lisbon; >ntp <FONT=20
size=3D2>> >    =20
boot-server 10.128.0.20; <FONT=20
size=3D2>>     server 10.128.0.20; =
 <FONT=20
size=3D2>>} <FONT=20
size=3D2>>------------------------------------- =
 <FONT=20
size=3D2>> > >The=20
"monitor traffic interface fe-0/0/0" shows this (10.128.0.20 is =
the=20
NTP >server, inside customer's =
network):=20
 >15:25:48.737589 Out xx.yy.zzz.44.ntp >=20
10.128.0.20.ntp:  v3 client strat 0 >poll=20
6 prec -20 [tos 0x10] >15:25:48.745207  In=20
No-L2-hdr 10.128.0.20.ntp > xx.yy.zzz.44.ntp:  v3 =
server=20
 >strat 1 poll 6 prec -19 <FONT=20
size=3D2>>----------------------------------- <FONT=20
size=3D2>> > >But=20
this is the output for "show ntp status": <FONT=20
size=3D2>> > <FONT=20
size=3D2>>status=3Dc011 sync_alarm, sync_unspec, 1 event,=20
event_restart, >processor=3D"i386",=20
system=3D"JUNOS5.0R1.4", leap=3D11, stratum=3D16, >precision=3D-20, rootdelay=3D0.000, =
rootdispersion=3D6.105,=20
peer=3D0, >refid=3D0.0.0.0,=20
reftime=3D00000000.00000000  Thu, Feb  7 2036 =20
6:28:16.000, >poll=3D6,=20
clock=3Dc119f9e3.d22c343b  Fri, Aug 30 2002 15:04:19.820,=20
state=3D1, >phase=3D0.000, =
frequency=3D0.000,=20
jitter=3D0.000, stability=3D0.000 <FONT=20
=
size=3D2>>-----------------------------------------------------------<=
/FONT>=20
 > > =
 <FONT=20
size=3D2>>So it seems it's not working... In fact, the initial =
difference=20
of 16 secs >(<128) has widened to =
36 secs in=20
4 days... >Any input will be =
welcome!=20
 >Thanks, >Javier=20
 > <FONT=20
=
size=3D2>>_______________________________________________=20
 >juniper-nsp mailing list=20
juniper-nsp@puck.nether.net ><A =
target=3D_blank=20
=
href=3D"http://puck.nether.net/mailman/listinfo/juniper-nsp">http://puck.=
nether.net/mailman/listinfo/juniper-nsp</A>=20

_______________________________________________=20
 juniper-nsp mailing list=20
juniper-nsp@puck.nether.net <A =
target=3D_blank=20
=
href=3D"http://puck.nether.net/mailman/listinfo/juniper-nsp">http://puck.=
nether.net/mailman/listinfo/juniper-nsp</A>=20
</BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0012_01C2536D.44AEEB10--