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

S2720, S5700, and S6720 V200R013C00

This document describes the configurations of Device Management, including device status query, hardware management, Stack, SVF, cloud-based management, PoE, monitoring interface, OPS, energy-saving management, information center, fault management, NTP, synchronous ethernet, PTP.

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


Network Time Protocol (NTP) is an application layer protocol belonging to the Transmission Control Protocol/Internet Protocol (TCP/IP) suite. NTP synchronizes time between time servers and clients. NTP implementation is based on Internet Protocol (IP) and User Datagram Protocol (UDP). NTP transmission occurs through UDP port 123.


As network topologies become increasingly complex, clock synchronization becomes more important for all devices within a network. Manual configuration of system clocks by network administrators is both labor-intensive and error-prone, potentially affecting clock precision. NTP operates as a network protocol which synchronizes the clocks of devices within a network.

NTP is applied when all devices on a network require consistency between their clocks, such as in the following situations:
  • When in network management, routers require timestamps on analysis logs and debugging messages collected from different routers.
  • When an accounting system requires that all device clocks be consistent.
  • When multiple systems must reference the same clock when operating together to process complicated events.
  • When performing incremental backup, a backup server and clients require synchronization between clocks.
  • When certain applications require access to user login or file modification times.

Switch can function as both the NTP server and NTP client.

Version Evolution

NTP evolved from a simple time protocol using the ICMP Timestamp message. NTP has grown in complexity, now maintaining time synchronization with improved security and reliability. Table 12-1 lists the NTP versions and their updates.
Table 12-1  NTP version evolution
Version Date Standard Description
NTPv1 June 1988 RFC 1059 NTPv1 encompasses complete NTP rules and algorithms, but does not support authentication and control messages.
NTPv2 September 1989 RFC 1119 In addition to encompassing complete NTP rules and algorithms, NTPv2 supports authentication and control messages.
NTPv3 March 1992 RFC 1305 NTPv3 utilizes correctness rules while improving clock selection and filter algorithms. NPTv3 has been widely adopted, and only operates on an IPv4 network.
NTPv4 June 2010 RFC 5905 While similar to NTPv3, NTPv4 operates on both IPv4 and IPv6 networks. NTPv4 is backward compatible with NTPv3, and provides a complete encryption and authentication system, which is lacking in NTPv3.
Updated: 2019-04-20

Document ID: EDOC1100065674

Views: 75756

Downloads: 513

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next