No relevant resource is found in the selected language.
Enterprise
Worldwide
Search
Support Documentation
S1700, S2720, S5700, and S6700 V200R019C10 Alarm Handling

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

PTP

PTP_1.3.6.1.4.1.2011.5.25.187.5.11 hwPTPRingFiberLengthChange

Description

PTP/3/PTPTRAPDFXRINGFIBERLENGTHCHANGE: OID [oid] [integer] The new offset value of the ring-network optical fiber that is connected to [STRING] is [integer1], which is a [integer2] value.

The ring network fiber length was changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.187.5.11 minor equipmentAlarm(6)

Parameters

Name Meaning
[oid] Indicates the MIB object ID of the alarm.
integer Interface index
STRING Interface name
integer1 New time offset caused by the fiber length change
integer2 Positive and negative values of the new time offset caused by the fiber length change

Impact on the System

The precision of clock synchronization is affected.

Possible Causes

The difference between the time offset caused by the fiber length change and the configured asymmetry correction value exceeded the specified range (± 55 ns).

Procedure

  1. Run the display this command in the interface view to check whether the asymmetry correction value is configured on the interface. That is, whether the ptp asymmetric-correction command configuration exists.

    • If yes, go to Step 2.
    • If no, go to Step 3.

  2. Run the ptp asymmetric-correction command to reconfigure the asymmetry correction value.
  3. Collect traps, logs, and configurations, and contact technical support personnel.

PTP_1.3.6.1.4.1.2011.5.25.187.5.12 hwPTPRingFiberLengthChangeResume

Description

PTP/3/PTPTRAPDFXRINGFIBERLENGTHCHANGERESUME: OID [oid] [integer] The length change value of the ring-network optical fiber that is connected to [STRING] is determined. The new offset value is [integer1], which is a [integer2] value

The ring network fiber length change was restored.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.187.5.12 minor equipmentAlarm(6)

Parameters

Name Meaning
[oid] Indicates the MIB object ID of the alarm.
integer Interface index
STRING Interface name
integer1 New time offset caused by the fiber length change
integer2 Positive and negative values of the new time offset caused by the fiber length change

Impact on the System

None.

Possible Causes

A new asymmetry correction value was configured for the interface on which the ring network fiber length change alarm was generated.

Procedure

  1. This log message is informational only, and no action is required.

PTP_1.3.6.1.4.1.2011.5.25.187.5.13 hwPtpTimeLockFail

Description

PTP/2/PTPTRAPDFXTIMELOCKFAIL: OID [oid] The time lock status is [integer] at present.

The time source failed to be locked.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.187.5.13 major equipmentAlarm(5)

Parameters

Name Meaning
[oid] Indicates the MIB object ID of the alarm.
[integer] Clock status
  • 0: out-of-lock
  • 1: locked

Impact on the System

Time synchronization fails.

Possible Causes

Possible causes are as follows:
  1. The frequency was out of lock.
  2. The subcard logic or the hardware of the clock module was faulty.
  3. The timestamp received when the fault occurred remained unchanged or the timestamp was incorrect.

Procedure

  1. Run the display clock source command to check whether the clock source is a PTP clock source.

    • If yes, go to Step 2.

    • If no, go to Step 4.

  2. Run the display current-configuration command to check whether the PTP configurations are changed.

    • If yes, go to Step 3.
    • If no, go to Step 6.

  3. Reconfigure PTP attributes. For details, see "Configuring PTP" in Configuration Guide - Device Management Configuration Guide.
  4. Run the display clock config command to check whether the clock source configurations are changed.

    • If yes, go to Step 5.
    • If no, go to Step 6.

  5. Reconfigure the local clock source. For details, see Configuration Guide - Device Management Configuration Guide.
  6. Collect traps, logs, and configurations, and contact technical support personnel.

PTP_1.3.6.1.4.1.2011.5.25.187.5.14 hwPtpTimeLockFailResume

Description

PTP/2/PTPTRAPDFXTIMELOCKFAILRESUME: OID [oid] Time lock is resumed at present, with the status of [integer].

The clock source was restored to locked.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.187.5.14 major equipmentAlarm(5)

Parameters

Name Meaning
[oid] Indicates the MIB object ID of the alarm.
[integer] Clock status.
  • 0: out-of-lock
  • 1: locked

Impact on the System

Time synchronization is restored.

Possible Causes

The clock source of time synchronization was traced and locked.

Procedure

  1. This log message is informational only, and no action is required.

