You already met NTP in your CCNA studies.
This lesson refreshes the essentials in one pass, so the next ones can go further.What NTP Does
Without NTP, every device keeps its own time and they drift apart:

Figure 1 – Without NTP, clocks drift apart
With NTP, all devices point to one NTP server, allowing them to converge on the same time.

Figure 2 – With NTP, devices share one time
NTP is a standardized protocol in RFC 5905, and NTPv4 is the current version.
Answer the question below
What is the current version of NTP?
NTP Stratums
NTP establishes a hierarchy of clock sources.
It uses the term stratum to measure distance from the reference.
Stratum 0 is the reference clock itself, a GPS or atomic source.
Figure 3 – The NTP stratum hierarchy
The server directly connected to it is a Stratum 1 server.
Each step down the chain adds one.The usable values range from 1 to 15.
Stratum 16 means that the device is unsynchronized and has no valid source yet.
NTP uses UDP port 123.
Answer the question below
What stratum is a server directly connected to the reference clock?
Let's configure a simple NTP topology now.
Look at the topology below:
Figure 6 – R2 syncs to the server, R3 syncs to R2
The NTP server is synchronized to a GPS reference, so it sits at stratum 1
R2 becomes stratum 2
R3 becomes stratum 3
Configure the NTP server
You can configure R2 to point to the NTP server:
R2# configure terminal Enter configuration commands, one per line. End with CNTL/Z. R2(config)# ntp server 209.165.200.225 R2(config)# endR2 now uses the stratum 1 server at 209.165.200.225 as an NTP source
Extend the Chain to R3
R2 now has the time, so it can serve it in turn.
On R3 we can tell the router to synchronize to R2:R3# configure terminal Enter configuration commands, one per line. End with CNTL/Z. R3(config)# ntp server 192.168.1.1 R3(config)# endThe server feeds R2, and R2 feeds R3: the chain is complete.
Answer the question below
R3 syncs to R2, which is stratum 2. What stratum does R3 become?
Now, verify that the devices are synchronized.
Before Synchronization
You just pointed R2 at the server.
Does it lock onto the time straight away?
Runshow ntp statusright now and read the first line.R2# show ntp status Clock is unsynchronized, stratum 16, no reference clock nominal freq is 250.0000 Hz, actual freq is 249.9990 Hz, precision is 2**24 reference time is 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1990) clock offset is 0.00 msec, root delay is 0.00 msec root dispersion is 0.00 msec, peer dispersion is 0.00 msec system poll interval is 64, never updated.The clock is not synchronized
Stratum 16 message
This tells you R2 isn't synchronized yet.
NTP needs a moment, so this is normal right after you configure it.Answer the question below
What stratum does an unsynchronized device report?
After Synchronization
We can try the command again after leaving some time:
R2# show ntp status Clock is synchronized, stratum 2, reference is 209.165.200.225 nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**10 ntp uptime is 1893700 (1/100 of seconds), resolution is 4000 reference time is E0E2D211.E353FA40 (22:50:58.888 UTC Thu Aug 14 2026) clock offset is 0.5120 msec, root delay is 9.45 msec root dispersion is 8.21 msec, peer dispersion is 3.40 msec loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.000000000 s/s system poll interval is 64, last update was 9 sec ago.Clock is synchronized,
Stratum 2,
Reference is 209.165.200.225
This tells you R2 is now synchronized and the reference is the IP address of the stratum 1 server.
Answer the question below
In show ntp status, which field shows the gap between the local clock and its source?
Reading show ntp associations
Check the NTP associations to see every server your device talks to:
R2# show ntp associations address ref clock st when poll reach delay offset disp *~209.165.200.225 .GPS. 1 38 1024 377 1.914 0.613 1.05 * sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configuredHere we can see one line:
*means that R2 chose this server.~means that you configured it manually.Its stratum is
1..GPS.is what the server itself syncs to.
R2 has successfully selected the stratum 1 server as its time source.
Confirm the Time Source
The two previous commands describe the NTP association itself.
This last one reads the local clock, to confirm the source has changed:R2# show clock detail 22:51:7.176 UTC Thu Aug 14 2026 Time source is NTPThe time is now synchronized with the NTP server.
Your router no longer relies on a clock that was set by hand.Answer the question below
What is the time source on R2 after NTP synchronization?
Now check whether R3 synced correctly to R2.

Figure 7 – R3 syncs to R2
Check the R3 NTP synchronization
Start by checking the NTP status on R3:
R3# show ntp status Clock is synchronized, stratum 3, reference is 192.168.1.1 nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**10 ntp uptime is 1893700 (1/100 of seconds), resolution is 4000 reference time is E0E2D280.A1B2C340 (22:52:0.631 UTC Thu Aug 14 2026) clock offset is 0.4810 msec, root delay is 9.45 msec root dispersion is 12.33 msec, peer dispersion is 3.40 msec loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.000000000 s/s system poll interval is 64, last update was 14 sec ago.R3 is synchronized, confirming that it successfully received time from R2.
It is at stratum 3, one step below R2 (stratum 2).
The reference is 192.168.1.1, which is R2's IP address.
The same three commands work the same way on R3, so there is no need to run them all again.
The full chain is working: the stratum 1 server feeds R2, and R2 feeds R3.Answer the question below
In show ntp status, which field names the server the device follows?
Reading the reach Counter
One column of show ntp associations deserves its own explanation.
Thereachcolumn tracks the last eight polls your device sent to that server.Every poll that gets an answer turns on one bit. Every poll that is lost turns one off.
The router prints the result as an octal number, which is why the values look unusual.You only need to read the two ends of the range:
377means all eight bits are on, so the last eight polls were all answered.0means no recent poll was answered at all.
Anything in between tells you the server is reachable but losing packets.
A fresh association climbs toward 377 over several minutes, so a low value right after you configure a server is normal.Answer the question below
What reach value means the last eight polls were all answered?
Answer the question below
Reach shows 1, 3, 7 as polls get answered: what does it show after the fourth answered poll?
Your chain is built and verified.
The next lessons go further: how stratum really counts, how two routers back each other up, how your router picks between sources, and how it checks that a source is genuine.