No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Configuration Guide - Device Management

CloudEngine 12800 and 12800E V200R003C00

This document describes the configurations of Device Management, including device status query, hardware management, Information Center Configuration, NTP, Synchronous Ethernet Configuration, Fault Management Configuration, Energy-Saving Management Configuration, Performance Management Configuration, Maintenance Assistant Configuration, and OPS Configuration.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Overview of NTP

Overview of NTP


The Network Time Protocol (NTP) is an application layer protocol in the TCP/IP protocol suite. NTP is used to synchronize the time among a set of distributed time servers and clients. NTP is implemented based on the Internet Protocol (IP) and User Datagram Protocol (UDP). NTP packets are transmitted using UDP port 123.


As network topologies become increasingly complex, clock synchronization becomes more important for devices on the entire network. If a system clock is modified manually by network administrators, the workload is heavy and the modification is error-prone, which affects clock precision. NTP is formulated as a networking protocol for clock synchronization between devices on a network.

The following are some of the situations in which NTP applies:
  • In network management, logs or debugging messages collected from different routers are referred to according to the time that they occurred.
  • An accounting system requires that the clocks of all the devices be consistent.
  • When several systems work together to process a complicated event, they have to refer to the same clock to ensure a correct execution order.
  • Incremental backup between a backup server and clients requires that their clocks be synchronized.
  • Some applications need to obtain the time in which a user logs in a system and a document is modified.

Version Evolution

NTP is evolved from the Time Protocol and the ICMP Timestamp message but is specifically designed to maintain accuracy and robustness. Table 4-1 shows the NTP version evolution.
Table 4-1 NTP version evolution
Version Date Protocol Number Description
NTPv1 June 1988 RFC 1059 NTPv1 puts forward complete NTP rules and algorithms for the first time, but it does not support authentication and control messages.
NTPv2 September 1989 RFC 1119 NTPv2 supports authentication and control messages.
NTPv3 March 1992 RFC 1305 NTPv3 uses correctness principles and improves clock selection and filter algorithms, and it is widely used.
NTPv4 June 2010 RFC 5905 NTPv4 is compatible with NTPv3, but modifies the NTP header so that NTPv4 can support IPv6 address family.
Updated: 2019-05-05

Document ID: EDOC1100004193

Views: 70569

Downloads: 26

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next