PTP_1.3.6.1.4.1.2011.5.25.187.5.17 hwPtpFrequencyLockFail

Description

PTP/2/PTPTRAPDFXTIMELOCKFAIL: OID [oid] The time lock status is [integer] at present.

The time source was out of lock.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.187.5.17 major equipmentAlarm(5)

Parameters

Name Meaning
[oid] Indicates the MIB object ID of the alarm.
[integer] Clock status.
  • 0: out-of-lock
  • 1: locked

Impact on the System

Frequency synchronization fails.

Possible Causes

  1. In synchronous Ethernet mode, the frequency offset value of the reference frequency source exceeded the threshold.
  2. In 1588v2 frequency synchronization mode, the timestamp was abnormal.
  3. The internal frequency control word of the DSP exceeded ± 10 ppm.

Procedure

  1. Run the display clock source command to check whether the clock source is a PTP clock source.

    • If yes, go to Step 2.

    • If no, go to Step 4.

  2. Run the display current-configuration command to check whether the PTP configurations are changed.

    • If yes, go to Step 3.
    • If no, go to Step 6.

  3. Reconfigure the PTP attributes of the clock source. For details, see Configuration Guide - Device Management Configuration Guide.
  4. Run the display clock config command to check whether the clock source configurations are changed.

    • If yes, go to Step 5.
    • If no, go to Step 6.

  5. Reconfigure the local clock source. For details, see Configuration Guide - Device Management Configuration Guide.
  6. Collect traps, logs, and configurations, and contact technical support personnel.

PTP_1.3.6.1.4.1.2011.5.25.187.5.18 hwPtpFrequencyLockResume

Description

PTP/2/PTPTRAPDFXFREQLOCKFAILRESUME: OID [oid] Current lock status of clock frequency synchronization resumed. (hwClockFreqLockStatus = [integer])

The time out-of-lock was restored.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.187.5.18 major equipmentAlarm(5)

Parameters

Name Meaning
[oid] Indicates the MIB object ID of the alarm.
hwClockFreqLockStatus Clock status.
  • 0: out-of-lock
  • 1: locked

Impact on the System

Frequency synchronization is resumed.

Possible Causes

The clock source of frequency synchronization was traced and locked.

Procedure

  1. This log message is informational only, and no action is required.

PTP_1.3.6.1.4.1.2011.5.25.187.5.1 hwPtpPortStateChange

Description

PTP/4/PORTSTATECHANGE:OID [oid] The state of port [ULONG] changed.(portname=[STRING], currentstate=[STRING], oldstate=[STRING]).

The interface status was changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.187.5.1 Warning equipmentAlarm(5)

Parameters

Name Meaning
[oid] Indicates the MIB object ID of the alarm.
[ULONG] ID of the interface whose status was changed
portname Name of the interface whose status was changed
currentstate Status of the interface, including:
  1. Master
  2. Slave
  3. Passive
  4. Listening
  5. Faulty
  6. Initializing
  7. Premaster
  8. Disabled
  9. Uncalibrated
oldstate Old status of the interface, including:
  1. Master
  2. Slave
  3. Passive
  4. Listening
  5. Faulty
  6. Initializing
  7. Premaster
  8. Disabled
  9. Uncalibrated

Impact on the System

None.

Possible Causes

  1. Device attributes were changed.
  2. A link fault occurred or the interface was Down.

Procedure

  1. Run the display ptp all command in any view to check whether a faulty PTP interface exists.

    • If a PTP interface is in the faulty state, the link is faulty or the PTP interface is Down. In this case, go to Step 3.

    • If no PTP interface is in the faulty state, go to Step 2.

  2. Run the display this and display ptp all config commands in the interface view to check PTP configurations. Compare the PTP configurations with the previous configurations and check whether the clock attributes of the PTP device and interface have been changed.

    • If the clock attributes of the PTP device and interface have been changed, go to Step 4.
    • If the clock attributes of the PTP device and interface have not been changed, go to Step 3.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

PTP_1.3.6.1.4.1.2011.5.25.187.5.23 hwPtpPassiveFiberLengthChange

Description

PTP/3/PTPTRAPDFXPASSIVEFIBERLENGTHCHANGE: OID [oid] Passive port fiber length has changed.(Portindex=[integer], Portname=[STRING], Offset=[integer], Sign=[integer])

The fiber length of the passive interface was changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.187.5.23 minor qualityOfServiceAlarm(3)

Parameters

