R4 <-> R1 R1(config)#do sh ntp status | i Clock is Clock is synchronized, stratum 1, reference is .LOCL. R1(config)#do sh ip alias Address Type IP Address Port Interface 126.1.22.1
R4(config)#ntp authenticate R4(config)#ntp authentication-key 1 md5 CISCO R4(config)#ntp trusted-key 1 R4(config)#do sh ip route Gateway of last resort is 126.1.22.1 to network 0.0.0.0 S* 0.0.0.0/0 [1/0] via 126.1.22.1 R4(config)#ntp server 126.1.22.1 key 1 R4(config)#end R4#debug ntp validity NTP peer validity debugging is on *Mar 1 00:47:48.031: NTP: packet from 126.1.22.1 failed validity tests 10 *Mar 1 00:47:48.031: Authentication failed *Mar 1 00:47:49.051: NTP: packet from 126.1.22.1 failed validity tests 10 *Mar 1 00:47:49.055: Authentication failed *Mar 1 00:47:50.007: NTP: packet from 126.1.22.1 failed validity tests 10 *Mar 1 00:47:50.007: Authentication failed *Mar 1 00:47:51.011: NTP: packet from 126.1.22.1 failed validity tests 10 *Mar 1 00:47:51.015: Authentication failed *Mar 1 00:47:52.015: NTP: packet from 126.1.22.1 failed validity tests 10 *Mar 1 00:47:52.015: Authentication failed *Mar 1 00:47:53.063: NTP: packet from 126.1.22.1 failed validity tests 10 *Mar 1 00:47:53.063: Authentication failed *Mar 1 00:47:53.955: NTP: packet from 126.1.22.1 failed validity tests 10 *Mar 1 00:47:53.955: Authentication failed *Mar 1 00:47:55.015: NTP: packet from 126.1.22.1 failed validity tests 10 *Mar 1 00:47:55.015: Authentication failed *Mar 1 00:47:56.031: NTP: packet from 126.1.22.1 failed validity tests 10 *Mar 1 00:47:56.035: Authentication failed *Mar 1 00:47:56.999: NTP: packet from 126.1.22.1 failed validity tests 10 *Mar 1 00:47:56.999: Authentication failed *Mar 1 00:47:58.035: NTP: packet from 126.1.22.1 failed validity tests 10 *Mar 1 00:47:58.039: Authentication failed *Mar 1 00:47:59.027: NTP: packet from 126.1.22.1 failed validity tests 10 *Mar 1 00:47:59.027: Authentication failed -- Garry L. Baker "There is no 'patch' for stupidity." - www.sqlsecurity.com On Fri, Oct 8, 2010 at 8:22 AM, Áki Hermann Barkarson <[email protected]> wrote: > I have a problem with ntp auth and logging.. i have enabled "ntp logging" > and pretty much everything ntp debug command offers.. > > The only thing i can get from debugging is this (on R3) > > Mar 1 00:54:39.071: Authentication key 1 > > > R3(config)# > R3(config)#do sh ntp ass > > address ref clock st when poll reach delay offset > disp > *~127.127.7.1 127.127.7.1 4 23 64 377 0.0 0.00 > 0.0 > > > R4(config)#do sh ntp ass > > address ref clock st when poll reach delay offset > disp > ~3.3.3.3 0.0.0.0 16 12 64 0 0.0 0.00 > 16000. > * master (synced), # master (unsynced), + selected, - candidate, ~ > configured > > This is a case where i set the incorrect password and i have R4 > authenticate R3 and it fails.. i know it fails.. but i can get no logging to > verify it.. > > Please advice. How can i verify ntp authentication.. since ntp synch can > take a loong time just waiting doesn't seem like a good idea. > > -Áki > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
