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 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of IP multicast, including IP multicast basics, IGMP, MLD, PIM (IPv4), PIM (IPv6), MSDP, multicast VPN, multicast route management (IPv4), multicast route management (IPv6), IGMP snooping, MLD snooping, static multicast MAC address, multicast VLAN, multicast network management.

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).
Configuring the NTP Primary Clock

Configuring the NTP Primary Clock


A device on the network can synchronize its clock in the following manners.
  • Synchronizing with the local clock: The local clock is used as the reference clock.
  • Synchronizing with another device on the network: This device is used as an NTP clock server to provide a reference clock for the local clock.

If both manners are configured, the device selects an optimal clock source by comparing the clocks determined in the two manners. The clock of a lower stratum is preferred.

An authoritative clock is used as a reference time source for a synchronization subnet, and is located at the top of a hierarchical structure on the synchronization subnet. The authoritative clock is stratum0. The current authoritative clock is mostly a Radio Clock or the Global Positioning System (GPS). The time of the authoritative clock is synchronized through the broadcast UTC time, not through NTP.

In practice, the NTP server synchronized with the authoritative clock is set as stratum1, and is used as a master reference clock source. Other devices on the network synchronize their clocks with the clock of the NTP server, which means the local clock of the NTP server is configured as the NTP primary clock. The NTP distance from a device on the network to the master reference clock source, that is, the number of NTP servers on the NTP synchronization chain, determines the stratum of the clock on the device.

As shown in Figure 4-10, SwitchA is the primary clock, and the clock stratum is 1. The clock synchronization direction is from SwitchA to SwitchB, and then to SwitchC. Only after the SwitchB is synchronized with SwitchA, SwitchC can synchronize its clock with the clock of SwitchB. After all the devices on the synchronization subnet are synchronized, SwitchB and SwitchC are stratum2 and stratum3, respectively.
Figure 4-10 NTP synchronization subnet

After the local clock is configured as the reference clock, the local device can be used as the clock source to synchronize other devices on the network. Confirm before this configuration, so as avoid clock errors on the network. It is recommended that a high-precision clock source (such as the GPS clock source) be used if the user network requires high clock precision.


  1. Run system-view

    The system view is displayed.

  2. Run ntp refclock-master [ ip-address ] [ stratum ]

    The local clock is configured as the NTP primary clock.

    By default, no NTP primary clock is specified.

  3. Run commit

    The configuration is committed.

Updated: 2020-01-07

Document ID: EDOC1100075362

Views: 34065

Downloads: 119

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next