Hi All,
I faced the same too when I do NTP lab. It takes very long to Syn but sometime
fast. No idea why fast and why slow.
Not much difference on GNS3 lab and Proctor Lab too.
From command reference guide, there's burst Keyword with ntp peer/ ntp server.
Not sure it will make any difference or not. But I didnt try on the time and
havent tried with IPv6 too.
Cisco command reference guide/ Network management command/
ntp server {vrf vrf-name | ip-address| ipv6-address| ipv4| ipv6| hostname}
[normal-sync] [versionnumber] [keykey-id] [sourceinterface]
[prefer][maxpollnumber] [minpollnumber] [burst] [iburst]
ntp peer {vrf vrf-name | ip-address| ipv6-address| ipv4| ipv6| hostname}
[normal-sync] [versionnumber] [keykey-id] [sourceinterface]
[prefer][maxpollnumber] [minpollnumber] [burst] [iburst]
If you are using NTPv4, the NTP synchronization takes more
time to complete unlike NTPv3, which syncs in seconds or a maximum of 1 to 2
minutes. The acceptable time for sync in case of NTPv4 is 15 to 20 minutes. To
achieve faster NTP synchronization, enable the burst or iburst modes by using
the burst or iburst keywords. With
the burst or iburst mode configured, NTP synchronization takes about 1 to 2
minutes to sync.
My $0.2
Phyo..
________________________________
From: Marc Abel <[email protected]>
To: Joe Astorino <[email protected]>; Michael Lipsey
<[email protected]>
Cc: "[email protected]" <[email protected]>
Sent: Sunday, October 25, 2009 10:23:05
Subject: Re: [OSL | CCIE_RS] NTP issues
I had one where a reload did not sync it. About 8 minutes after the reload it
finally synced.
________________________________
Joe Astorino wrote
Sometimes NTP takes FOREVER. Generally, the more unsynced the clocks are , the
longer it takes. A reload on the client actually usually seems to fix things
right away in my experience. Let us know!
On Sat, Oct 24, 2009 at 7:57 PM, Michael Lipsey <[email protected]> wrote:
>
>
>
>
>
>
>
>
>
>
>>
>>
>I think it just takes time, about 10 minutes seems to be the
>number. If you use the command show ntp ass detail you can see the filtoffset
>and filterror change with each poll (about every minute).
>
>There are 8 samples shown.
>
>Once things normalize up it appears to work. The idea I guess is
>to be patient.
>
>I dislike NTP today.
>
>-mike
>
>>
>>
>From:Adrian Brayton
>[mailto:[email protected]]
>Sent: Saturday, October 24, 2009 4:08 PM
>
>To: Michael Lipsey
>Cc: [email protected]
>Subject: Re: [OSL | CCIE_RS] NTP issues >
>
>Hey Michael,
>>
>>
>
>>
>I havent tried this in a lab but what if you...
>>
>
>>
>r1 - NTP master 1
>>
>
>>
>r2 - ntp ser "r1"
>>
>
>>
>r4 - ntp peer "r2"
>>
>
>>
>r5 - ntp peer "r4"
>>
>
>>
>and so on... That just might work!
>>
>
>>
>
>>
>>
>>
>On Oct 24, 2009, at 6:28 PM, Michael Lipsey wrote:
>
>
>
>>
>>
>>
>I
>know this is going to sound lame, it really should be easier than this. This is
>exactly the kind of thing that scares me about the lab. Getting hung up on a
>relatively minor issue for the entire 8 hours (5.5 now).
>>
>
>>
>So,
>I’m doing a simple lab, lab one from V3.
>>
>
>>
>It
>has an NTP configuration in it that is nested. One Router is the next’s server
>so that the stratum levels match the routers’ number.
>>
>
>>
>R1
>is the master
>>
>
>>
>Ntp
>master 1
>>
>
>>
>R2
>is the next router
>>
>
>>
>Ntp
>server 1.1.1.1
>>
>
>>
>R2#sho
>ntp ass de
>>
>1.1.1.1
>configured, our_master, sane, valid, stratum 1
>>
>ref
>ID .LOCL., time CE8D9A76.4CBCB578 (15:23:34.299 UTC Sat Oct 24 2009)
>>
>our
>mode client, peer mode server, our poll intvl 64, peer poll intvl 64
>>
>root
>delay 0.00 msec, root disp 0.33, reach 377, sync dist 0.00
>>
>delay
>0.00 msec, offset 78.6275 msec, dispersion 4.38
>>
>precision
>2**24, version 4
>>
>org
>time CE8D9A7E.3D78B26B (15:23:42.240 UTC Sat Oct 24 2009)
>>
>rec
>time CE8D9A7E.2940579C (15:23:42.161 UTC Sat Oct 24 2009)
>>
>xmt
>time CE8D9A7E.28C041FC (15:23:42.159 UTC Sat Oct 24 2009)
>>
>filtdelay
>= 0.00 0.00
>0.00 0.00 0.00
>0.00 0.00 0.00
>>
>filtoffset
>= 0.07 0.07
>0.07 0.07 0.07
>0.07 0.07 0.07
>>
>filterror
>= 0.00 0.00
>0.00 0.00 0.00
>0.00 0.00 0.00
>>
>minpoll
>= 6, maxpoll = 10
>>
>
>>
>R2#sho
>ntp status
>>
>Clock
>is synchronized, stratum 2, reference is 1.1.1.1
>>
>nominal
>freq is 250.0000 Hz, actual freq is 249.9996 Hz, precision is 2**24
>>
>reference
>time is CE8D98F7.22AC15AC (15:17:11.135 UTC Sat Oct 24 2009)
>>
>clock
>offset is 0.0786 msec, root delay is 0.00 msec
>>
>root
>dispersion is 0.09 msec, peer dispersion is 0.00 msec
>>
>loopfilter
>state is 'CTRL' (Normal Controlled Loop), drift is 0.000001405 s/s
>>
>system
>poll interval is 64, last update was 425 sec ago.
>>
>
>>
>Cat1
>is the next router
>>
>
>>
>Ntp
>server 2.2.2.2
>>
>
>>
>Cat1(config)#do
>sho ntp status
>>
>Clock
>is synchronized, stratum 3, reference is 2.2.2.2
>>
>nominal
>freq is 119.2092 Hz, actual freq is 119.2099 Hz, precision is 2**18
>>
>reference
>time is CE8D9A7B.CCF8C226 (15:23:39.800 UTC Sat Oct 24 2009)
>>
>clock
>offset is -3.8897 msec, root delay is 4.18 msec
>>
>root
>dispersion is 109.94 msec, peer dispersion is 15.37 msec
>>
>
>>
>R4
>is supposed to be the next router however for the life of me I can’t get it to
>sync. I had trouble with R2 as well but worked through that by removing and
>reading the NTP config a few times on R1 and R2 – desperation more than
>troubleshooting.
>>
>
>>
>R4(config)#do
>sho ntp as de
>>
>35.35.35.35
>configured, insane, invalid, stratum 3
>>
>ref
>ID 2.2.2.2 , time CE8D9ABB.CC07E26C
>(15:24:43.796 UTC Sat Oct 24 2009)
>>
>our
>mode client, peer mode server, our poll intvl 64, peer poll intvl 64
>>
>root
>delay 0.00 msec, root disp 108.85, reach 177, sync dist 70.83
>>
>delay
>0.00 msec, offset 43176.9866 msec, dispersion 64.77
>>
>precision
>2**18, version 4
>>
>org
>time CE8D9AE1.ACF0A68B (15:25:21.675 UTC Sat Oct 24 2009)
>>
>rec
>time CE8D9AB6.80471CB0 (15:24:38.501 UTC Sat Oct 24 2009)
>>
>xmt
>time CE8D9AB6.7EFF0FC9 (15:24:38.496 UTC Sat Oct 24 2009)
>>
>filtdelay
>= 0.00 0.00
>0.00 0.01 0.00
>0.00 0.00 0.00
>>
>filtoffset
>= 43.17 43.17 43.17
>43.18 43.18 -79.19 -79.19 0.00
>>
>filterror
>= 0.00 0.00
>0.00 0.00 0.00
>0.00 0.00 16.00
>>
>minpoll
>= 6, maxpoll = 10
>>
>
>>
>I
>can’t for the life of me figure out why this thing won’t sync to Cat1 (or
>anything else for that matter).
>>
>
>>
>HELP!
>I have already spent 2 and half hours on this foolishness!
>>
>
>>
>
>>
>Thanks
>guys.
>>
>
>>
>-Mike
>_______________________________________________
>>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
>
>
--
Regards,
Joe Astorino CCIE #24347 (R&S)
Sr. Technical Instructor - IPexpert
Mailto: [email protected]
Telephone: +1.810.326.1444
Live Assistance, Please visit: www.ipexpert.com/chat
eFax: +1.810.454.0130
IPexpert is a premier provider of Classroom and Self-Study Cisco CCNA (R&S,
Voice & Security), CCNP, CCVP, CCSP and CCIE (R&S, Voice, Security & Service
Provider) Certification Training with locations throughout the United States,
Europe and Australia. Be sure to check out our online communities at
www.ipexpert.com/communities and our public website at www.ipexpert.com
New Email addresses available on Yahoo!
Get the Email name you've always wanted on the new @ymail and @rocketmail.
Hurry before someone else does!
http://mail.promotions.yahoo.com/newdomains/aa/_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
