As you know, the Network Time Protocol is responsible for keeping your devices synchronized across your network.
NTP provides millisecond-level accuracy, and for most enterprise networks, that is more than enough.But some industries cannot tolerate even a millisecond of clock difference.
When Milliseconds Are Too Slow
Some environments require microsecond or even nanosecond precision.
Here are three industries where NTP is simply not enough:
Figure 1 – PTP use cases across industries
In high-frequency trading, a few microseconds of clock drift can mean millions in lost revenue.
In 5G networks, base stations must be synchronized within nanoseconds to avoid radio interference.
In electric grids, substations must coordinate switching events within microseconds to prevent blackouts.
These environments all share the same need: sub-microsecond clock synchronization.
NTP cannot deliver that. This is where Precision Time Protocol (PTP) comes in.Answer the question below
What level of clock accuracy does NTP provide?
What is PTP?
PTP is defined in IEEE 1588.
The current version is PTPv2, which can run directly over Ethernet (Layer 2) or over UDP (Layer 3).
Unlike NTP, PTP achieves nanosecond-level accuracy over your existing Ethernet or IP network.
Figure 2 – NTP vs PTP accuracy comparison
On the NTP side, accuracy typically ranges from about 10 milliseconds over the Internet to around 1 millisecond on a local LAN.
On the PTP side, accuracy drops to around 100-200 nanoseconds with standard hardware.
With dedicated boundary clocks and hardware timestamping, that number goes down to 20-30 nanoseconds.That is a difference of several orders of magnitude.
But how does PTP actually work? To understand that, you first need to know how PTP organizes devices on your network.Answer the question below
What IEEE standard defines PTP?
PTP organizes devices into a hierarchy, just like NTP uses stratum levels.
But instead of numbers, PTP uses named clock roles.The Grandmaster Clock
At the very top sits the Grandmaster Clock.
It is the most accurate clock on the network, typically synchronized to a GPS receiver.
Figure 3 – Grandmaster Clock at the top of the hierarchy
The Grandmaster is not manually assigned.
It is elected by the Best Master Clock Algorithm (BMCA), which compares Priority1, Clock Class, Clock Accuracy, and Priority2.Run
show ptp clockon your Grandmaster:R1# show ptp clock PTP CLOCK INFO PTP Device Type: Grand Master clock PTP Device Profile: Power Profile Clock Identity: 0x18:8B:9D:FF:FE:65:3C:0 Clock Domain: 0 Number of PTP ports: 28 Time Transfer: linear Filter Priority1: 128 Priority2: 128 Clock Quality: Class: 248 Accuracy: unknown Offset (log variance): N/A Offset From Master(ns): 0 Mean Path Delay(ns): 0 Steps Removed: 0 Local clock time: 17:09:03 EDT Aug 25 2025The output confirms this device is the Grandmaster:
PTP Device Type: Grand Master clock confirms this device is the time source for the entire PTP domain.
Offset From Master(ns): 0 means there is no upstream master. This device IS the reference.
Priority1: 128 is the default value. To force a different Grandmaster, lower this value.
Answer the question below
What is the first criterion the BMCA uses to select the Grandmaster?
The Boundary Clock
One level below the Grandmaster, your switches act as Boundary Clocks.
A Boundary Clock terminates and regenerates PTP messages.
It processes the Sync from the Grandmaster, adjusts its own clock, then creates a brand new Sync for the devices below.
Figure 4 – Boundary Clocks join the hierarchy
Run
show ptp clockon your Boundary Clock switch to see the difference:SW1# show ptp clock PTP CLOCK INFO PTP Device Type: Boundary clock PTP Device Profile: Power Profile Clock Identity: 0x57:2C:B1:FF:FE:22:16:80 Clock Domain: 0 Number of PTP ports: 28 Time Transfer: linear Filter Priority1: 128 Priority2: 128 Clock Quality: Class: 248 Accuracy: unknown Offset (log variance): N/A Offset From Master(ns): 17 Mean Path Delay(ns): 12 Steps Removed: 1 Local clock time: 17:10:38 EDT Aug 25 2025Compare the differences with the Grandmaster:
PTP Device Type: Boundary clock means this switch terminates PTP on one side and regenerates it on the other.
Offset From Master(ns): 17 shows SW1 is 17 nanoseconds off from the Grandmaster.
Steps Removed: 1 confirms SW1 is one hop away from the Grandmaster.
An offset of 17 nanoseconds is far beyond what NTP could ever achieve.
Answer the question below
What field in show ptp clock tells you how far the clock is from the Grandmaster?
The Ordinary Clock (Slave)
At the bottom of the hierarchy, your servers and endpoints are Ordinary Clocks.
They just receive time and adjust their local clock.
Figure 5 – Complete PTP hierarchy
Now you know the three clock types.
But there is one more concept to understand: each connection between two PTP devices uses port roles to determine the direction of time distribution.Master and Slave Port Roles
Every PTP link has a Master port on one side and a Slave port on the other.
The Master port sends Sync messages.
The Slave port receives them.
Now look at the same hierarchy with Master and Slave port roles:

Figure 6 – PTP hierarchy with port roles
Each Master port (M) sends Sync messages down to the Slave port (S) below.
Verifying the PTP Domain
You can verify your PTP domain with two commands.

