Re: Trouble with NTP, some clients just don't sync once

From: Edison Ortiz (edisonmortiz@gmail.com)
Date: Sun Feb 25 2007 - 17:31:50 ART


When configuring NTP authentication, order of operation is vital. What's the
'show ntp ass det' from R3
and R6 ?

You are also missing a peer from R6 to R3.

  ----- Original Message -----
  From: Ryan
  To: Edison Ortiz
  Cc: Cisco certification
  Sent: Sunday, February 25, 2007 1:57 PM
  Subject: Re: Trouble with NTP, some clients just don't sync once
authenitciated

  Password is 'CISCO'

  For R3 (3640)
  !
  ntp authentication-key 1 md5 123A2C243124 7
  ntp authenticate
  ntp trusted-key 1
  ntp peer 150.1.6.6
  ntp server 204.12.1.254 key 1
  !

  For R6 (3640)
  !
  ntp authentication-key 1 md5 112A3036343D 7
  ntp authenticate
  ntp trusted-key 1
  ntp clock-period 17179875
  ntp server 54.1.1.254 key 1
  !

  For R1 (2620), R2 (2620),and SW1 (3560), with R3 as their server.
  !
  ntp server 150.1.3.3
  !

  For R4(3640), R5(3640), and SW4(3550), with R6 as their server.
  !
  ntp clock-period 17179866
  ntp server 150.1.6.6
  !

  The clock-period number is slightly different. This was part of the config
was not populated by me.

  And it works fine if R3 and R6 are not authenticating. I have full
reachability and no ACL's. But once I authenticate from R3, R1, R2 and SW1
stop syncing. (not problems from R6 group once R6 authenticates)

  It's very strange. What makes it more puzzling is I lost points on a Mock
Lab for the the same scenario. I was missing the "ntp server <server> key 1
field, but now, even with it in, it's broke...

  I'm puzzled...

  -Ryan

  On 2/25/07, Edison Ortiz <edisonmortiz@gmail.com > wrote:
    Can you post the ntp portion of your configs ?

    ----- Original Message -----
    From: "Ryan" <ryan95842@gmail.com>
    To: "Cisco certification" <ccielab@groupstudy.com>
    Sent: Saturday, February 24, 2007 9:06 PM
    Subject: Trouble with NTP, some clients just don't sync once
authenitciated

> Having some trouble with NTP. Task is to have R3 get time form BB3 and
R6
> from BB1. No big deal. Then we are to have R1,R2, and SW1 get time from
R3
> and R4, R5, and SW4 get time from R6. Again, no big deal. Then we are
to
> have R3 and R6 peer. This all works and every one gets sync'd. No
problems
> so far.
>
> Then we need to authenticate R3 and R6. Not a problem. Both R3 and R6
get
> authenticated.
>
> Now the problem is, the routers pulling time from R3 won't sync
anymore.
> The
> ones pulling from R6 do though. (R3 and R6 are both 3640's running 12.4
> (10b))
>
> Any thoughts as to why R1, R2, and SW1 will no longer sync?
>
>
>
> -Ryan
>
>
>
>
> Rack1R1#
> Rack1R1#sh run | inc ntp
> ntp server 150.1.3.3
> Rack1R1#sh ntp status
> Clock is unsynchronized, stratum 16, no reference clock
> nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is
> 2**18
> reference time is 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)
> clock offset is 0.0000 msec, root delay is 0.00 msec
> root dispersion is 0.00 msec, peer dispersion is 0.00 msec
> Rack1R1#
>
> Rack1R2#sh run | inc ntp
> ntp server 150.1.3.3
> Rack1R2#sh ntp status
> Clock is unsynchronized, stratum 16, no reference clock
> nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is
> 2**18
> reference time is 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)
> clock offset is 0.0000 msec, root delay is 0.00 msec
> root dispersion is 0.00 msec, peer dispersion is 0.00 msec
> Rack1R2#
>
> Rack1R3#sh run | inc ntp
> ntp authentication-key 1 md5 123A2C243124 7
> ntp authenticate
> ntp trusted-key 1
> ntp peer 150.1.6.6
> ntp server 204.12.1.254 key 1
> Rack1R3#sh ntp status
> Clock is synchronized, stratum 5, reference is 204.12.1.254
> nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is
> 2**18
> reference time is AF3C323E.0832087B (06:57:02.032 UTC Mon Mar 1 1993)
> clock offset is -0.8067 msec, root delay is 6.91 msec
> root dispersion is 10480.99 msec, peer dispersion is 10480.15 msec
> Rack1R3#
>
> Rack1R4#sh run | inc ntp
> ntp clock-period 17179866
> ntp server 150.1.6.6
> Rack1R4#sh ntp status
> Clock is synchronized, stratum 6, reference is 150.1.6.6
> nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is
> 2**18
> reference time is AF3C3256.F2680AEA (06:57:26.946 UTC Mon Mar 1 1993)
> clock offset is - 0.3338 msec, root delay is 65.70 msec
> root dispersion is 2.85 msec, peer dispersion is 0.24 msec
> Rack1R4#
>
> Rack1R5#sh run | inc ntp
> ntp clock-period 17179865
> ntp server 150.1.6.6
> Rack1R5#sh ntp status
> Clock is synchronized, stratum 6, reference is 150.1.6.6
> nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is
> 2**18
> reference time is AF3C3256.9D7AC4AB (06:57:26.615 UTC Mon Mar 1 1993)
> clock offset is -0.6593 msec, root delay is 110.63 msec
> root dispersion is 5.52 msec, peer dispersion is 2.58 msec
> Rack1R5#
>
> Rack1R6#sh run | inc ntp
> ntp authentication-key 1 md5 112A3036343D 7
> ntp authenticate
> ntp trusted-key 1
> ntp clock-period 17179875
> ntp server 54.1.1.254 key 1
> Rack1R6#sh ntp status
> Clock is synchronized, stratum 5, reference is 54.1.1.254
> nominal freq is 250.0000 Hz, actual freq is 249.9999 Hz, precision is
> 2**18
> reference time is AF3C3269.75801229 (06:57:45.458 UTC Mon Mar 1 1993)
> clock offset is 2.2310 msec, root delay is 61.92 msec
> root dispersion is 2.35 msec, peer dispersion is 0.09 msec
> Rack1R6#
>
> Rack1SW1#
> Rack1SW1#sh run | inc ntp
> ntp server 150.1.3.3
> Rack1SW1#sh ntp status
> Clock is unsynchronized, stratum 16, no reference clock
> nominal freq is 119.2092 Hz, actual freq is 119.2092 Hz, precision is
> 2**18
> reference time is AF3C2E9A.8D365A38 (06:41:30.551 UTC Mon Mar 1 1993)
> clock offset is 0.4110 msec, root delay is 75.61 msec
> root dispersion is 1.30 msec, peer dispersion is 0.11 msec
> Rack1SW1#
>
> Rack1SW4#sh run | inc ntp
> ntp clock-period 17179935
> ntp server 150.1.6.6
> Rack1SW4#sh ntp status
> Clock is synchronized, stratum 6, reference is 150.1.6.6
> nominal freq is 250.0000 Hz, actual freq is 249.9990 Hz, precision is
> 2**18
> reference time is AF3C32A2.90F0B536 (06:58:42.566 UTC Mon Mar 1 1993)
> clock offset is 7.2399 msec, root delay is 110.20 msec
> root dispersion is 12.77 msec, peer dispersion is 3.17 msec
> Rack1SW4#
>
>
>
>
> EOF
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Thu Mar 01 2007 - 07:38:48 ART