You're very welcome. Even though the clock did synchronize, you're correct that there was still an "Unsynchronized" message. That happens if the Root Dispersion value is greater than 1000ms, which it was because I was using Cisco VIRL rather than physical gear.
very wonderful Mr.Kevin but there is somthing pops on my mind i wanna cisco l2 switch in the access layer to obtain clock from l3 switch from distribution layer i find it a bit difficult for me because i configured multple vlans plus i did some pruning and the reason why i want time sync is i have configured a syslog server and iwant these msgs to be generated with time and date on the server from each network device within my network . i feel lost at that point and i dont know what to do
@@kwallaceccie You know actually i am asking because i saw in Cisco books they recommended to configure clock timezone and summer-time before configure clock set, and they didn't mention the reason but they just said that it's better, so i thought that could be the reason behind "unsynchronized Status", what do you say?.
@@kwallaceccie This is a quote from Cisco's book "NTP’s job is to synchronize clocks, but NTP works best if you set the device clock to a reasonably close time before enabling the NTP client function with the ntp server command. For instance, my wristwatch says 8:52 p.m. right now. Before starting NTP on a new router or switch so that it synchronizes with another device, I should set the time to 8:52 p.m., set the correct date and timezone, and even tell the device to adjust for daylight savings time-and then enable NTP. Setting the time correctly gives NTP a good start toward synchronizing."
the best video ever, short, clear, concise :), thank you sir
Thanks for the video, easier to understand from your delivery
Best explanation video of NTP I have seen
Excellent explanation. I so much appreciate your lessons. Thank you so much sir.
This was awsome, thanks Kevin.
Simple and clear explanation, thanks, Kevin.
Thanks bud. Why was your clock still Unsynchronized though?
You're very welcome. Even though the clock did synchronize, you're correct that there was still an "Unsynchronized" message. That happens if the Root Dispersion value is greater than 1000ms, which it was because I was using Cisco VIRL rather than physical gear.
By the way, root dispersion is the maximum clock time difference that was ever observed between the local clock and the root clock (stratum 1 clocks).
Excellent. Thank you very much, Kevin.
Absolutely superb! Thanks Kevin
As always, very good explanation Kevin, Thanks.
very wonderful Mr.Kevin but there is somthing pops on my mind i wanna cisco l2 switch in the access layer to obtain clock from l3 switch from distribution layer i find it a bit difficult for me because i configured multple vlans plus i did some pruning and the reason why i want time sync is i have configured a syslog server and iwant these msgs to be generated with time and date on the server from each network device within my network . i feel lost at that point and i dont know what to do
You are the best.. Thank you very much for this amazing channel
Another refresher thank yuo
Great as usual, we want more specially for CCNP Encore (350-401) Please
Very interesting! Thank you!
You set the server as stratum 3, why then does the reference clock on the client show that incremeneted to stratum 4?
that was a great video!
Thank you
Also upload a video on SNMP, MIB all in details...please
looks good
why it says "clock is unsynchronized"
It's because the Root Dispersion Time is too high, as a result of doing the demo in CML rather than on physical gear.
@@kwallaceccie
You know actually i am asking because i saw in Cisco books they recommended to configure clock timezone and summer-time before configure clock set, and they didn't mention the reason but they just said that it's better, so i thought that could be the reason behind "unsynchronized Status", what do you say?.
Interesting, I haven’t experimented with the order of those configuration commands.
@@kwallaceccie
This is a quote from Cisco's book
"NTP’s job is to synchronize clocks, but NTP works best if you set the device clock to a reasonably close time before enabling the NTP client function with the ntp server command. For instance, my wristwatch says 8:52 p.m. right now. Before starting NTP on a new router or switch so that it synchronizes with another device, I should set the time to 8:52 p.m., set the correct date and timezone, and even tell the device to adjust for daylight savings time-and then enable NTP. Setting the time correctly gives NTP a good start toward synchronizing."
my raspberry pi with gps is a stratum 1 time source with pps support easy to make and cheap
first time here
ntp authentication is disabled by default. you enable it with ntp authenticate
123? Omg I get it now
This video was absolutely no help. I am completey loss especially around the "summer time" part. Very unclear.
isp's block this port now. Thanks a lot DDOS hackers.