Figure 7 – PTP hierarchy with port roles
Run
show ptp briefto check the port roles on your switch:SW1# show ptp brief Interface Domain PTP State GigabitEthernet0/0 0 SLAVE GigabitEthernet0/1 0 MASTER GigabitEthernet0/2 0 MASTERSLAVE on G0/0 means this port receives time from the Grandmaster.
MASTER on G0/1 and G0/2 means these ports distribute time to downstream devices.
Now run
show ptp parentto verify which Grandmaster the entire domain is synced to:SW1# show ptp parent PTP PARENT PROPERTIES Parent Clock: Parent Clock Identity: 0x38:E:4D:FF:FE:81:FE:29 Parent Port Number: 196 Observed Parent Offset (log variance): 17258 Observed Parent Clock Phase Change Rate: N/A Grandmaster Clock: Grandmaster Clock Identity: 0x18:8B:9D:FF:FE:65:3C:0 Grandmaster Clock Quality: Class: 6 Accuracy: Within 1us Offset (log variance): 0 Priority1: 128 Priority2: 128Grandmaster Clock Identity matches R1's identity from the earlier output.
The entire PTP domain is synchronized to the same reference.Class: 6 means the Grandmaster is locked to a GPS reference.
Accuracy: Within 1us confirms the time source is within 1 microsecond of UTC.
Answer the question below
What command shows the Grandmaster clock identity and quality?
Your switches can operate in two different PTP modes.
Boundary Clock
So far, all the switches you have seen run as Boundary Clocks.
This is the default mode on Cisco Catalyst switches.
A Boundary Clock receives the Sync from the upstream master and synchronizes its own internal clock.
Then it generates a brand new Sync with its own timestamp and sends it downstream.
Figure 8 – Boundary Clock terminates and regenerates
From the perspective of downstream devices, the Boundary Clock is their time source.
They never see the original Grandmaster Sync.Configure SW1 in Boundary Clock mode:
SW1# configure terminal Enter configuration commands, one per line. End with CNTL/Z. SW1(config)# ptp mode boundary SW1(config)# endVerify the mode:
SW1# show ptp clock PTP CLOCK INFO PTP Device Type: Boundary clock PTP Device Profile: Power Profile Clock Identity: 0x57:2C:B1:FF:FE:22:16:80 Clock Domain: 0 Number of PTP ports: 28 Priority1: 128 Priority2: 128 Offset From Master(ns): 17 Mean Path Delay(ns): 12 Steps Removed: 1PTP Device Type: Boundary clock confirms your switch is actively terminating and regenerating PTP messages.
On Cisco switches, you can change the PTP mode with the
ptp modecommand:SW1(config)# ptp mode ? boundary Boundary Clock mode e2etransparent End-to-End Transparent Clock mode forward Forward packets without processing gmc-bc Grand Master Clock - Boundary Clock modeBoundary Clock is the default and most common mode.
Now let's look at the other mode you need to know: Transparent Clock.Answer the question below
What is the default PTP mode on Cisco Catalyst switches?
Transparent Clock (TC)
A Transparent Clock does not synchronize its own clock.
It does not appear in the PTP hierarchy either.
Instead, it simply forwards the Sync message from the Grandmaster.
It adds a correction field to account for the time the packet spent inside the switch.
Figure 9 – Transparent Clock forwards with correction
The downstream slave receives the original Sync from the Grandmaster, not a regenerated copy.
The correction field tells the slave exactly how much delay the switch introduced.
Transparent Clock is used when you want the Grandmaster to remain visible end-to-end.
No intermediate clock breaks the timing chain.Configure SW1 as a Transparent Clock:
SW1# configure terminal Enter configuration commands, one per line. End with CNTL/Z. SW1(config)# ptp mode e2etransparent SW1(config)# endVerify the change:
SW1# show ptp clock PTP CLOCK INFO PTP Device Type: Transparent clock PTP Device Profile: Power Profile Clock Identity: 0x57:2C:B1:FF:FE:22:16:80 Clock Domain: 0 Number of PTP ports: 28 Priority1: 128 Priority2: 128 Offset From Master(ns): 0 Mean Path Delay(ns): 0 Steps Removed: 0Notice the differences:
PTP Device Type: Transparent clock confirms the switch is no longer a Boundary Clock.
Offset From Master(ns): 0 and Steps Removed: 0 both fall to zero because the switch no longer synchronizes its own clock.
Answer the question below
Which PTP clock type is invisible to the hierarchy?
Answer the question below
With SW1 in e2etransparent mode, what Steps Removed does a server behind it show?
Now that you have seen the PTP hierarchy in action, here is how PTP compares to NTP.
Pull vs Push
With NTP, your device periodically polls the server and asks for the current time.
This is a pull model.

Figure 10 - NTP pulls time from the server
With PTP, the Grandmaster continuously pushes Sync messages to all downstream devices.
This is a push model.

Figure 11 - PTP pushes time from the Grandmaster
The push model combined with hardware timestamping is what gives PTP its nanosecond-level accuracy.
Comparison Table
Aspect
NTP
PTP
Standard
Accuracy
Milliseconds
Sub-microsecond (nanoseconds)
Model
Pull (client polls server)
Push (Grandmaster sends Sync)
Transport
UDP 123 (Layer 3 only)
Layer 2 or Layer 3 (UDP 319/320)
Hierarchy
Stratum (0–16)
Grandmaster → Boundary → Slave
Clock selection
Lowest stratum preferred
Best Master Clock Algorithm (BMCA)
Timestamping
Software
Hardware (on supported switches)
Table 1 – NTP vs PTP comparison
For standard enterprise networks, NTP is the right choice.
For environments where microsecond accuracy is critical, PTP is the answer.
In practice, many networks run both.
NTP handles the general infrastructure, while PTP serves the devices that need extreme precision.Answer the question below
In PTP, what model does the Grandmaster use to distribute time?