System Setup and Software Installation Guide for Cisco NCS 1014, IOS XR Releases 26.x.x

PDF

System Setup and Software Installation Guide for Cisco NCS 1014, IOS XR Releases 26.x.x

NTP servers

Want to summarize with AI?

Log in

Explains how Network Time Protocol (NTP) servers synchronize device clocks across a network to ensure accurate and consistent timekeeping.


A Network Time Protocol (NTP) server is a network device that

  • provides a common, authoritative time source for other devices,

  • synchronizes network clocks using the User Datagram Protocol (UDP) and Coordinated Universal Time (UTC), and

  • distributes accurate time across the network to maintain consistency and support management, security, and troubleshooting operations.

Importance of time synchronization: In modern and large networks, time synchronization is critical because every aspect of managing, securing, planning, and debugging a network depends on accurate timestamps for the occurrence of events.
Table 1. Feature History

Feature Name

Release Information

Feature Description

NTP Support

Cisco IOS XR Release 7.11.1

Network Time Protocol (NTP) allows devices to synchronize clocks with the NTP servers, maintaining the most accurate time. NCS 1010 now supports time synchronization. In modern and large networks, time synchronization is critical because every aspect of managing, securing, planning, and debugging a network depends on the time of occurrence of events.

Commands added:

  • ntp server

  • show ntp associations

  • show ntp status

NTP key features and operation

NTP uses the User Datagram Protocol (UDP) as its transport protocol.

  • NTP communication is always based on Coordinated Universal Time (UTC).

  • NTP networks usually receive their time from an authoritative source, such as a radio clock or atomic clock attached directly to a time server. NTP distributes this time across the network.

  • The "stratum" concept describes the number of NTP hops a machine is from an authoritative time source:

    • A stratum 1 server is directly connected to an authoritative source (for example, a radio or atomic clock, or a GPS time source).

    • A stratum 2 server receives its time from a stratum 1 server via NTP, and so forth.

  • Machines running NTP, called "associations," are usually statically configured with the IP addresses of machines with which they should form associations. Accurate timekeeping is achieved by exchanging NTP messages between each pair of associated machines.

  • An NTP broadcast client listens for broadcast messages sent by an NTP broadcast server at a designated IPv4 address. The client synchronizes the local clock using the first received broadcast message.


Synchronize the clock with an NTP server

Synchronize the IOS XR system clock with an NTP server to prevent time deviation and maintain precise system operation.

IOS XR features an independent system clock, which must be periodically synchronized with an NTP server to avoid drifting from true time. Accurate system time is essential for proper logging, scheduling, and network functionality.

Procedure

1.

Enter configuration mode.

Example:

RP/0/RP0/CPU0:ios# configure
2.

Configure the NTP server using the command ntp server ntp-server-ip-address version version-number prefer iburst .

Example:

IPv4:

RP/0/RP0/CPU0:ios(config)#ntp server 10.127.60.137 version 4 prefer iburst

IPv6:

RP/0/RP0/CPU0:ios(config)#ntp server 2001:DB8::1 version 4 prefer iburst
Note

The NTP server can also be reached through a VRF if the management interface is in a VRF.

3.

Commit the configuration.

Example:

RP/0/RP0/CPU0:ios(config-ntp)#commit
4.

Verify NTP associations using the command show ntp associations

Example:

RP/0/RP0/CPU0:ios#show ntp associations
Tue Oct 17 06:32:54.389 UTC

      address         ref clock     st  when  poll reach  delay  offset    disp
 ~10.0.0.1       10.64.58.50       2    15    64    1    1.95  -0.062  1937.7
 ~10.127.60.137    .STEP.           16     -    64    0    0.00   0.000   15937
 * sys_peer, # selected, + candidate, - outlayer, x falseticker, ~ configured
5.

Verify that the clock is synchronized using the command show ntp status .

Example:

RP/0/RP0/CPU0:ios#show ntp status
Tue Oct 17 06:33:41.125 UTC
Clock is synchronized, stratum 3, reference is 10.0.0.1
nominal freq is 1000000000.0000 Hz, actual freq is 31762818.6272 Hz, precision is 2**24
reference time is E8D8A944.A4F2AEF1 (06:33:40.644 UTC Tue Oct 17 2023)
clock offset is -0.592 msec, root delay is 2.434 msec
root dispersion is 939.64 msec, peer dispersion is 938.03 msec
loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.0000304834 s/s
system poll interval is 64, last update was 1 sec ago
authenticate is disabled, panic handling is disabled,
hostname resolution retry interval is 1440 minutes.

