NTPv4 is an extension of NTPv3 that supports IPv4 and IPv6. It is backward compatible with NTPv3, offers some new features, and time synchronization is faster and more precise.
Security has improved, NTPv4 supports public key cryptography and standard X509 certificates.
When using NTP for IPv4, broadcast is a popular option as it allows you to send NTP packets in the broadcast domain to everyone. We can’t do this with IPv6, but NTPv4 does support site-local multicast.
DNS support is also improved. With NTPv3, if you configure a hostname to sync with, your device does a lookup for the hostname and stores the IP address in the configuration, the hostname is then lost. With NTPv4, the hostname is stored in the configuration.
In this lesson, I’ll show you how to configure NTPv4 with a unicast and multicast client.
This is the topology we’ll use:
Configuration-wise, NTPv4 is pretty much the same thing.
To help speed things up, let’s set the same time and date on all routers before we configure NTP:
R1, R2 & R3 #clock set 10:37:00 2 July 2018
I will configure R1 as an NTP master so that I don’t need an external server:
R1(config)#ntp master 1
Let’s configure our clients. R2 will be an NTP unicast client and for R3 we will use multicast.
We can configure the IPv6 address of R1 but instead, we’ll use a hostname to test if R2 stores the hostname in its configuration. I’ll create a manual host record for this:
R2(config)#ipv6 host R1 2001:DB8:0:12::1
Now we configure R1 as the NTP server. The
version 4 parameter sets the correct version:
R2(config)#ntp server R1 version 4
To make multicast work, we need to configure R1 to send NTP multicast packet and R3 to receive them.
This is the multicast address we will use:
- FF05 is the multicast address for the site-local scope.
- ::101 is the address that IANA has assigned to NTP for IPv6.
Let’s configure R1 to send NTP multicast packets with this address: