From: Jason Madsen (madsen.jason@gmail.com)
Date: Sun Nov 16 2008 - 13:36:09 ARST
Hello,
Your NTP config' looks fine as long as your keystrings match. Is your basic
layer 2/3 frame info' correct? Do you have any ACLs applied? Ensure
you're permitting UDP port 123 bidirectionally between your spokes and your
hub. Did you check your NTP status before applying the authentication?
Jason
On Sun, Nov 16, 2008 at 7:01 AM, GAURAV MADAN <gauravmadan1177@gmail.com>wrote:
> Hi Group
>
> Somehow I am not getting my NTP synchronised . Can someone help me in this
> .
> I have R1
> / \
> / \
> R2 R3
> R1 as Hub and R2 and R3 as spokes
>
> R1 as NTP server and R2 and R3 as clients.
>
> R1
> ******
> R1(config)#do sh run | inc ntp
> ntp authentication-key 1 md5 02250D480809 7
> ntp master 2
>
> R2
> **********
> R2(config)#do sh run | inc ntp
> ntp authentication-key 1 md5 0802455D0A16 7
> ntp authenticate
> ntp trusted-key 1
> ntp server 131.1.12.1 key 1 prefer
> R2(config)#
>
> R3
> **********
> R3(config)#do sh run | inc ntp
> ntp authentication-key 1 md5 01300F175804 7
> ntp authenticate
> ntp trusted-key 1
> ntp server 131.1.13.1 key 1 prefer
> R3(config)#
>
> NTP status on R2 as well as R3 remians unsynch :
>
> R3(config)#do sh ntp sta
> Clock is unsynchronized, stratum 16, no reference clock
> nominal freq is 250.0000 Hz, actual freq is 249.9822 Hz, precision is 2**24
> 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
> loopfilter state is 'FSET' (Drift set from file), drift is 0.000070901 s/s
> system poll interval is 64, never updated.
> R3(config)#
>
> I am getting following on enabling debugs . I guess I have made no
> mistake in config . Please do point out if any :
>
> R3(config)#
> *Nov 16 14:13:41.981: NTP message sent to 131.1.13.1, from interface
> 'Serial0/0/0.31' (131.1.13.3).
> *Nov 16 14:13:42.033: NTP message received from 131.1.13.1 on
> interface 'Serial0/0/0.31' (131.1.13.3).
> *Nov 16 14:13:42.033: NTP Core(DEBUG): ntp_receive: message received
> *Nov 16 14:13:42.033: NTP Core(DEBUG): ntp_receive: peer is
> 0x471D86C0, next action is 1.
> *Nov 16 14:13:42.033: NTP Core(NOTICE): ntp_receive: dropping message:
> crypto-NAK.
> R3(config)#
> *Nov 16 14:14:40.985: NTP message sent to 131.1.13.1, from interface
> 'Serial0/0/0.31' (131.1.13.3).
> *Nov 16 14:14:41.037: NTP message received from 131.1.13.1 on
> interface 'Serial0/0/0.31' (131.1.13.3).
> *Nov 16 14:14:41.037: NTP Core(DEBUG): ntp_receive: message received
> *Nov 16 14:14:41.037: NTP Core(DEBUG): ntp_receive: peer is
> 0x471D86C0, next action is 1.
> *Nov 16 14:14:41.037: NTP Core(NOTICE): ntp_receive: dropping message:
> crypto-NAK.
> R3(config)#
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Dec 01 2008 - 08:18:30 ARST