Name Meaning
[oid] Indicates the MIB object ID of the alarm.
Portindex Interface index
Portname Interface name
Offset New time offset caused by the fiber length change
Sign Positive and negative values of the new time offset caused by the fiber length change

Impact on the System

The precision of time synchronization is affected.

Possible Causes

The device measures the time offset value of the passive interface every 1000s. The difference between the time offset value and the configured asymmetry correction value exceeded the specified threshold.

Procedure

  1. Check whether the fiber length of the primary and secondary links are changed.

    • If yes, the transmit and receive fibers are asymmetric. In this case, replace the fibers and run the ptp asymmetry-correction command in the interface view to configure the asymmetric correction values on the asymmetric fiber interfaces.

    • If no, go to Step 2.

  2. Run the display current-configuration | include asymmetry command in the system view to check whether the asymmetric correction value is configured for the interfaces on the primary and secondary links.

    • If yes, the asymmetric correction values are configured incorrectly. In this case, run the ptp asymmetric-correction command in the interface view to reconfigure the asymmetric correction values.
    • If no, go to Step 3.

  3. Check whether the primary and secondary links are stable.

    • If yes, go to Step 4.
    • If no, locate and rectify the fault to ensure link stability.

  4. Collect traps, logs, and configurations, and contact technical support personnel.

PTP_1.3.6.1.4.1.2011.5.25.187.5.2 hwPtpClockSourceChange

Description

PTP/3/CLOCKSOURCECHANGE:OID [oid] [integer] Time source change from [STRING] to [STRING].(hwPtpPortOldSourcePortNum = [integer], hwPtpPortSourcePortNum = [integer], hwPtpOldPortName = [STRING], hwPtpPortName = [STRING])

The PTP clock source was changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.187.5.2 minor equipmentAlarm(5)

Parameters

Name Meaning
[oid] Indicates the MIB object ID of the alarm.
hwPtpPortOldSourcePortNum Port number of the device that once served as the clock source of the local device
hwPtpPortSourcePortNum Port number of the device that currently serves as the clock source of the local device
hwPtpOldPortName Port name of the device that once served as the clock source of the local device
hwPtpPortName Port name of the device that currently serves as the clock source of the local device

Impact on the System

Services are not affected.

Possible Causes

Possible causes are as follows:
  1. Device attributes were changed, causing clock source switching.
  2. The associated link or interface was Down.

Procedure

  1. Run the display ptp all command in any view to check whether a PTP interface is faulty.

    • If a PTP interface is faulty, the associated link is faulty or the PTP interface is Down. In this case, go to Step 3.

    • If no PTP interface is faulty, go to Step 2.

  2. Run the display this and display ptp all config commands in the interface view to view PTP configurations. Compare the PTP configurations with the previous configurations and check whether the clock attributes of the device and interface have been changed.

    • If the clock attributes of the PTP device and interface have been changed, go to Step 4.
    • If the clock attributes of the PTP device and interface have not been changed, go to Step 3.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

PTP_1.3.6.1.4.1.2011.5.25.187.5.30 hwPtpPortBmcInfoChange

Description

PTP/4/PORTBMCINFOCHANGE:OID [oid] The bmc info of port [integer] changed.(hwPtpPortName=[STRING], hwPtpPortSourcePortClockId =[STRING], hwPtpPortSourcePortNum=[integer],hwPtpPortSourceStepsRemoved =[integer])

The clock source information on the PTP interface changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.187.5.30 Warning equipmentAlarm(5)

Parameters

Name Meaning
[oid] Indicates the MIB object ID of the alarm.

integer

Interface index

hwPtpPortName

Interface name

hwPtpPortSourcePortClockId

Clock source ID received on an interface

hwPtpPortSourcePortNum

Clock source interface number received on an interface

hwPtpPortSourceStepsRemoved

Number of hops of the clock source received on an interface

Impact on the System

None.

Possible Causes

The clock source ID, clock source interface number, or number of hops of the clock source received on the interface changed.

Procedure

  1. This trap message is informational only, and no action is required.

PTP_1.3.6.1.4.1.2011.5.25.187.5.31 hwPtpTimeSourceClockClassDecline

Description

PTP/2/PTPTIMESOURCECLOCKCLASSDECLINE:OID [oid] The clock-class of input time source is below threshold.

The input clock class of the time source fell below the threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.187.5.31 Major qualityOfServiceAlarm(3)

Parameters

Name Meaning
[oid] Indicates the MIB object ID of the alarm.

Impact on the System

The clock class of the current clock source declined.

