From: Pickell, Aaryn (Aaryn.Pickell@xxxxxxxxxxxxx)
Date: Thu Jun 07 2001 - 15:53:34 GMT-3
The sh ntp association you have is from R1? That looks like what I would
expect from R2, actually. On R2, you need to have the trusted-key command
for authentication to work.
Aaryn Pickell - CCNP ATM, CCDP, MCSE
Senior Engineer - Routing Protocols
Getronics Inc.
Direct: 713-394-1609
Email:aaryn.pickell@getronics.com
This e-mail message and any attachments are confidential and may be
privileged. If you are not the intended recipient, please notify me
immediately by replying to this message and please destroy all copies of
this message and attachments. Thank you.
> -----Original Message-----
> From: Richard Geiger [mailto:geiger_rich@hotmail.com]
> Sent: Thursday, June 07, 2001 1:32 PM
> To: ccielab@groupstudy.com
> Subject: NTP Question
>
>
> My problem appears to be that the master clock does not
> recognize it's own
> clock as the master ..??? Authentication is working fine.
>
> Please help I am scheduled next for the Lab Next monday in the
> Great White North...
>
> Here is the config and the results..
>
>
>
> RTR1
> clock timezone CST -6
> clock summer-time CDT recurring
> ntp authentication-key 1 md5 070C285F4D060D0C1A17 7
> ntp authenticate
> ntp trusted-key 1
> ntp source Loopback0
> ntp master
>
>
> RTR2
> !
> clock timezone CST -6
> clock summer-time CDT recurring
> ntp authentication-key 1 md5 094F471A1A0A031B0609 7
> ntp authenticate
> ntp broadcastdelay 15
> ntp server 16.16.16.16 key 1
>
> 1#sh ntp a
>
> address ref clock st when poll reach
> delay offset
> disp
> ~16.16.16.16 0.0.0.0 16 18 64 0
> 0.0 0.00
> 16000.
> * master (synced), # master (unsynced), + selected, - candidate, ~
> configured
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:20 GMT-3