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

OSN 500 550 580 V100R008C50 Alarms and Performance Events Reference 02

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).
PTP_ATTR_MISMATCH

PTP_ATTR_MISMATCH

Description

The PTP_ATTR_MISMATCH alarm indicates that Precision Time Protocol (PTP) port attributes are inconsistent at two ends. If the PTP port attributes are inconsistent at two ends, PTP packets may not be processed correctly. As a result, the time cannot be traced normally.

Attribute

Alarm Severity Alarm Type

Minor

Equipment alarm

Parameters

When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table.

Name Meaning

Parameter 1

Indicates the inconsistent PTP port attribute.

  • 0x01: The delay modes are inconsistent.
  • 0x02: The encapsulation types are inconsistent.
  • 0x03: The clock subnet IDs are inconsistent.
  • 0x04: The peer clock source IDs to be received are inconsistent.

Impact on the System

The time cannot be traced normally.

Possible Causes

The possible causes of the PTP_ATTR_MISMATCH alarm are as follows:

  • Cause 1: The delay modes are inconsistent.
  • Cause 2: The encapsulation types are inconsistent.
  • Cause 3: The clock subnet IDs are inconsistent.
  • Cause 4: The peer clock source IDs to be received are inconsistent.

Procedure

  1. Check the alarm on the NMS and determine the cause of the alarm according to the alarm parameters.
  2. Cause 1: The delay modes are inconsistent.
    1. Check whether the time port delay mechanisms are consistent between the PTP ports at both ends.
    If… Then...

    The time port delay mechanisms are inconsistent,

    Set the time port delay mechanisms to the same values for the PTP ports at both ends. That is, set the P/E modes to either E2E or P2P. For details, see Setting Parameters for IEEE 1588v2 Clock Packets in Feature Description. Then check whether the alarm is cleared. If the alarm persists, go to 6.

    The time port delay mechanisms are consistent,

    Check whether the alarm is cleared. If the alarm persists, go to 6.

  3. Cause 2: The encapsulation types are inconsistent.
    1. Check whether the encapsulation types are consistent between the PTP ports at both ends.
    If… Then...

    The encapsulation types are inconsistent,

    Set PTP Packet Encapsulation Format to the same values for the PTP ports at both ends. For details, see Setting PTP Clock Port Attributes in Feature Description. Then check whether the alarm is cleared. If the alarm persists, go to 6.

    The encapsulation types are consistent,

    Check whether the alarm is cleared. If the alarm persists, go to 6.

  4. Cause 3: The clock subnet IDs are inconsistent.
    1. Check whether the clock subnet IDs are consistent between the PTP ports at both ends.
    If... Then...

    The clock subnet IDs are inconsistent,

    Set the clock subnet IDs to the same values for the PTP ports at both ends. For details, see Configuring a PTP Clock Subnet in Feature Description. Then check whether the alarm is cleared. If the alarm persists, go to 6.

    The clock subnet IDs are consistent,

    Check whether the alarm is cleared. If the alarm persists, go to 6.

  5. Cause 4: The peer clock source IDs to be received are inconsistent.
    1. Check whether a loop exists on the link.
    If... Then...

    A loop exists on the link,

    Eliminate the loop. Then check whether the alarm is cleared. If the alarm persists, go to 6.

    No loop exists on the link,

    Check whether the alarm is cleared. If the alarm persists, go to 6.

  6. Contact Huawei technical support engineers to handle the alarm.

Related Information

None

Translation
Download
Updated: 2019-01-21

Document ID: EDOC1100020975

Views: 75003

Downloads: 136

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