service · 7 min read

Replacing your time server: migrating to a modern NTP/PTP solution

Outdated or discontinued time server? Here is how to migrate without interruption to a modern NTP/PTP solution, keeping your IRIG/PTP outputs and traceability.

Choose your reading level

Is your time server reaching end of life, or no longer supported? Then it is time to migrate, preferably before it fails. A time server is the foundation under your network, your measurements or your compliance: if it stops or drifts, you notice it at the worst possible moments.

Migrating does not have to be disruptive. In many cases:

the new server takes over the same role (NTP, PTP, IRIG output) without your clients noticing;
you can run the old and new server in parallel for a while;
you keep your antenna and cabling where possible.

We help you plan the switch so that no time is lost. Ask for migration advice.

An outdated or discontinued time server is a risk that grows over time. This guide describes how to switch to a modern NTP/PTP solution without interruption.

When to replace?

End-of-life / end-of-support: no more firmware updates, no spare parts, a growing security risk.
Drifting time: an old oscillator that no longer stays within tolerance.
New requirements: you need PTP where NTP used to suffice, or a compliance standard (MiFID II, IEC 61850) your old device cannot meet. See the compliance guide.

What stays, what changes

In most migrations:

Your clients notice nothing: the new server offers the same protocols (NTP, PTP, IRIG-B, time code) on the same addresses.
Antenna and cabling often remain usable: an existing GNSS antenna and coax can usually be reused.
The time source improves: a modern disciplined oscillator (OCXO/Rubidium) gives better holdover and traceability.

The migration in steps

1. Inventory: which protocols and outputs does your current server provide (NTP, PTP, IRIG-B, 1 PPS)? 2. Choose the successor: follow the NTP/PTP time server decision guide and the family comparison. 3. Run in parallel: let the new server run alongside the old one and verify the time. 4. Switch over: move the clients, remove the old server. 5. Document: record the new chain (source, stratum, uncertainty) for your reliability and audit.

We plan with you

Daylight bv guides the switch: from inventory to parallel test and cutover, with support in Dutch and English. Discuss your migration.

A time-server migration is a chain replacement, not a box replacement. The goal: the new source delivers the same or better accuracy, traceability and outputs, with a cutover without a time jump.

Mapping compatibility

Document the existing chain: protocols (NTP, PTP profile, IRIG-B format, 1 PPS), physical outputs, IP configuration and the antenna installation. A modern grandmaster can usually provide all existing outputs, so downstream equipment remains untouched.

Parallel operation and verification

Let the new server discipline in parallel on the same GNSS source and compare the offset to the old server before switching over. This detects cable, config or asymmetry problems before the cutover. The switchover itself must not introduce a phase step at the clients.

Keeping or improving traceability

Use the migration to document traceability (source, stratum, disciplining method, uncertainty). Where the old chain lacked demonstrable traceability, this is the moment to put it right. See reliable time and stratum levels.

Legacy outputs

Keep IRIG-B alongside NTP/PTP where needed; much legacy equipment expects that time code. See IRIG-B time code. Choose a grandmaster that provides the full output set so you do not have to migrate device by device.

Sources: IEEE 1588-2019; IRIG Standard 200; NIST Time & Frequency Division.