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

Alarm Handling

CloudEngine 8800, 7800, 6800, and 5800 V200R002C50

This document provides the explanations, causes, and recommended actions of alarms 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_1.3.6.1.4.1.2011.6.80.2.1 hwNtpStateChangeTrap

NTP_1.3.6.1.4.1.2011.6.80.2.1 hwNtpStateChangeTrap

Description

NTP synchronization state changed. (hwNtpState=[state], hwNtpSource=[source], hwNtpSourceVpnName=[VpnName])

The NTP clock synchronization status was changed.

Attribute

Attribute

Description

Alarm or Event

Event

Trap Severity

Critical

Mnemonic Code

hwNtpStateChangeTrap

Trap OID

1.3.6.1.4.1.2011.6.80.2.1

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the matching trap.

Parameters

Parameter Description

hwNtpState

NTP clock synchronization status

hwNtpSource

IP address of the clock synchronization source

hwNtpSourceVpnName

Name of the VPN where the clock synchronization source resides

VB Parameters

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.6.80.1.1

hwNtpState

None

1.3.6.1.4.1.2011.6.80.1.2

hwNtpSource

None

1.3.6.1.4.1.2011.6.80.1.3

hwNtpSourceVpnName

None

Impact on the System

The NTP status is unsynchronized.

Possible Causes

The possible causes of the NTP status change from synchronized to unsynchronized are as follows:
  • Cause 1: The system clock on the local end is configured.
  • Cause 2: The peer is deleted.
  • Cause 3: The peer is unreachable.
  • Cause 4: The peer fails authentication.
  • Cause 5: The peer clock is not synchronized.
  • Cause 6: The update interval for the peer clock exceeded the threshold.
  • Cause 7: The NTP clock stratum on the peer is higher than that on the local end.
  • Cause 8: The clock synchronization source is lost.
  • Cause 9: The NTP mode on the local end does not match that on the peer.

Procedure

  • Cause 1: The system clock on the local end is configured.
    1. Configure a new clock source. Then, check whether NTP enters the synchronized state.

      • If so, go to step 3.
      • If not, go to step 2.

    2. Collect alarm information and configuration information, and then contact technical support personnel.
    3. End.
  • Cause 2: The peer is deleted.
    1. Configure a new clock source. Then, check whether NTP enters the synchronized state.

      • If so, go to step 3.
      • If not, go to step 2.

    2. Collect alarm information and configuration information, and then contact technical support personnel.
    3. End.
  • Cause 3: The peer is unreachable.
    1. Check the network connectivity between the local end and peer.

      • If the network connectivity is normal, go to step 2.
      • If the network connectivity fails, go to step 3.

    2. Configure a new clock source. Then, check whether NTP enters the synchronized state.

      • If so, go to step 4.
      • If not, go to step 3.

    3. Collect alarm information and configuration information, and then contact technical support personnel.
    4. End.
  • Cause 4: The peer fails authentication.
    1. Check whether NTP authentication is configured for both the local end and peer.

      • If so, go to step 2.
      • If not, configure NTP authentication.

    2. Check whether the NTP authentication keys on the local end and peer are the same.

      • If so, go to step 3.
      • If not, reconfigure the NTP authentication key.

    3. Collect alarm information and configuration information, and then contact technical support personnel.
    4. End.
  • Cause 5: The peer clock is not synchronized.
    1. Configure a new clock source.

      • If NTP enters synchronized state, go to step 3.
      • If NTP does not enter synchronized state, go to step 2.

    2. Collect alarm information and configuration information, and then contact technical support personnel.
    3. End.
  • Cause 6: The update interval for the peer clock exceeded the threshold.
    1. Configure a new clock source.

      • If NTP enters synchronized state, go to step 3.
      • If NTP does not enter synchronized state, go to step 2.

    2. Collect alarm information and configuration information, and then contact technical support personnel.
    3. End.
  • Cause 7: The NTP clock stratum on the peer is higher than that on the local end.
    1. Run the display ntp status command to check the NTP clock stratum on the local end.

      • If the clock stratum on the local end is lower than that on the peer, go to step 2.
      • If the clock stratum on the local end is higher than that on the peer, go to step 3.

    2. Configure a new clock source to make the clock stratum on the peer be lower than that on the local end.

      • If NTP enters synchronized state, go to step 4.
      • If NTP does not enter synchronized state, go to step 3.

    3. Collect alarm information and configuration information, and then contact technical support personnel.
    4. End.
  • Cause 8: The clock synchronization source is lost.
    1. Configure a new clock source.

      • If NTP enters synchronized state, go to step 3.
      • If NTP does not enter synchronized state, go to step 2.

    2. Collect alarm information and configuration information, and then contact technical support personnel.
    3. End.
  • Cause 9: The NTP mode on the local end does not match that on the peer.
    1. Run the display ntp sessions version command to view the NTP mode.

      • If the NTP mode on the local end matches that on the peer, go to step 3.
      • If the NTP mode on the local end does not match that on the peer, go to step 2.

    2. Set the NTP mode.

      • If NTP enters synchronized state, go to step 4.
      • If NTP does not enter synchronized state, go to step 3.

    3. Collect alarm information and configuration information, and then contact technical support personnel.
    4. End.
Translation
Download
Updated: 2019-03-20

Document ID: EDOC1000166558

Views: 196024

Downloads: 115

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