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

Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs on the product.
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).
NTP/2/NTP_SYNCHRONIZE_STATUS

NTP/2/NTP_SYNCHRONIZE_STATUS

Message

NTP/2/NTP_SYNCHRONIZE_STATUS: NTP state changed from synchronized to unsynchronized. (SynchronizationSourceAddress = [Source] , VpnInstance = [VpnName], Reason = [Reason])

Description

This log records the NTP synchronization status.

Parameters

Parameter Name Parameter Meaning

SynchronizationSourceAddress

Indicates the server IP address used to synchronize local NTP clock.

VpnInstance

Indicates the VPN instance for local NTP clock synchronization.

Reason

Indicates the reason why NTP clock status changes to unsynchronized.

Possible Causes

NTP state changed from synchronized to unsynchronized state due to one of the following reason:

  • Reason 1: VPN change detected.
  • Reason 2: Peer reachability lost.
  • Reason 3: Authentication failure.
  • Reason 4: Authentication configuration changed.
  • Reason 5: Source interface unavailable.
  • Reason 6: KOD DENY received.
  • Reason 7: Manycast discovery restarted.
  • Reason 8: Unicast server configuration removed.
  • Reason 9: Unicast peer configuration removed.
  • Reason 10: Reference clock configuration removed.
  • Reason 11: Stratum increase detected.
  • Reason 12: Peer clock unsynchronized/unselectable.
  • Reason 13: Manycast configuration removed.
  • Reason 14: Configuration changed.
  • Reason 15: Clock selection failed - Excessive falsetickers.
  • Reason 16: Clock selection failed - No selectable clock.
  • Reason 17: Clock change detected.
  • Reason 18: Interface configuration changed.
  • Reason 19: IPv6 disabled on the interface.
  • Reason 20: Unknown.

Procedure

  • Reason 1: VPN change detected

    Select another VPN.

  • Reason 2: Peer reachability lost

    1. Check the status of the remote network for clock synchronization.
    2. If the remote network status cannot be obtained, configure the standby clock source.

  • Reason 3: Authentication failure

    1. Check whether a key is configured.
    2. If no key is configured, configure a key.
    3. If a key has been configured, check whether the key is correct.

  • Reason 4: Authentication configuration changed

    See the handling method of reason 3.

  • Reason 5: Source interface unavailable

    Add the source interface again and reconfigure NTP.

  • Reason 6: KOD DENY received

    Delete the NTP configuration and configure the standby clock source.

  • Reason 7: Manycast discovery restarted

    Reset the manycast timeout.

  • Reason 8: Unicast server configuration removed

    Reconfigure the NTP unicast server.

  • Reason 9: Unicast peer configuration removed

    Reconfigure the remote NTP unicast server.

  • Reason 10: Reference clock configuration removed

    Reconfigure the local NTP clock as the NTP master clock.

  • Reason 11: Stratum increase detected

    Configure an NTP clock source with higher precision.

  • Reason 12: Peer clock unsynchronized/unselectable

    Reconfigure the remote NTP clock source.

  • Reason 13: Manycast configuration removed

    Configure NTP in manycast mode.

  • Reason 14: Configuration changed

    Reconfigure the reference clock source.

  • Reason 15: Clock selection failed - Excessive falsetickers

    Configure an effective clock source.

  • Reason 16: Clock selection failed - No selectable clock

    Configure an effective clock source.

  • Reason 17: Clock change detected

    Reconfigure the remote clock source.

  • Reason 18: Interface configuration changed

    Modify the NTP configuration.

  • Reason 19: IPv6 disabled on the interface

    Enable IPv6 on the interface.

  • Reason 20: Unknown

    Modify the NTP configuration.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 114753

Downloads: 85

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