Possible Causes

  1. Cause 1: In PTP mode, the clock source's class was lower than the specified threshold, and the stepsRemoved value of the clock source was 0.
  2. Cause 2: In 1PPS+TOD mode, the class of a clock source's PPS was lower than the specified threshold.

Procedure

  1. Run the display ptp all command to check whether the current clock source is a PTP or 1PPS+TOD input.

    • If the current clock source is a PTP input, go to Step 2.
    • If the current clock source is a 1PPS+TOD input, go to Step 3.

  2. Run the display ptp all command to check whether the clockClass value of the clock source is lower than the specified threshold and whether stepsRemoved is 0.

    • If so, go to Step 5.
    • If not, go to Step 6.

  3. Run the display clock config command to check whether the current TOD format is CCSA.

    • If so, go to Step 4.
    • If not, go to Step 6.

  4. Run the display ptp all command to check whether the clock class of the synchronized external time interface falls below the threshold.

    • If so, go to Step 5.
    • If not, go to Step 6.

  5. Adjust the clock class of the device where the clock source resides to a higher level or switch to a clock source with a higher clock class. Then, check whether the alarm persists.

    • If so, go to Step 7.
    • If not, go to Step 6.

  6. Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

PTP_1.3.6.1.4.1.2011.5.25.187.5.32_hwPtpTimeSourceClockClassDeclineResume

PTP_1.3.6.1.4.1.2011.5.25.187.5.32 hwPtpTimeSourceClockClassDeclineResume

Description

PTP/2/PTPTIMESOURCECLOCKCLASSDECLINERESUME:OID [oid] The clock-class of input time source is above or equal to threshold.

The clock class of the time source was greater than or equal to the specified threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.187.5.32 Major equipmentAlarm(5)

Parameters

Name Meaning
[oid] Indicates the MIB object ID of the alarm.

Impact on the System

None.

Possible Causes

The clock class of the current time source was changed back to be greater than or equal to the specified threshold.

Procedure

  1. This log message is informational only, and no action is required.

Related Information

PTP_1.3.6.1.4.1.2011.5.25.187.5.31_hwPtpTimeSourceClockClassDecline

PTP_1.3.6.1.4.1.2011.5.25.187.5.33 hwPtpPktLos

Description

PTP/2/PTPPACKETLOST:OID [oid] The ptp packet of the trace source is lost. (hwPtpPktType = [integer]).

PTP packets were lost.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.187.5.33 Major equipmentAlarm(5)

Parameters

Name Meaning
[oid] Indicates the MIB object ID of the alarm.

hwPtpPktType

PTP packet type

Impact on the System

If Announce packets are dropped, the clock source will be switched. If Sync or Delay_Resp packets are dropped, an out-of-lock issue may occur.

Possible Causes

The slave interface fails to receive Announce, Sync, and Delay_Resp packets on the slave interface.

Procedure

  1. Run the display ptp interface interface-type interface-number command repeatedly to check whether the number of packets on the involved interface increases properly.

    • If so, go to Step 2.
    • If not, go to Step 4.

  2. Run the display ptp all config command on the peer device to check whether the peer interface is properly configured.

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

  3. Modify the configurations, such as the packet sending rate, of the peer interface. Then, check whether the alarm is cleared.

    • If so, go to Step 5.
    • If not, go to Step 4.

  4. Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.

Related Information

PTP_1.3.6.1.4.1.2011.5.25.187.5.34_hwPtpPktLosResume

PTP_1.3.6.1.4.1.2011.5.25.187.5.34 hwPtpPktLosResume

Description

PTP/2/PTPPACKETLOSTRESUME:OID [oid] The ptp packet of the trace port is normal. (hwPtpPktType = [integer]).

The PTP packet loss alarm was cleared.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.187.5.34 Major equipmentAlarm(5)

Parameters

Name Meaning
[oid] Indicates the MIB object ID of the alarm.

hwPtpPktType

PTP packet type

Impact on the System

None.

Possible Causes

The slave interface can properly receive Announce, Sync, and Delay_Resp packets.

Procedure

  1. This alarm is informational only, and no action is required.

Related Information

PTP_1.3.6.1.4.1.2011.5.25.187.5.33_hwPtpPktLos

PTP_1.3.6.1.4.1.2011.5.25.187.5.37 hwPtpTimeOffsetSumOver

Description

PTP/3/PTPTIMEOFFSETSUMOVER:OID [oid] The ptp time offset sum is abnormal.(hwPtpTimeOffsetSumP2P=[integer], hwPtpAlarmThresholdOffsetSum=[integer]).

