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

Reminder

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

upgrade

Common Operation Guide

CloudEngine 12800, 12800E, 8800, 7800, 6800, and 5800 Series Switches

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).
Common NTP Operations

Common NTP Operations

To perform time synchronization, a switch may utilize multiple NTP operating modes. The following modes are supported.

NTP Mode

Usage Scenario

Deployment Location and Synchronization Direction

Unicast client/server

Within a synchronous subnet, unicast server/client mode runs on a higher stratum. Devices are required to obtain the server IP address in advance.

NTP is configured on only the clients. On the server, you only need to configure the NTP master clock.

Clients can be synchronized to the server but the server will not be synchronized to clients.

Peer

The peer mode operates on a lower stratum within a synchronous subnet. An active peer and a passive peer can synchronize with each other.

NTP is configured only on the symmetric active peer, but not on the symmetric passive peer.

The peer with the higher stratum synchronizes with the peer with a lower stratum.

Broadcast

This mode is applicable when the IP address of a server or a symmetric peer is not determined, or when the clocks of a large number of devices need to be synchronized on a network.

NTP needs to be configured on both the server and client.

Clients can be synchronized to the server but the server will not be synchronized to clients.

Multicast

This mode is used when a significant number of clients are distributed throughout a network that does not require high precision. For example, one or multiple time servers periodically send multicast packets to clients, and the clients synchronize their time based on the multicast packets.

NTP needs to be configured on both the server and client.

Clients can be synchronized to the server but the server will not be synchronized to clients.

Manycast

This mode is applied when servers are scattered throughout a network. Clients are able to discover and then synchronize with the closest manycast server. Manycast is especially useful when the server frequently changes, which will cause reconfigurations of all clients within the network.

NTP needs to be configured on both the server and client.

Clients can be synchronized to the server but the server will not be synchronized to clients.

NOTE:

If a source address from which NTP packets are sent is specified on the server, the address must be the same as the server IP address configured on the client. Otherwise, the client cannot process the NTP packets sent by the server, resulting in a clock synchronization failure.

Translation
Download
Updated: 2018-10-08

Document ID: EDOC1000102369

Views: 196020

Downloads: 3214

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next