The IOS XR system clock on Cisco NCS 1014 is synchronized with the NTP server, ensuring accurate system time.


Verify external reference clock status

Confirm that the Cisco NCS 1014 system clock is synchronized with an external NTP server and check the status of all relevant NTP associations.

Use this task to ensure accurate system time and network synchronization for the Cisco NCS 1014, which relies on an external reference clock via NTP. The commands described can be entered in any order.

Procedure

1.

Run the command show ntp associations [detail] [location node-id] to view NTP associations.

Example:

RP/0/RP0/CPU0:ios#show ntp associations
Sun Nov 5 15:14:44.128 UTC

address ref clock st when poll reach delay offset disp
*~10.0.0.1 10.64.58.50 2 81 128 377 1.84 7.802 2.129
* sys_peer, # selected, + candidate, - outlayer, x falseticker, ~ configured

Displays the status of NTP associations.

Example:

RP/0/RP0/CPU0:ios#show ntp associations detail
Sun Nov 5 15:14:48.763 UTC

10.0.0.1 configured, our_master, stratum 2
ref ID 10.64.58.50, time E8F22BB9.79D4A841 (14:56:57.475 UTC Sun Nov 5 2023)
our mode client, peer mode server, our poll intvl 128, peer poll intvl 128
root delay 0.6866 msec, root disp 1.04, reach 377, sync dist 6.2590
delay 1.84 msec, offset 7.802 msec, dispersion 2.129
precision 2**23, version 4
org time E8F22F92.B647E8FC (15:13:22.712 UTC Sun Nov 5 2023)
rcv time E8F22F92.B88F303C (15:13:22.720 UTC Sun Nov 5 2023)
xmt time E8F22F92.B88F303C (15:13:22.720 UTC Sun Nov 5 2023)
filtdelay = 1.844 1.772 1.983 1.954 1.945 2.000 1.902 1.778
filtoffset = 7.857 7.802 8.065 8.063 8.332 8.397 8.664 8.684
filterror = 0.000 0.060 1.995 2.055 4.050 4.110 6.060 6.120

Example:

RP/0/RP0/CPU0:ios#show ntp associations detail location 0/RP0/CPU0
Sun Nov 5 15:38:15.744 UTC

10.0.0.1 configured, our_master, stratum 2
ref ID 10.64.58.50, time E8F233C0.5606A159 (15:31:12.336 UTC Sun Nov 5 2023)
our mode client, peer mode server, our poll intvl 128, peer poll intvl 128
root delay 0.7019 msec, root disp 0.47, reach 377, sync dist 5.6762
delay 2.01 msec, offset 7.226 msec, dispersion 3.856
precision 2**23, version 4
org time E8F23563.DE5D42D5 (15:38:11.868 UTC Sun Nov 5 2023)
rcv time E8F23563.E07C296D (15:38:11.876 UTC Sun Nov 5 2023)
xmt time E8F23563.E07C296D (15:38:11.876 UTC Sun Nov 5 2023)
filtdelay = 2.006 1.865 1.936 1.762 1.932 1.875 1.881 2.011
filtoffset = 7.210 7.305 7.372 7.226 7.298 7.258 7.251 7.224
filterror = 0.000 2.025 2.085 4.035 4.095 6.060 6.120 8.070
2.

Run the command show ntp status [location node-id] to verify the system clock’s synchronization status.

Example:

RP/0/RP0/CPU0:ios#show ntp status
Sun Nov 5 15:14:36.949 UTC

Clock is synchronized, stratum 3, reference is 10.0.0.1
nominal freq is 1000000000.0000 Hz, actual freq is 44881851.3383 Hz, precision is 2**24
reference time is E8F22D7A.AB020D97 (15:04:26.668 UTC Sun Nov 5 2023)
clock offset is 9.690 msec, root delay is 2.553 msec
root dispersion is 24.15 msec, peer dispersion is 2.13 msec
loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.0000212807 s/s
system poll interval is 128, last update was 610 sec ago
authenticate is disabled, panic handling is disabled,
hostname resolution retry interval is 1440 minutes.

Verifies that the clock is synchronized with the NTP server.


NTP troubleshooting information