The PTP time offset sum exceeded the threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.187.5.37 Minor equipmentAlarm(5)

Parameters

Name Meaning
[oid] Indicates the MIB object ID of the alarm.

hwPtpTimeOffsetSumP2P

Peak-to-peak time offset sum of the clock source

hwPtpAlarmThresholdOffsetSum

Alarm threshold for the time offset sum

Impact on the System

The involved device fails to lock the time source.

Possible Causes

The peak-to-peak time offset accumulated within 15 minutes exceeded the threshold.

Procedure

  1. Run the display ptp all command to check whether the current time is clocked.

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

  2. Wait for 5 minutes. Run the display ptp all command to check whether the time is locked.

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

  3. Wait for 5 minutes. Check whether the alarm is cleared.

    • If the alarm is cleared, go to Step 5.
    • If the alarm persists, go to Step 4.

  4. Collect trap, log, and configuration information, and contact Huawei technical support personnel.
  5. End.

Related Information

PTP_1.3.6.1.4.1.2011.5.25.187.5.38_hwPtpTimeOffsetSumOverResume

PTP_1.3.6.1.4.1.2011.5.25.187.5.38 hwPtpTimeOffsetSumOverResume

Description

PTP/3/PTPTIMEOFFSETSUMOVERRESUME:OID [oid] The ptp time offset sum is normal. (hwPtpTimeOffsetSumP2P=[integer], hwPtpAlarmThresholdOffsetSum=[integer])

The PTP time offset sum threshold-crossing alarm was cleared.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.187.5.38 Minor equipmentAlarm(5)

Parameters

Name Meaning
[oid] Indicates the MIB object ID of the alarm.

hwPtpTimeOffsetSumP2P

Peak-to-peak time offset sum of the clock source

hwPtpAlarmThresholdOffsetSum

Alarm threshold for the time offset sum

Impact on the System

The system will not be affected.

Possible Causes

The peak-to-peak time offset sum was restored to normal.

Procedure

  1. This alarm is informational only, and no action is required.

Related Information

PTP_1.3.6.1.4.1.2011.5.25.187.5.37_hwPtpTimeOffsetSumOver

PTP_1.3.6.1.4.1.2011.5.25.187.5.3 hwPtpTimeSyncFaulty

Description

PTP/3/SYNSTATUSFAULTY:OID [oid] Time source traced status is [integer]

PTP time synchronization failed.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.187.5.3

minor

equipmentAlarm(5)

Parameters

Name Meaning

[oid]

Indicates the MIB object ID of the alarm.

integer

Synchronization status of the clock source

Impact on the System

The device fails to perform time synchronization.

Possible Causes

Possible causes are as follows:

  1. The link was faulty or the interface went Down, and as a result, the device failed to keep trace of the clock source.
  2. The priority of the clock source was set to a large value so that the device was in the local state and failed to synchronize with time signals of other devices.

Procedure

  1. Run the display ptp command in any view to check whether the device is in the local state.

    • If yes, go to Step 2.

    • If not, go to Step 4.

  2. Run the display ptp all command in any view to check whether the external BITS signal status is normal.

    • If yes, go to Step 3.
    • If not, go to Step 4.

  3. Refer to Configuration Guide - Device Management Configuration Guide to configure clock source attributes. Then, check whether the alarm is cleared.

    • If the alarm is cleared, go to Step 5.
    • If the alarm persists, go to Step 4.

  4. Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.

PTP_1.3.6.1.4.1.2011.5.25.187.5.4 hwPtpTimeSyncResume

Description

PTP/3/SYNSTATUSRESUME:OID [oid] Time source traced status is [integer].

PTP time synchronization was resumed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.187.5.4 minor equipmentAlarm(5)

Parameters

Name Meaning
[oid] Indicates the MIB object ID of the alarm.
integer Synchronization status of the clock source

Impact on the System

Time synchronization is restored on the device.

Possible Causes

The PTP function was normal, and the device was synchronized. In this case, this alarm is informational only, and no action is required.

Procedure

  1. This log message is informational only, and no action is required.

Related Information

PTP_1.3.6.1.4.1.2011.5.25.187.5.3 hwPtpTimeSyncFaulty

Translation
日本語 简体中文
Download
Updated: 2022-05-25

Document ID: EDOC1100127008

Views: 80285

Downloads: 334

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Digital Signature File

Digital Signature Authentication Mode
Share
Previous Next

Copyright © 2023 Huawei Technologies Co., Ltd. All rights reserved.

You are going to visit :